* Re: Why is Org PDF LaTeX Output not readonly?
[not found] <f6483136fa0b484ea496f3b1fd44cc41@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
@ 2017-02-15 14:22 ` Eric S Fraga
2017-02-15 16:07 ` Florian Lindner
[not found] ` <e073edef4f544608a389ac999bd86f80@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
0 siblings, 2 replies; 13+ messages in thread
From: Eric S Fraga @ 2017-02-15 14:22 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
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 done by Auctex.
It is for me as the PDF is displayed in a docview window. I.e. if I
export to "PDF and open" and then type 'q' in that buffer, the window is
buried ('k' kills the window). What version of emacs are you using?
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Why is Org PDF LaTeX Output not readonly?
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>
1 sibling, 1 reply; 13+ messages in thread
From: Florian Lindner @ 2017-02-15 16:07 UTC (permalink / raw)
To: emacs-orgmode
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 quit-window and
>> closes the window. This way it's done by Auctex.
>
> It is for me as the PDF is displayed in a docview window. I.e. if I
> export to "PDF and open" and then type 'q' in that buffer, the window is
> buried ('k' kills the window). What version of emacs are you using?
Hey,
I'm using
GNU Emacs 25.1.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.22.7) of 2017-02-07
Org mode version 9.0.5 (9.0.5-elpa @ /home/florian/.emacs.d/elpa/org-20170210/)
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:
Latexmk: This is Latexmk, John Collins, 5 Sep. 2016, version: 4.48.
Rule 'pdflatex': Rules & subrules not known to be previously run:
pdflatex
Rule 'pdflatex': The following rules & subrules became out-of-date:
'pdflatex'
------------
Run number 1 of rule 'pdflatex'
------------
------------
Running 'pdflatex -recorder "./RBF.tex"'
------------
Latexmk: applying rule 'pdflatex'...
This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Arch Linux) (preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
(./RBF.tex
LaTeX2e <2016/03/31> patch level 3
Babel <3.9r> and hyphenation patterns for 83 language(s) loaded.
(/usr/share/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texmf-dist/tex/latex/base/size11.clo))
[...]
Best,
Florian
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Why is Org PDF LaTeX Output not readonly?
2017-02-15 16:07 ` Florian Lindner
@ 2017-02-15 16:22 ` Nick Dokos
0 siblings, 0 replies; 13+ messages in thread
From: Nick Dokos @ 2017-02-15 16:22 UTC (permalink / raw)
To: emacs-orgmode
Florian Lindner <mailinglists@xgm.de> 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, looking like:
>
> Latexmk: This is Latexmk, John Collins, 5 Sep. 2016, version: 4.48.
Why does it matter?
--
Nick
^ permalink raw reply [flat|nested] 13+ messages in thread
[parent not found: <e073edef4f544608a389ac999bd86f80@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>]
* Re: Why is Org PDF LaTeX Output not readonly?
[not found] ` <e073edef4f544608a389ac999bd86f80@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
@ 2017-02-15 16:37 ` Eric S Fraga
2017-02-16 8:33 ` Florian Lindner
[not found] ` <79bb378e94514fd7b377b77b3301f404@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
0 siblings, 2 replies; 13+ messages in thread
From: Eric S Fraga @ 2017-02-15 16:37 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
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.
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Why is Org PDF LaTeX Output not readonly?
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>
[not found] ` <79bb378e94514fd7b377b77b3301f404@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
1 sibling, 2 replies; 13+ messages in thread
From: Florian Lindner @ 2017-02-16 8:33 UTC (permalink / raw)
To: emacs-orgmode
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 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.
Florian
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Why is Org PDF LaTeX Output not readonly?
2017-02-16 8:33 ` Florian Lindner
@ 2017-02-16 14:48 ` Nick Dokos
[not found] ` <075f23b0867d4f43bac143679183abb1@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
1 sibling, 0 replies; 13+ messages in thread
From: Nick Dokos @ 2017-02-16 14:48 UTC (permalink / raw)
To: emacs-orgmode
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
^ permalink raw reply [flat|nested] 13+ messages in thread[parent not found: <075f23b0867d4f43bac143679183abb1@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>]
* Re: Why is Org PDF LaTeX Output not readonly?
[not found] ` <075f23b0867d4f43bac143679183abb1@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
@ 2017-02-16 16:41 ` Eric S Fraga
2017-02-17 13:24 ` Nick Dokos
0 siblings, 1 reply; 13+ messages in thread
From: Eric S Fraga @ 2017-02-16 16:41 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
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 of like docview or
what read-only views give.
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Why is Org PDF LaTeX Output not readonly?
2017-02-16 16:41 ` Eric S Fraga
@ 2017-02-17 13:24 ` Nick Dokos
0 siblings, 0 replies; 13+ messages in thread
From: Nick Dokos @ 2017-02-17 13:24 UTC (permalink / raw)
To: emacs-orgmode
Eric S Fraga <e.fraga@ucl.ac.uk> 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 buffer (or delete it, maybe). Sort of like docview or
> what read-only views give.
Ok - thanks!
--
Nick
^ permalink raw reply [flat|nested] 13+ messages in thread
[parent not found: <79bb378e94514fd7b377b77b3301f404@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>]
* Re: Why is Org PDF LaTeX Output not readonly?
[not found] ` <79bb378e94514fd7b377b77b3301f404@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
@ 2017-02-16 13:47 ` Eric S Fraga
2017-02-16 16:09 ` Florian Lindner
0 siblings, 1 reply; 13+ messages in thread
From: Eric S Fraga @ 2017-02-16 13:47 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
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.
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Why is Org PDF LaTeX Output not readonly?
2017-02-16 13:47 ` Eric S Fraga
@ 2017-02-16 16:09 ` Florian Lindner
2017-02-17 12:35 ` Nicolas Goaziou
0 siblings, 1 reply; 13+ messages in thread
From: Florian Lindner @ 2017-02-16 16:09 UTC (permalink / raw)
To: emacs-orgmode
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.
Best,
Florian
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Why is Org PDF LaTeX Output not readonly?
2017-02-16 16:09 ` Florian Lindner
@ 2017-02-17 12:35 ` Nicolas Goaziou
2017-02-19 11:24 ` Florian Lindner
0 siblings, 1 reply; 13+ messages in thread
From: Nicolas Goaziou @ 2017-02-17 12:35 UTC (permalink / raw)
To: Florian Lindner; +Cc: emacs-orgmode
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
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Why is Org PDF LaTeX Output not readonly?
2017-02-17 12:35 ` Nicolas Goaziou
@ 2017-02-19 11:24 ` Florian Lindner
0 siblings, 0 replies; 13+ messages in thread
From: Florian Lindner @ 2017-02-19 11:24 UTC (permalink / raw)
To: emacs-orgmode
Am 17.02.2017 um 13:35 schrieb Nicolas Goaziou:
> 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'.
http://orgmode.org/w/org-mode.git?p=org-mode.git;a=commit;h=67c84c161fa4e97c1f98ef1bbc72fa0f6098e1fd
Great! Thanks!
^ permalink raw reply [flat|nested] 13+ messages in thread
* Why is Org PDF LaTeX Output not readonly?
@ 2017-02-15 14:02 Florian Lindner
0 siblings, 0 replies; 13+ messages in thread
From: Florian Lindner @ 2017-02-15 14:02 UTC (permalink / raw)
To: emacs-orgmode
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
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2017-02-19 11:24 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[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
2017-02-19 11:24 ` Florian Lindner
2017-02-15 14:02 Florian Lindner
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).