Am 17.02.2017 um 13:35 schrieb Nicolas Goaziou:
> Hello,
>
> Florian Lindner writes:
>
>> Am 16.02.2017 um 14:47 schrieb Eric S Fraga:
>>> On Thursday, 16 Feb 2017 at 08:33, Florian Lindner wrote:
It would be much easier to close it quickly this way and it would be
consistent with othe
Eric S Fraga writes:
> On Thursday, 16 Feb 2017 at 14:48, Nick Dokos wrote:
>
> [...]
>
>> I don't understand this: why is it easier if the buffer is read-only?
>> Don't you still have to do M-x kill-buffer?
>
> IIUC, it's not so much read-only as a special mode where a single 'q'
> will bury the
Hello,
Florian Lindner writes:
> Am 16.02.2017 um 14:47 schrieb Eric S Fraga:
>> On Thursday, 16 Feb 2017 at 08:33, Florian Lindner wrote:
>>> It would be much easier to close it quickly this way and it would be
>>> consistent with other buffers that serve the same
>>> purpose, like the beforeme
On Thursday, 16 Feb 2017 at 14:48, Nick Dokos wrote:
[...]
> I don't understand this: why is it easier if the buffer is read-only?
> Don't you still have to do M-x kill-buffer?
IIUC, it's not so much read-only as a special mode where a single 'q'
will bury the buffer (or delete it, maybe). Sort
Am 16.02.2017 um 14:47 schrieb Eric S Fraga:
> On Thursday, 16 Feb 2017 at 08:33, Florian Lindner wrote:
>> It would be much easier to close it quickly this way and it would be
>> consistent with other buffers that serve the same
>> purpose, like the beforementioned Auctex output buffer.
>
> It wo
Florian Lindner writes:
> Am 15.02.2017 um 17:37 schrieb Eric S Fraga:
>> On Wednesday, 15 Feb 2017 at 16:07, Florian Lindner wrote:
>>> The exported PDF opens in okular (xdg-open) and I'm perfectly happy with
>>> it. I think we're talking about different
>>> things. I mean the buffer that conta
On Thursday, 16 Feb 2017 at 08:33, Florian Lindner wrote:
> It would be much easier to close it quickly this way and it would be
> consistent with other buffers that serve the same
> purpose, like the beforementioned Auctex output buffer.
It would indeed be easier. The buffer is created in org-la
Am 15.02.2017 um 17:37 schrieb Eric S Fraga:
> On Wednesday, 15 Feb 2017 at 16:07, Florian Lindner wrote:
>> The exported PDF opens in okular (xdg-open) and I'm perfectly happy with it.
>> I think we're talking about different
>> things. I mean the buffer that contains the output of the latex comm
On Wednesday, 15 Feb 2017 at 16:07, Florian Lindner wrote:
> The exported PDF opens in okular (xdg-open) and I'm perfectly happy with it.
> I think we're talking about different
> things. I mean the buffer that contains the output of the latex command and
> potential error message, looking like:
Florian Lindner writes:
> Am 15.02.2017 um 15:22 schrieb Eric S Fraga:
> The exported PDF opens in okular (xdg-open) and I'm perfectly happy with it.
> I think we're talking about different
> things. I mean the buffer that contains the output of the latex command and
> potential error message,
Am 15.02.2017 um 15:22 schrieb Eric S Fraga:
> On Wednesday, 15 Feb 2017 at 14:02, Florian Lindner wrote:
>> Hello,
>>
>> is there any reason why the output buffer of org mode exporting to
>> LaTeX is not read-only? Read-only is probably not the
>> right expression, what I mean is that e.g. q calls
On Wednesday, 15 Feb 2017 at 14:02, Florian Lindner wrote:
> Hello,
>
> is there any reason why the output buffer of org mode exporting to
> LaTeX is not read-only? Read-only is probably not the
> right expression, what I mean is that e.g. q calls quit-window and
> closes the window. This way it's
Hello,
is there any reason why the output buffer of org mode exporting to LaTeX is not
read-only? Read-only is probably not the
right expression, what I mean is that e.g. q calls quit-window and closes the
window. This way it's done by Auctex.
Thanks,
Florian
13 matches
Mail list logo
