Eric:
I was able to access the API docs (requiring, with my Firefox, to accept a
security exception.)
https://aa.usno.navy.mil/data/docs/api.php
I have to move on. I have found that XEphem's Moon declination output is
excellent, so I only have to convert the time format.
Thank you for your hel
On Tuesday, 27 Nov 2018 at 19:33, Samuel Wales wrote:
> this might be the most ridiculous idea you have ever heard, but does
> babel have a concept similar to stdio pipes? i've often wanted to
> just pipe stuff. dunno if this would help marcin.
>
> the only inter-block communication i am aware of
this might be the most ridiculous idea you have ever heard, but does
babel have a concept similar to stdio pipes? i've often wanted to
just pipe stuff. dunno if this would help marcin.
the only inter-block communication i am aware of are variables and
noweb inclusion.
[and, unless i am mistaken
On Tue, Nov 27, 2018 at 3:57 AM Marcin Borkowski wrote:
> but it's fairly complicated. Any better ideas?
What is the part that you think is too complicated?
One last suggestion. I see the latex export backend takes any BEGIN_XXX and
outputs a \begin{XXX} environment. That would be almost what I was asking
for when XXX = equation or displaymath or whatever. Except that in that
case the inline preview wont work (for BEGIN_LATEX it was working just
becaus
Indeed it would be nice to have preview working for SRC blocks with lang =
latex too.
> > 1. #+BEGIN_LATEX could be changed to honor current fontification
> > setting
>
> This construct doesn't exist in Org.
Yes, I realized after posting, it was suggested in reddit but I was
unable to find any reference to it in the source code. Maybe it did
exist in the past since it's often menti
Hello,
Carlos Pita writes:
> So, to sum up:
>
> 1. #+BEGIN_LATEX could be changed to honor current fontification
> setting
This construct doesn't exist in Org.
> 2. #+BEGIN_EXPORT latex should be changed to allow inline preview
>
> I would say 2 is a bug.
It is not a bug. Why would it be one?
emanuel.charpent...@gmail.com writes:
> Le mardi 27 novembre 2018 à 21:26 +0100, Nicolas Goaziou a écrit :
>
> [ Snip... ]
>
>> What happens if you remove "org-ref.el" reference?
>
> Same thing.
>
> Even after uninstalling org-ref and its dependencies.
>
> Sorry...
OK. I got it. This has nothing
ok. I thought there might be a reason. I guess something like a read-only
property could be a problem if anything tries to change those. Are there
other properties you know of that could be problematic? maybe before/after
change properties? I think there are inhibit-* variables to avoid issues
with
Ok, I got the "#+BEGIN_LATEX latex" idea from reddit, but exploring
the source code I realized that the right thing to do here is to
"#+BEGIN_EXPORT latex" which makes more sense and is less redundant.
Now the problem still exists that "#+BEGIN_EXPORT latex" won't do
inline preview.
So, to sum up
Hello,
John Kitchin writes:
> In the function org-export--generate-copy-script, the buffer contents are
> copied over with buffer-substring-no-properties, so it appears that all
> text properties are lost in the temporary copy.
>
> I wondered why that is done?
I feel more comfortable when I can
Please, add the ability to fontify code inside
#+BEGIN_LATEX
...
#+END_LATEX
blocks. Embedded LaTeX doesn't get native fontification and SRC
blocks aren't the place to just get fancy colors (besides, latex inline
preview doesn't work for them). Currently there is this trick:
#+BEGIN_LATEX latex
Hello,
David Masterson writes:
> * Header 1
>
> * Header 2
>
> Position the cursor on '1' and M-return will create a new header with a
> blank line before and after it, but C-return will create a new header
> with a blank line before, but not after it.
I see. I pushed a fix in master branch. Pl
Le mardi 27 novembre 2018 à 21:26 +0100, Nicolas Goaziou a écrit :
[ Snip... ]
> What happens if you remove "org-ref.el" reference?
Same thing.
Even after uninstalling org-ref and its dependencies.
Sorry...
--
Emmanuel Charpentier
Hello,
John Ciolfi writes:
> Hi
>
> I ran into a confusing error due to missing language for a code block. Given
> attached issue.org
> which contains:
>
> #+BEGIN_SRC
> if (a > 1) {
> }
> #+END_SRC
>
> if you convert to pdf using the attached issue_repro.el via:
>
> emacs
Hello,
Matt Price writes:
> As per our earlier thread, here is a patch to remove
> org-src--saved-temp-window-config from org-src.el.
> From ad2d8d26eee6c2bcfa517e0f7352406c9980bfd4 Mon Sep 17 00:00:00 2001
> From: Matt Price
> Date: Tue, 27 Nov 2018 08:19:03 -0500
> Subject: [PATCH] Org-sr.el:
Hello,
Emmanuel Charpentier writes:
> My original posting included the tex file generated by C-c C-e l l.
> Perusing it will show you that babel is not used anywhere in this export.
>
> On the (remote) chance that my problem might be caused by my use of emacs
> 25.2, I just installe emacs 26 fro
In the function org-export--generate-copy-script, the buffer contents are
copied over with buffer-substring-no-properties, so it appears that all
text properties are lost in the temporary copy.
I wondered why that is done?
I came across this because I was using text properties to find pieces of
t
Nicolas Goaziou writes:
> David Masterson writes:
>> My example is simple.
>>
>> * emacs --no-init
>> * edit an org file with an outline
>> * position cursor at the end of an outline entry
>> * M-Return
>> ** result: a new header with a blank line before and after
>> * C-Return
>> ** result: a
My original posting included the tex file generated by C-c C-e l l.
Perusing it will show you that babel is not used anywhere in this export.
On the (remote) chance that my problem might be caused by my use of emacs
25.2, I just installe emacs 26 from the emacs-snapshot packages for Debian
testing
Hello,
Emmanuel Charpentier writes:
> As of today, I note that the #+langiage export variable is no longer
> honored when exporting to LaTeX/PDF. See enclosed files :
I noticed this quite some time go (months, last year maybe), but didn't
dived into it because I'm not sure what to expect. ox-lat
On Sunday, 25 Nov 2018 at 21:36, emanuel.charpent...@gmail.com wrote:
> I forgot to add that, when exporting to plain tex or ODT, #+language*
> *seems* to be honored : the table of contents is entitled "Table des
> matières".
>
> The problem is therefore probably in ox-latex.el (but way above my
>
As per our earlier thread, here is a patch to remove
org-src--saved-temp-window-config from org-src.el.
From ad2d8d26eee6c2bcfa517e0f7352406c9980bfd4 Mon Sep 17 00:00:00 2001
From: Matt Price
Date: Tue, 27 Nov 2018 08:19:03 -0500
Subject: [PATCH] Org-sr.el: On exiting src buffer, do not restore pr
I forgot to add that, when exporting to plain tex or ODT, #+language*
*seems* to be honored : the table of contents is entitled "Table des
matières".
The problem is therefore probably in ox-latex.el (but way above my
level of competance in em...
--
Emmanuel Charpentier
I forgot to add that, when exporting to plain tex or ODT, #+language*
*seems* to be honored : the table of contents is entitled "Table des
matières".
The problem is therefore probably in ox-latex.el (but way above my
level of competance in emacs-lisp...).
--
Emmanuel Charpentier
Hi
I ran into a confusing error due to missing language for a code block. Given
attached issue.org
which contains:
#+BEGIN_SRC
if (a > 1) {
}
#+END_SRC
if you convert to pdf using the attached issue_repro.el via:
emacs --batch -L /path/to/org/install/emacs/site-lisp/org
Hi folks,
I have a multiline source block (a complex sql query). I'd like it to
be inserted into another (shell) source block, so that I can run psql on
a remote server (via ssh) and execute this query (I cannot access the
database from my machine).
I came up with this:
--8<---cut h
On Tuesday, November 27, 2018 12:02 AM, Nicolas Goaziou
wrote:
>
> Are you talking about Org a whole, or just Org agenda? All your examples
> are about the latter. If it's about Org agenda, well, I'm afraid to say
> there are so many things to fix there that keybindings are only the tip
> of the
Hello,
Gustav Wikström writes:
> Too bad, "@" was growing on me. @ is currently automatically set as
> a tag when attaching files to nodes.
You probably customized `org-attach-auto-tag' because this is not the
default behaviour. It adds "ATTACH" tag automatically.
> So it was fitting to use it
Hello,
David Masterson writes:
> My example is simple.
>
> * emacs --no-init
> * edit an org file with an outline
> * position cursor at the end of an outline entry
> * M-Return
> ** result: a new header with a blank line before and after
> * C-Return
> ** result: a new header with a blank line
Hello,
mithraeum writes:
> I'd like to request that org's keybindings be separated from the functions
> they use to do their work.
>
> This would greatly ease the use of these functions by people who want to use
> their own keybindings rather than relying on keybindings that org provides.
>
>
32 matches
Mail list logo
