Re: [O] Macro question with new texinfo exporter
Hi Achim, Achim Gratz strom...@nexgo.de 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 useful for when you want to create backtraces. ... which is why I always want, but users don't, I agree. Thanks, -- Bastien
Re: [O] Macro question with new texinfo exporter
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-x ! to org-reload-uncompiled or another binding could be found. BTW, I just see that the menu entry for loading org uncompiled is wrong, it still tries to run it via C-u C-c C-x r, which isn't bound anymore since Org 6.26d due to a conflict with bindings in other modes. Looks like nobody ever used this in the last four years… fixed in maint and merged to master. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Waldorf MIDI Implementation additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] Macro question with new texinfo exporter
Achim Gratz strom...@nexgo.de 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 anyone so inclined to map C-c C-x ! to org-reload-uncompiled or another binding could be found. I don't think this is necessary, C-u C-c C-x ! is easy enough. BTW, I just see that the menu entry for loading org uncompiled is wrong, it still tries to run it via C-u C-c C-x r, which isn't bound anymore since Org 6.26d due to a conflict with bindings in other modes. Looks like nobody ever used this in the last four years… fixed in maint and merged to master. Thanks for fixing this! PS: I wonder if *any* of the menu item is used... as I don't use the menu myself, it's hard to tell. -- Bastien
Re: [O] Macro question with new texinfo exporter
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 tables, so I guess the menu gets good use by other new users of Org (just that apparently none of them tries to reload Org uncompiled). Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Macro question with new texinfo exporter
Achim Gratz strom...@nexgo.de 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 often used the menu to do things in tables, so I guess the menu gets good use by other new users of Org (just that apparently none of them tries to reload Org uncompiled). Related to this -- how do you folks handle multiple local git branches? Do you always run uncompiled, and follow every git checkout with org-reload? I've caught myself several times recently doing git checkouts and reloading, but of course still reloading the byte-compiled files from the previous branch
Re: [O] Macro question with new texinfo exporter
Bastien b...@altern.org 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 got into my finger memory. The menu is a useful crutch for me in those cases: I use the menu the first time, put the key chord into short-term memory and forget about it as soon as I'm done. Two weeks later, I start from scratch :-) Nick Footnotes: [fn:1] An imprecise term, but for me that means less often than once a week. YMMV. And as one gets older, that mileage changes - DAMHIKT :-)
Re: [O] Macro question with new texinfo exporter
Eric Abrahamsen e...@ericabrahamsen.net wrote: Achim Gratz strom...@nexgo.de 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 often used the menu to do things in tables, so I guess the menu gets good use by other new users of Org (just that apparently none of them tries to reload Org uncompiled). Related to this -- how do you folks handle multiple local git branches? Do you always run uncompiled, and follow every git checkout with org-reload? I've caught myself several times recently doing git checkouts and reloading, but of course still reloading the byte-compiled files from the previous branch I don't trust org-reload enough for that: I write[fn:1] a minimal .emacs that does whatever it needs to do to get me to the problem as fast as possible and start a new emacs (emacs -q -l /path/to/minimal.emacs ...) Nick Footnotes: [fn:1] Write is a bit of an exaggeration: I have a standard one that I copy and modify for my current needs. When I'm done, I throw it away.
Re: [O] Macro question with new texinfo exporter
Nick Dokos nicholas.do...@hp.com wrote: Eric Abrahamsen e...@ericabrahamsen.net wrote: Achim Gratz strom...@nexgo.de 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 often used the menu to do things in tables, so I guess the menu gets good use by other new users of Org (just that apparently none of them tries to reload Org uncompiled). Related to this -- how do you folks handle multiple local git branches? Do you always run uncompiled, and follow every git checkout with org-reload? I've caught myself several times recently doing git checkouts and reloading, but of course still reloading the byte-compiled files from the previous branch I don't trust org-reload enough for that: I write[fn:1] a minimal .emacs that does whatever it needs to do to get me to the problem as fast as possible and start a new emacs (emacs -q -l /path/to/minimal.emacs ...) I do ``make clean'' early and often too...
Re: [O] Macro question with new texinfo exporter
Nick Dokos nicholas.do...@hp.com writes: Bastien b...@altern.org 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 got into my finger memory. The menu is a useful crutch for me in those cases: I use the menu the first time, put the key chord into short-term memory and forget about it as soon as I'm done. Two weeks later, I start from scratch :-) Nick Footnotes: [fn:1] An imprecise term, but for me that means less often than once a week. YMMV. And as one gets older, that mileage changes - DAMHIKT :-) My experience resembles Nick's. The menus save me lots of time. I'm not sure what DAMHIKT means, but there is no doubt that mileage changes with age. The term key chord puzzled me for a long time, until a colleague pointed out that it is possible to play a computer running Emacs, just like playing a piano. I was stunned! All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Macro question with new texinfo exporter
Nicolas Goaziou n.goaz...@gmail.com writes:
Bastien b...@altern.org 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.
I need a bit more help with this. I created a tracking branch for
maint:
git branch --track maint origin/maint
Then, I checkout maint:
git checkout maint
Reloading Org yields these messages:
The following features were found in load-path, please check if that's correct:
(org-e-texinfo org-export)
Some error occured while reloading Org features
(ob-core ob-tcl)
Please check *Messages*!
Org-mode version 7.9.3e (7.9.3e @ /Users/dk/.emacs.d/src/org-mode/lisp/)
cond: Symbol's function definition is void: org-e-latex-export-to-latex
I'm stymied here. I'd like to be able to use the new macro code with
the new exporter. How is that possible?
All the best,
Tom
--
T.S. Dye Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
Re: [O] Macro question with new texinfo exporter
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. Achim, any objection of making it the default, while C-u M-x org-reload RET would reload compiled files if any? -- Bastien
Re: [O] Macro question with new texinfo exporter
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Bastien b...@altern.org 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.
I need a bit more help with this. I created a tracking branch for
maint:
git branch --track maint origin/maint
Then, I checkout maint:
git checkout maint
Reloading Org yields these messages:
The following features were found in load-path, please check if that's
correct:
(org-e-texinfo org-export)
Some error occured while reloading Org features
(ob-core ob-tcl)
Please check *Messages*!
Org-mode version 7.9.3e (7.9.3e @ /Users/dk/.emacs.d/src/org-mode/lisp/)
cond: Symbol's function definition is void: org-e-latex-export-to-latex
I'm stymied here. I'd like to be able to use the new macro code with
the new exporter. How is that possible?
The experimental exporter can be found in master branch. The maint
branch has a very old version which is unusable.
I pushed the fix to maint because it was about Elements, not directly
the exporter.
Regards,
--
Nicolas Goaziou
Re: [O] Macro question with new texinfo exporter
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 install location and then just do a make up2 or something similar whenever you want to update. Reloading Org yields these messages: The following features were found in load-path, please check if that's correct: (org-e-texinfo org-export) So did you check that those features were found in the right place? Some error occured while reloading Org features (ob-core ob-tcl) Please check *Messages*! 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/.emacs.d/src/org-mode/lisp/) cond: Symbol's function definition is void: org-e-latex-export-to-latex I'm stymied here. I'd like to be able to use the new macro code with the new exporter. How is that possible? Just update master. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
Re: [O] Macro question with new texinfo exporter
Nicolas Goaziou n.goaz...@gmail.com 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 confused me. All the best, Tom -- T.S. Dye Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
Re: [O] Macro question with new texinfo exporter
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 defaut behavior of org-reload. Achim, any objection of making it the default, while C-u M-x org-reload RET would reload compiled files if any? I think that the current default, which has been in place for years, is just fine. Reloading uncompiled is only useful for when you want to create backtraces. If you always want to run uncompiled, then you can opt to never compile Org and org-reload will follow suit, if you clean up load-path to not contain older (compiled) Org distributions: --8---cut here---start-8--- (setq load-path (delq nil (mapcar (lambda (p) (when (not (string-match lisp/org$ p)) p)) load-path))) (add-to-list 'load-path /path/to/uncompiled/org) (load org-loaddefs.el nil nil 'nosuffix) --8---cut here---end---8--- Of course you should not do this after Org has already been loaded. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf Blofeld V1.15B11: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Macro question with new texinfo exporter
Aloha Achim, Achim Gratz strom...@nexgo.de 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/.emacs.d/src/org-mode/lisp/) cond: Symbol's function definition is void: org-e-latex-export-to-latex I'm stymied here. I'd like to be able to use the new macro code with the new exporter. How is that possible? Just update master. Thanks for looking into this. Yes, this was my confusion. I didn't understand that maint was merged with master. I thought Nicolas' reference to maint was an indication that I had to use the new code there. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Macro question with new texinfo exporter
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com 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 change must appear, 8.0 is a good timing, I agree. 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? -- Bastien
Re: [O] Macro question with new texinfo exporter
Bastien b...@altern.org 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 fine. However, it should be possible to escape backslashes, as \\, is different from \,. I'll have a look at it a bit later. Regards, -- Nicolas Goaziou
Re: [O] Macro question with new texinfo exporter
Bastien b...@altern.org 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,
--
Nicolas Goaziou
Re: [O] Macro question with new texinfo exporter
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com 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 why I prefer the parentheses is that it makes
clear for newbies that the items within the parentheses
are arguments, whereas I find it less clear with no
parentheses.
--
Bastien
Re: [O] Macro question with new texinfo exporter
Hello,
Bastien b...@altern.org 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:
- if it is a comma, use old syntax
- in any other case, use new syntax.
The reason why I prefer the parentheses is that it makes
clear for newbies that the items within the parentheses
are arguments, whereas I find it less clear with no
parentheses.
Write more Lisp ;)
Regards,
--
Nicolas Goaziou
Re: [O] Macro question with new texinfo exporter
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com 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 the parentheses is that it makes clear for newbies that the items within the parentheses are arguments, whereas I find it less clear with no parentheses. Write more Lisp ;) (You mean... I should (perhaps) write less lisp (right)?) -- Bastien
Re: [O] Macro question with new texinfo exporter
Bastien b...@altern.org writes: Nicolas Goaziou n.goaz...@gmail.com 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 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 ? Regards, -- Nicolas Goaziou
Re: [O] Macro question with new texinfo exporter
Nicolas Goaziou n.goaz...@gmail.com writes: Bastien b...@altern.org writes: Nicolas Goaziou n.goaz...@gmail.com 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 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 ? Perhaps make macro expansion conditional on old/new exporter, rather than the form of the macro? Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Macro question with new texinfo exporter
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: consp, nil):
{{{kbd(C-,)}}}
and so does this:
{{{kbd(C-\,)}}}
In fact, any number of backslashes appears to trigger the same error.
I'm hoping to find @kbd{C-,} in the .texi output.
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}}}
Regards,
--
Nicolas Goaziou
Re: [O] Macro question with new texinfo exporter
Nicolas Goaziou n.goaz...@gmail.com 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-,)}}}? That would be
easy on my end.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
[O] Macro question with new texinfo exporter
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:
{{{kbd(C-\,)}}}
In fact, any number of backslashes appears to trigger the same error.
I'm hoping to find @kbd{C-,} in the .texi output.
All the best,
Tom
--
T.S. Dye Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
