Am 11. Februar 2021 um 21:12 Uhr +0100 schrieb Sébastien Miquel:
> The purpose of #+BIND is to set some variables in the copied buffer.
>
> Also, these variables are set after macro expansion (and
> org-export-before-parsing-hook).
Thanks for the information. If they are set after macro
Maxim Nikulin writes:
> Looking into the code related to 'pty problem with
> start-process-shell-command, I have realized that the following case is
> not handled correctly:
>
> #+begin_src elisp
>(setq org-file-apps '(("\\.pdf::\\([0-9]+\\)\\'" . "xpdf %s %1")))
> #+end_src
Not relevant
TEC writes:
> Hi All,
>
> This is just some tweaks to the styling in ox-html that I think may
> appeal (and prevent ridiculously long lines on non-small displays, which
> are an issue for legibility).
>
> I also took the opportunity to remove the (obsolete) CDATA strings and
> make the CSS more
aroz...@gmail.com writes:
> I would like to open ID links [[id:...]] in a new window. I can make file
> links [[file:...]] open in a new window by running (add-to-list
> 'org-link-frame-setup '(file . find-file-other-window)), but this doesn't
> seem to affect the behavior of ID links.
Here's
Thomas S. Dye writes:
> Aloha all,
>
> Recently, custom links that I've used for years changed their
> behavior. They used to behave like other org mode links, but now
> they are displayed in a different color face and are always fully
> displayed, unless I add two new keywords to
>
Rodrigo Morales writes:
> * The question
>
> Let's suppose I have this simple code block in a buffer (let's say
> =A=)
>
> #+NAME: five-numbers
> #+begin_src bash
> echo foo
> seq 1 5
> echo bar
> #+end_src
>
> How can I get the content of the code block with name =five-numbers=
> as an string
How many custom, self-made tags can you have with org-mode? org-tag-alist
seems maxed out at 26. Is that the limit? On a heading, I can C-c C-c and a
(helm?) buffer comes up with my 26 tag choices. So can you only create as
many tags as there are lower-case letters in the alphabet. Is this true? I
* The question
Let's suppose I have this simple code block in a buffer (let's say
=A=)
#+NAME: five-numbers
#+begin_src bash
echo foo
seq 1 5
echo bar
#+end_src
How can I get the content of the code block with name =five-numbers=
as an string from any point in buffer =A=?
* Additional
* The problem
Let's suppose we have this simple code block
#+NAME: my-named-code-block
#+begin_src bash
echo foo-1
echo foo-2
#+end_src
which contain some commands that we want to execute before the
commands that are presented below. Therefore, we use the =:prologue=
header argument
Christian Moe writes:
> Hi,
>
> This is actually easy because Org allows named footnotes (numbers are
> really just a special case of names).
>
> Make backup copies of your files for safety's sake, then visit file1.org
> and M-% to replace all instances of "fn:" with (for example)
> "fn:file1_".
M. ‘quintus’ Gülker writes:
Now I wonder whether #+BIND is more elegant. But my macro expansion
function modifies a buffer-local variable. Does #+BIND allow for that,
so that the changed value is available in the original org buffer?
The purpose of #+BIND is to set some variables in the
Hi,
This is actually easy because Org allows named footnotes (numbers are
really just a special case of names).
Make backup copies of your files for safety's sake, then visit file1.org
and M-% to replace all instances of "fn:" with (for example)
"fn:file1_". The footnotes will now be named
On Thu, Feb 11, 2021 at 11:49:32AM -0600, aroz...@gmail.com wrote:
> Most of my writing is academic and involves lots of footnotes. Sometimes it
> is useful to be able to combine two separate files, each of which have
> footnotes. How do I do so in a way that automatically renumbers the
>
Lee Jia Hong,
on your second surprise, there was some discussion on the e-mail list,
around 19 April, 2020, somewhere near this area. you might refer to
that.
cheers, again, Greg
Most of my writing is academic and involves lots of footnotes. Sometimes it
is useful to be able to combine two separate files, each of which have
footnotes. How do I do so in a way that automatically renumbers the
footnotes in the file that comes second?
More specifically, I have file1.org and
Lee Jia Hong,
for your surprise number one, maybe look at this point of the Org Manual
Noweb insertions honor prefix characters that appear before the noweb
syntax reference.
basically, if the source of a <> has multiple lines (N, say), then the
output of a subsequent <> *copies* that
Jia,
#2 is known (maybe documented? Not sure) behavior: using :noweb-ref
accumulates multiple blocks with the same name, whereas #+NAME uses only
the first one. I think #+NAME's are supposed to be unique within a document.
I don't know about #1, the output from your P1 example seems surprising
* ox-html.el (org-html-template): Added the support for a CSS class name
to the content tag which wraps the entire content. The CSS class name
can be set via in buffer HTML_CONTENT_CLASS property or :html-content-class
for org publish.
---
lisp/ox-html.el | 16 +++-
1 file changed, 15
Maxim Nikulin writes:
> It is not namely typing latency, but I have noticed lags while moving
> over collapsed headings with "up" key (with "down" it is not so
> apparent) e.g. in overview view. It has happened after linux upgrade,
> emacs version changed from 25.2 to 25.3, system package
On 09/02/2021 01:24, Sébastien Miquel wrote:
I often get some unpleasant latency when editing org-mode
1. Is anyone experiencing something similar ?
It is not namely typing latency, but I have noticed lags while moving
over collapsed headings with "up" key (with "down" it is not so
On Tuesday, 9 Feb 2021 at 11:57, Dmitry Knyaginin wrote:
> during typing, all content below the current line disappeared.
> The content was unrecoverable with "undo".
:-(
You can type C-h l at any time to see all your recent keystrokes, in
case it was something you mis-typed to lead to this
On Tuesday, 9 Feb 2021 at 15:23, Christian Thäter wrote:
> Apropos, try out the native-comp Emacs branch.
Thank you. I've been watching the development of this branch with
interest! I'm too busy at the moment with work to play around with it
but I will soon.
Emacs, so long as I remember to
(First time posting to a mailing list, please correct me if I did something
wrong.)
TLDR:
Surprise 1: Different Noweb reference placing styles produces different tangled
results.
Question 1: Is it a bug?
Surprise 2: Source block naming with #+NAME: and :noweb-ref produce different
tangled
Hello,
I would like to report a bug:
during typing, all content below the current line disappeared.
The content was unrecoverable with "undo".
Have you seen this before?
The .org file before content corruption was about 1.5MB.
GNU Emacs 26.3
macOS 10.15.7
Please let me know if I can
On 2021-02-09 09:38, Eric S Fraga wrote:
>On Monday, 8 Feb 2021 at 19:24, Sébastien Miquel wrote:
>> 1. Is anyone experiencing something similar ?
>
>Yes, particularly since I moved to using exwm as my window manager, so
>not necessarily org related. For instance, I find that having doc-view
On Fri, Feb 5, 2021 at 7:33 PM Eric Abrahamsen
wrote:
> Carsten Dominik writes:
>
> > On Fri, Feb 5, 2021 at 11:13 AM Christian Moe
> wrote:
> >
> >>
> >> Tim Cross writes:
> >>
> >> > Eric Abrahamsen writes:
> >> >
> >> >>> Does it actually need a key binding? I've never used it and just use
On Wednesday, 10 Feb 2021 at 22:43, Maxim Nikulin wrote:
> Concerning BIND, there was a topic a month ago that bind
> has to be enabled explicitly. Unsure if it makes parameter available
> early enough however:
My understanding is that it makes it available, i.e. in the sense that
it's simply not
27 matches
Mail list logo
