Re: [O] texinfo export of @@

2012-12-08 Thread Thomas S. Dye
Aloha Jon,

Jonathan Leech-Pepin jonathan.leechpe...@gmail.com writes:

 Hello Tom,

 On Dec 7, 2012 3:35 PM, Thomas S. Dye t...@tsdye.com wrote:

 Aloha Jon,

 With this macro:

 #+MACRO: code @@info:@code{$1}@@

 this Org source:

  {{{code([@@b])}}}

 is exported as:

  @code{[b]@}.

 Any idea how to get @code{[@@b]} instead?

 You should be able to simply use ~@@b~ to create @code blocks

Yes, thanks for this advice.  It works much better.

All the best,
Tom

 Regards,
 Jon
 Hello Tom, 

 On Dec 7, 2012 3:35 PM, Thomas S. Dye t...@tsdye.com wrote:

 Aloha Jon,

 With this macro:

 #+MACRO: code @@info:@code{$1}@@

 this Org source:

  {{{code([@@b])}}}

 is exported as:

  @code{[b]@}.

 Any idea how to get @code{[@@b]} instead?

 You should be able to simply use ~@@b~ to create @code blocks


 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


 Regards,
 Jon


-- 
Thomas S. Dye
http://www.tsdye.com



[O] texinfo export of @@

2012-12-07 Thread Thomas S. Dye
Aloha Jon,

With this macro:

#+MACRO: code @@info:@code{$1}@@

this Org source:

 {{{code([@@b])}}}

is exported as:

 @code{[b]@}.

Any idea how to get @code{[@@b]} instead?

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] texinfo export of @@

2012-12-07 Thread Jonathan Leech-Pepin
Hello Tom,

On Dec 7, 2012 3:35 PM, Thomas S. Dye t...@tsdye.com wrote:

 Aloha Jon,

 With this macro:

 #+MACRO: code @@info:@code{$1}@@

 this Org source:

  {{{code([@@b])}}}

 is exported as:

  @code{[b]@}.

 Any idea how to get @code{[@@b]} instead?

You should be able to simply use ~@@b~ to create @code blocks


 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


Regards,
Jon


[O] texinfo export advice

2012-12-05 Thread Thomas S. Dye
Aloha all,

I'm trying to find a good Org representation for a common construct in
org.texi and need some help.

Here is the construct in org.texi:

@table @asis
@orgcmd{C-u C-u @key{TAB},org-set-startup-visibility}
Switch back to the startup visibility of the buffer, i.e.: whatever is
requested by startup options and @samp{VISIBILITY} properties in individual
entries.
@end table

It displays a key command and the Org function that it runs, then has a
description of the function.  In the info manual it looks like this:

`C-u C-u TAB' (`org-set-startup-visibility')
 Switch back to the startup visibility of the buffer, i.e.:
 whatever is requested by startup options and `VISIBILITY'
 properties in individual entries.

I can export this with the texinfo exporter with a lot of wrapping:

@@info:@table @asis@@
@@info:@orgcmd{C-u C-u @key{TAB},org-set-startup-visibility}@@
Switch back to the startup visibility of the buffer, i.e.: whatever is
requested by startup options and @@info:@samp{VISIBILITY}@@ properties in 
individual
entries.
@@info:@end table@@

This is fine, but the Org mode buffer doesn't look much like Org mode
after a few of these.

My idea is to use a description list, like so:

  - @@info:@orgcmd{C-u C-u @key{TAB},org-set-startup-visibility}@@ ::
   Switch back to the startup visibility of the buffer, i.e.:
   whatever is requested by startup options and
   @@info:@samp{VISIBILITY}@@ properties in individual entries.

This almost works.  However, it inserts an @index command that gets in
the way:

@table @samp
@item @orgcmd{C-u C-u @key{TAB},org-set-startup-visibility}
Switch back to the startup visibility of the buffer, i.e.:
whatever is requested by startup options and
@samp{VISIBILITY} properties in individual entries.

@end table

This is the view from info:

`

`C-u C-u TAB (`org-set-startup-visibility')'
 '
 Switch back to the startup visibility of the buffer, i.e.:
 whatever is requested by startup options and `VISIBILITY'
 properties in individual entries.

Note the extra open and close quotes and newlines.

I'm thinking something like this might be a useful addition:

#+attr_texinfo :item nil
  - @@info:@orgcmd{C-u C-u @key{TAB},org-set-startup-visibility}@@ ::
   Switch back to the startup visibility of the buffer, i.e.:
   whatever is requested by startup options and
   @@info:@samp{VISIBILITY}@@ properties in individual entries.

Ideas?

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