[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Why is Org PDF LaTeX Output not readonly?
From: |
Nick Dokos |
Subject: |
Re: [O] Why is Org PDF LaTeX Output not readonly? |
Date: |
Thu, 16 Feb 2017 09:48:54 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) |
Florian Lindner <address@hidden> 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 contains the output of the latex command and
>>> potential error message, looking like:
>>
>> Oh, sorry, I misunderstood. Well, as Nick says, does it really matter
>> as editing it won't affect anything?
>>
>> Funnily enough, I never see this buffer unless I go looking for
>> it. Maybe there's an org setting that causes this buffer to be
>> displayed or not? I cannot see one.
>
> It would be much easier to close it quickly this way
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?
> and it would be consistent with other buffers that serve the same
> purpose, like the beforementioned Auctex output buffer.
>
> For me, it would just the right thing.
>
OK - that I can understand.
--
Nick
- [O] Why is Org PDF LaTeX Output not readonly?, Florian Lindner, 2017/02/15
- Message not available
- Re: [O] Why is Org PDF LaTeX Output not readonly?, Eric S Fraga, 2017/02/16
- Re: [O] Why is Org PDF LaTeX Output not readonly?, Florian Lindner, 2017/02/16
- Re: [O] Why is Org PDF LaTeX Output not readonly?, Nicolas Goaziou, 2017/02/17
- Re: [O] Why is Org PDF LaTeX Output not readonly?, Florian Lindner, 2017/02/19