On Thu, Aug 27, 2015 at 6:53 PM, Nicolas Goaziou
wrote:
> Pip Cet writes:
>
> > Could you explain your reasoning for this in some more detail? I use
> > empty headlines + tags (properties, actually) in my "set properties in
> > headlines rather than special drawers&
ave the image unless they telepathically know that "frame"
means "image". "This Object" might be okay, I guess.
My suggestion is to use img for images; that also appears to be the
consensus on Stack Overflow. Let's find a good syntax for including
interactiv
I've used interactive SVGs with ox-html output quite a lot, and I found it
necessary to add the following horrible code; I'm not sure it's still
required:
let svgdoc = object.contentDocument;
let svgid = object.id;
if (!svgdoc) {
if (object.parentNode /* XXX why is this n
On 8/19/15, Nicolas Goaziou wrote:
> Prateek Mehta writes:
>
>> That probably makes sense, though I still feel it is a little
>> inconsistent.
>> One could argue that anything within colons is an org tag (regardless of
>> whether the title is empty), and isn't meant to be exported. It's
>> probab
Hi Eric,
I know this doesn't answer your actual question about nested macro
expansion, but writing some elisp might help you get the TIMESTAMP
property, at least: both
#+MACRO: bubba (eval (org-entry-get nil "TIMESTAMP"))
and
#+MACRO: bubba (eval (org-macro-expand "{{{property(TIMESTAMP)}}}"
org
On 8/19/15, Andreas Leha wrote:
> Thank you for your patch! It seems as it breaks global visibility
> cycling, though.
Sorry about that, I really messed up there. Kaushal's patch should
work better, as long as there is at least one valid heading in the
file (if I try running it on an entirely em
I've had the same problem, and I found it a little hard to find the
right thing in the source code, so maybe this helps: I think what you
want is "(setq create-lockfiles nil)", which doesn't steal the
lockfile but ignores it; if you need to make sure it's stolen, try
overriding `ask-user-about-lock
Hi,
can you confirm the issue only appears when the first line of the
buffer isn't an outline heading? I think it's easy enough to fix then,
and if you like you might want to try the patch I've attached.
It's bugged me for a while that `org-back-to-heading' et al throw
errors when they're used bef
the recursive-whitespace Regular Expressions that Pip Cet mentioned
> are not Emacs freezers in Emacs 25?
>
> On Tue, Aug 18, 2015 at 11:30 AM, Bastien wrote:
>
>> Hi Matthew,
>>
>> I've no problem with the link in hang.org.
>>
>> This is with Org 8.3.1 and Emacs 25.0.50.18.
>>
>> --
>> Bastien
>>
>
Hi Nicolas,
On Thu, Aug 13, 2015 at 11:37 PM, Nicolas Goaziou
wrote:
> Hello,
>
> Pip Cet writes:
>
>> Can you try this patch? That appears to fix the issue here, at least
>> for this one file, at the cost of yet another shy group added to the
>> regular expres
sep)))
(if starred (substring title 1) title))
- sep "*"
+ sep "?"
(org-re "\\(?:[ \t]+:[[:alnum:]_@#%%:]+:\\)?")
"[ \t]*$")))
(goto-char (point-mi
I hesitate to share this code (it's not very pretty right now), but I
have been working on two ideas that I think combine to solve problems
like this in a nicer (and lazier) fashion than the current approach:
headline properties and reverse inheritance.
Headline properties are simply about setting
12 matches
Mail list logo
