is-already-stored t)) ;; avoid call to org-store-link
> (setq org-stored-links
> (cons (list url title) org-stored-links))
>
>
> Emacs : GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.30)
> of 2018-07-05
> Package: Org mode version 9.1.14 (9.1.14-1059-g
re-link
(setq org-stored-links
(cons (list url title) org-stored-links))
Emacs : GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.30)
of 2018-07-05
Package: Org mode version 9.1.14 (9.1.14-1059-gadec50-elpaplus @
/home/ionasal/.emacs.d/elpa/org-plus-contrib-20181211/)
Have a question about org-publish-project. I have a bunch of org files
that work fine and I've been able to publish my project to PDF fine, but
I'd like to refine the setting, but I can't find the documentation for
what I want. Basically, I have the following:
(setq org-publish-project-alist
'
On Tue, 11 Dec 2018 01:00:15 +0800 wrote
> Check your ~/.mailcap and/or /etc/mailcap file as well: there are indeed
> many twisty passages through org-open-file, so you may end up calling
> whatever the system has set up (correctly or not).
> Nick
Aha, that was the answer. Apparen
On Tue, Dec 11, 2018 at 8:27 AM Nicolas Goaziou wrote:
> > (((headline (:raw-value "stuff" :begin 17 :end 36 :pre-blank 0
> > :contents-begin 26 :contents-end 36 ...)) 17 35))
>
> `org-element-at-point' ignores narrowing.
Yes, but my issue is with the fact that the entry bounds reported by
org-el
Hello,
Allen Li writes:
> org-map-entries narrows the buffer to narrower than the given entry.
>
> 1. Run: cat > /tmp/tmp.org < * some headline
> ** stuff
> some text
> ** asdf asdf
> EOF
>
> 2. emacs -Q
> 3. M-g M-g 2 RET
> 4. M-: (org-map-entries (lambda () (list (org-element-at-point)
> (poin
Hello,
Jens Lechtenboerger writes:
> Hi there,
>
> given a macro like
>
> #+MACRO: foo (eval (message "%s" $1))
>
> I need to call {{{foo("text")}}} with Org mode 9.1.14-9-g131531-elpa.
>
> On the master branch, that call will include the quotation marks as
> part of the string, so I need to cal
Hello,
Jens Lechtenboerger writes:
> Hi there,
>
> On 2017-11-21, Nicolas Goaziou wrote:
>
>> For the record, I implemented a "keyword" macro (master branch).
>
> That has been in master for over a year now. Are there plans for
> inclusion in a release? (Or did I overlook that?)
master branch
Hi there,
given a macro like
#+MACRO: foo (eval (message "%s" $1))
I need to call {{{foo("text")}}} with Org mode 9.1.14-9-g131531-elpa.
On the master branch, that call will include the quotation marks as
part of the string, so I need to call {{{foo(text)}}} (documented in
the manual, but I did
Hi there,
On 2017-11-21, Nicolas Goaziou wrote:
> For the record, I implemented a "keyword" macro (master branch).
That has been in master for over a year now. Are there plans for
inclusion in a release? (Or did I overlook that?)
Best wishes
Jens
10 matches
Mail list logo