Nick Dokos writes:
> Bastien wrote:
>
>> PS: I wonder if *any* of the menu item is used... as I don't use the
>> menu myself, it's hard to tell.
>>
>
> I do: there are many things I use rarely[fn:1] (e.g. archiving, drawers,
> properties, even marking TODOs outside the agenda: was that C-c t or
Nick Dokos wrote:
> Eric Abrahamsen wrote:
>
> > Achim Gratz writes:
> >
> > > Bastien writes:
> > >> PS: I wonder if *any* of the menu item is used... as I don't use the
> > >> menu myself, it's hard to tell.
> > >
> > > These days I only ever use it for "Show All" which does have a menu
> >
Eric Abrahamsen wrote:
> Achim Gratz writes:
>
> > Bastien writes:
> >> PS: I wonder if *any* of the menu item is used... as I don't use the
> >> menu myself, it's hard to tell.
> >
> > These days I only ever use it for "Show All" which does have a menu
> > entry, but no key binding. But befor
Bastien wrote:
> PS: I wonder if *any* of the menu item is used... as I don't use the
> menu myself, it's hard to tell.
>
I do: there are many things I use rarely[fn:1] (e.g. archiving, drawers,
properties, even marking TODOs outside the agenda: was that C-c t or C-c
C-t now?) that I have not g
Achim Gratz writes:
> Bastien writes:
>> PS: I wonder if *any* of the menu item is used... as I don't use the
>> menu myself, it's hard to tell.
>
> These days I only ever use it for "Show All" which does have a menu
> entry, but no key binding. But before I got used to where the keys are
> I of
Bastien writes:
> PS: I wonder if *any* of the menu item is used... as I don't use the
> menu myself, it's hard to tell.
These days I only ever use it for "Show All" which does have a menu
entry, but no key binding. But before I got used to where the keys are
I often used the menu to do things in
Achim Gratz writes:
> Bastien writes:
>>> Reloading uncompiled is only useful for when you want to
>>> create backtraces.
>>
>> ... which is why I always want, but users don't, I agree.
>
> We could provide org-reload-uncompiled that calls org-reload with a
> prefix argument, which would allow
Bastien writes:
>> Reloading uncompiled is only useful for when you want to
>> create backtraces.
>
> ... which is why I always want, but users don't, I agree.
We could provide org-reload-uncompiled that calls org-reload with a
prefix argument, which would allow anyone so inclined to map "C-c C-
Hi Achim,
Achim Gratz writes:
> I don't see the relation to the original problem, which is caused by a
> switch from master to maint.
Yes, I realized this.
> I think that the current default, which has been in place for years, is
> just fine.
Fair enough.
> Reloading uncompiled is only use
Aloha Achim,
Achim Gratz writes:
>
> What were those messages? And since the presence of both features
> indicates that you were previously on master, why did you switch to
> maint at all (everything on maint should have been merged into master)?
>
>> Org-mode version 7.9.3e (7.9.3e @ /Users/dk/
Bastien writes:
> You need to reload uncompiled files with C-u M-x org-reload RET
I don't see the relation to the original problem, which is caused by a
switch from master to maint. This will not work without at least
unloading Org or better, restarting Emacs.
> BTW, I think it should be the def
Nicolas Goaziou writes:
>
> I pushed the fix to maint because it was about Elements, not directly
> the exporter.
Oh, I see now. You pushed the fix to maint, then merged branch 'maint'
with master, so the fix is there as well. I didn't understand the
workflow, so the reference to maint confuse
Thomas S. Dye writes:
> Then, I checkout maint:
>
> git checkout maint
I'm not sure what your starting point is, but you'd almost certainly
will want to create the correct autoloads. In fact, you'd have a much
better chance of this working correctly if you took the time (just once)
to set up an i
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou writes:
>
>> Bastien writes:
>>
>>> Now back to the issue at hand, what about simply allowing to escape
>>> the , and " characters? This was Thomas first try, and a natural one
>>> I'd say.
>>
>> I have pushed a fix in maint for t
Hi Thomas,
t...@tsdye.com (Thomas S. Dye) writes:
> I'm stymied here. I'd like to be able to use the new macro code with
> the new exporter. How is that possible?
You need to reload uncompiled files with C-u M-x org-reload RET
BTW, I think it should be the defaut behavior of org-reload.
Achi
Nicolas Goaziou writes:
> Bastien writes:
>
>> Now back to the issue at hand, what about simply allowing to escape
>> the , and " characters? This was Thomas first try, and a natural one
>> I'd say.
>
> I have pushed a fix in maint for that. It should now be possible to use
> {{{kbd(C-\,)}}} to
Bastien writes:
> Now back to the issue at hand, what about simply allowing to escape
> the , and " characters? This was Thomas first try, and a natural one
> I'd say.
I have pushed a fix in maint for that. It should now be possible to use
{{{kbd(C-\,)}}} to get "C-," as argument.
Regards,
-
Bastien writes:
> Now back to the issue at hand, what about simply allowing to escape
> the , and " characters? This was Thomas first try, and a natural one
> I'd say.
>
> What do you think?
In this case, there's no point in allowing to escape quotation marks.
The current syntax handles them fi
Hi Nicolas,
Nicolas Goaziou writes:
> OTOH, the change will happen during a major release. Moreover macros
> belong to an export framework which have been totally rewritten. Must we
> cope with backward compatibility in this case ?
I'd say "as much as we can", yes. But if an incompatible chang
Nicolas Goaziou writes:
> Bastien writes:
>
>> Nicolas Goaziou writes:
>>
>>> Supporting old syntax is a bit tricky. Perhaps something like:
>>>
>>> - Find the first one to appear between comma and quote:
>>> - if it is a comma, use old syntax
>>> - in any other case, use new syntax.
Bastien writes:
> Nicolas Goaziou writes:
>
>> Supporting old syntax is a bit tricky. Perhaps something like:
>>
>> - Find the first one to appear between comma and quote:
>> - if it is a comma, use old syntax
>> - in any other case, use new syntax.
>
> Sounds good to me.
OTOH, the ch
Hi Nicolas,
Nicolas Goaziou writes:
> Supporting old syntax is a bit tricky. Perhaps something like:
>
> - Find the first one to appear between comma and quote:
> - if it is a comma, use old syntax
> - in any other case, use new syntax.
Sounds good to me.
>> The reason why I prefer t
Hello,
Bastien writes:
> FWIW I'm all for a variation of this
>
> {{{name(arg1 "arg2 with space" "arg3 \"with\" quote")}}}
>
> if we can also support the old syntax.
Supporting old syntax is a bit tricky. Perhaps something like:
- Find the first one to appear between comma and quote:
- i
Hi Nicolas,
Nicolas Goaziou writes:
> We ought to modify it. Perhaps something like:
>
> {{{name arg1 "arg2 with space" "arg3 \"with\" quote"}}}
FWIW I'm all for a variation of this
{{{name(arg1 "arg2 with space" "arg3 \"with\" quote")}}}
if we can also support the old syntax.
The reason w
Nicolas Goaziou writes:
>
> I didn't try it, but it probably comes from the syntax of macros, which
> is a bit brittle wrt commas.
>
> We ought to modify it. Perhaps something like:
>
> {{{name arg1 "arg2 with space" "arg3 \"with\" quote"}}}
So, with the modification, I'd write {{{kbd("C-,")}}
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> I have the following two macros:
>
> #+MACRO: markup @@info:@$1{@@$2@@info:}@@
> #+MACRO: kbd {{{markup(kbd,$1)}}}
>
> When I export to texinfo using the new exporter, the following macro
> call triggers an error (byte-code: Wrong type argument: con
Aloha all,
I have the following two macros:
#+MACRO: markup @@info:@$1{@@$2@@info:}@@
#+MACRO: kbd {{{markup(kbd,$1)}}}
When I export to texinfo using the new exporter, the following macro
call triggers an error (byte-code: Wrong type argument: consp, nil):
{{{kbd(C-,)}}}
and so does this:
{{
27 matches
Mail list logo
