emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Florian Lindner <mailinglists@xgm.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Why is Org PDF LaTeX Output not readonly?
Date: Fri, 17 Feb 2017 13:35:48 +0100	[thread overview]
Message-ID: <87bmu1ataz.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <o84irh$b9e$1@blaine.gmane.org> (Florian Lindner's message of "Thu, 16 Feb 2017 17:09:27 +0100")

Hello,

Florian Lindner <mailinglists@xgm.de> 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 beforementioned Auctex output buffer.
>> 
>> It would indeed be easier.  The buffer is created in org-latex-compile
>> and I guess it would be the case of setting the mode for the buffer?
>> Beyond my level of elisp expertise however.
>
> There is with-output-to-temp-buffer with redirects the output to a temp buffer that behaves like a help window and shows
> that buffer Using this function however makes only sense, when org mode defaults to displaying the latex output in case
> something goes wrong. Which, imo would be as sensible default too.
>
> Changing that is also way beyond my elisp knowlege.

In development version, Org now switches compilation buffers to
`compilation-mode'.

Thank you.

Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2017-02-17 12:36 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
     [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 [this message]
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=87bmu1ataz.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=mailinglists@xgm.de \
    /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

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).