From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Why is Org PDF LaTeX Output not readonly?
Date: Thu, 16 Feb 2017 09:48:54 -0500 [thread overview]
Message-ID: <87h93u199l.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: o83o47$ofj$1@blaine.gmane.org
Florian Lindner <mailinglists@xgm.de> 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
next prev parent reply other threads:[~2017-02-16 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f6483136fa0b484ea496f3b1fd44cc41@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-02-15 14:22 ` Why is Org PDF LaTeX Output not readonly? Eric S Fraga
2017-02-15 16:07 ` Florian Lindner
2017-02-15 16:22 ` Nick Dokos
[not found] ` <e073edef4f544608a389ac999bd86f80@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-02-15 16:37 ` Eric S Fraga
2017-02-16 8:33 ` Florian Lindner
2017-02-16 14:48 ` Nick Dokos [this message]
[not found] ` <075f23b0867d4f43bac143679183abb1@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-02-16 16:41 ` Eric S Fraga
2017-02-17 13:24 ` Nick Dokos
[not found] ` <79bb378e94514fd7b377b77b3301f404@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-02-16 13:47 ` Eric S Fraga
2017-02-16 16:09 ` Florian Lindner
2017-02-17 12:35 ` Nicolas Goaziou
2017-02-19 11:24 ` Florian Lindner
2017-02-15 14:02 Florian Lindner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h93u199l.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).