Re: [O] simple way to call `C-c a v' or a way to bind it to a key?

2014-02-16 Thread Yasushi SHOJI
Hi Thorsten,

At Sat, 15 Feb 2014 18:34:07 +0100,
Thorsten Jolitz wrote:
 
 so instead of binding the dispatcher function to a global key you can
 bind one or more of the specific functions, e.g.
 
 ,
 | (global-set-key (kbd f12) 'org-agenda-list)
 `

I thought simply binding `org-agenda-list' to a key does not work in
the case with custome agenda setup.

But, it turns out that it's as simple as the following:

(defun yashi/org-agenda (optional arg)
  (interactive P)
  (org-agenda arg a))

(global-set-key (kbd f1) 'yashi/org-agenda)

Thanks,
-- 
 yashi



Re: [O] parser: verbatim or code?

2014-02-16 Thread Yasushi SHOJI
Hi,

At Sat, 15 Feb 2014 09:23:41 -0500,
Nick Dokos wrote:
 
 I think it's a code bug: ~verbatim~ is the precedent-setting latex
 convention.
 
 However fixing it might break existing documents (although in many
 instances code and verbatim are treated equivalently, so that might
 not be much of a problem).

A quick grep on export back-ends reveals that some back-ends uses them
differently. Namely

 - latex
 - man
 - org ;-)
 - texinfo

Should I just leave as-is?
-- 
   yashi



Re: [O] Sub-totals

2014-02-16 Thread Michael Brand
Hi Cecil

On Sat, Feb 15, 2014 at 6:14 PM, Cecil Westerhof cldwester...@gmail.com wrote:
 - I would like to have only the last element of the range filled.

I always thought that this would not be possible with reasonable
effort. Your question made me think again and it is possible, now I
can change my own use cases with sub-total :-) . See docstring and
take the procedure with vlen etc. from the TBLFM of the new ERT
test-org-table/sub-total here:
http://orgmode.org/w/org-mode.git?p=org-mode.git;a=blob;f=testing/lisp/test-org-table.el

Or read the docstring there and just take this copy that I used to
build the ERT:
|---+---+---|
| Item  |  Item |  Sub- |
| name  | value | total |
|---+---+---|
| a1|   4.1 |   |
| a2|   8.2 |   |
| a3|   |  12.3 |
|---+---+---|
| b1|  16.0 |  16.0 |
|---+---+---|
| c1|32 |   |
| c2|64 |  96.0 |
|---+---+---|
| Total | 124.3 |   |
|---+---+---|
#+TBLFM: @$2 = vsum(@II..@) :: $3 = if(vlen(@-I$2..@0$2) ==
vlen(@-I$2..@+I$2), vsum(@-I$2..@+I$2) +.0, string()); EN f-1 ::
@$3 = string()

Michael



Re: [O] [patch] Support CUSTOM_ID property in latex export

2014-02-16 Thread Nicolas Goaziou
Hello,

Richard Lawrence richard.lawre...@berkeley.edu writes:

 1) Sometimes I need to refer to a section from within an embedded LaTeX
 block.  In that case, I need to know the appropriate label to use at the
 LaTeX level, not just in Org.  For example:

 * A headline
   :PROPERTIES:
   :CUSTOM_ID: sec:a-headline
   :END:

 # ... stuff ...

 #+BEGIN_LATEX
 % ... more stuff ...
 (see section~\ref{sec:a-headline})
 #+END_LATEX

I don't think this is a good idea, as the character set allowed in
\label{...} macros is only a subset of the character set allowed in
custom id value. Hence the `org-export-solidify-link-text' function.

If you are cautious, this will not be a problem, but it could bite users
with little LaTeX knowledge.

 This is not possible with the present section labeling in LaTeX export,
 because I have no way of forcing Org to use a particular label for a
 section.

  * A headline
#+latex: \label{my-section}

#+BEGIN_LATEX
% ... more stuff ...
(see section~\ref{my-section})
#+END_LATEX

It also seems more consistent to me: since you want to explicitly write
the \ref{...}, you are also expected to explicitly write the \label{...}
part.

 2) I hope this doesn't happen, but there may come a time when I need to
 move away from Org and just use straight LaTeX.  Having control over the
 labeling will make this transition much easier, because it means I won't
 have to worry about manually changing the labels in a long document from
 Org's default sec-... numbering to my own semantic labels.

See above. You can even automate that with a hook (i.e., get the custom
id value and add a corresponding label at the beginning of the
headline).

 3) This will make the LaTeX exporter's behavior more consistent with the
 HTML exporter's behavior.  The HTML exporter will use CUSTOM_ID if it is
 supplied to construct the id attributes of headlines and divs.  If
 someone is relying on this behavior of the HTML exporter, they might be
 unpleasantly surprised by the LaTeX exporter's behavior.

One relying on an implementation detail instead of the actual
specifications has to be prepared for surprises.

What do you think?


Regards,

-- 
Nicolas Goaziou



Re: [O] parser: verbatim or code?

2014-02-16 Thread Nicolas Goaziou
Hello,

Yasushi SHOJI ya...@atmark-techno.com writes:

 Nick Dokos wrote:
 
 I think it's a code bug: ~verbatim~ is the precedent-setting latex
 convention.
 
 However fixing it might break existing documents (although in many
 instances code and verbatim are treated equivalently, so that might
 not be much of a problem).

 A quick grep on export back-ends reveals that some back-ends uses them
 differently. Namely

  - latex
  - man
  - org ;-)
  - texinfo

 Should I just leave as-is?

If we leave it as-is, documentation needs to be updated anyway.

If we do change them, it should only happen in org-element.el. I don't
think that would break existing documents, as code and verbatim are
really close to each other.

I don't care either way. Though, I lean towards the first option, as
I like = as verbatim (which may be the source of the initial
confusion).


Regards,

-- 
Nicolas Goaziou



Re: [O] Best way to generate textile from orgmode ?

2014-02-16 Thread Yasushi SHOJI
Hi Marc,

# way too late to reply but...

At Thu, 11 Apr 2013 22:11:49 +0200,
Marc-Oliver Ihm wrote:
 
 i would like to convert orgmode to textile (which is used within confluence 
 wiki).

I was hoping that someone's gonna beat me to it. but hey, it's much
fun to write elisp than textile (it's redmine in my case ;-p).

https://github.com/yashi/org-textile

Only some basic formats are supported right now, but quite useful for
me, at least.  Hope it is as well for you.

It's also in melpa, thanks to @purcell.

Best,
-- 
yashi



Re: [O] parser: verbatim or code?

2014-02-16 Thread Michael Brand
Hi Nicolas

On Sun, Feb 16, 2014 at 10:20 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:
 If we leave it as-is, documentation needs to be updated anyway.

 If we do change them, it should only happen in org-element.el. I don't
 think that would break existing documents, as code and verbatim are
 really close to each other.

 I don't care either way. Though, I lean towards the first option, as
 I like = as verbatim (which may be the source of the initial
 confusion).

When I read org-element-text-markup-successor

((equal marker ~) 'code)
((equal marker =) 'verbatim)

it confuses me because of the well known Org manual

You can make words *bold*, /italic/, _underlined_, =code= and
~verbatim~

Michael



Re: [O] parser: verbatim or code?

2014-02-16 Thread Nicolas Goaziou
Hello,

Michael Brand michael.ch.br...@gmail.com writes:

 When I read org-element-text-markup-successor

 ((equal marker ~) 'code)
 ((equal marker =) 'verbatim)

 it confuses me because of the well known Org manual

 You can make words *bold*, /italic/, _underlined_, =code= and
 ~verbatim~

Indeed, that's the very issue we're discussing in this thread.

I'm not sure to understand what you mean here.


Regards,

-- 
Nicolas Goaziou



Re: [O] Org not preserving Python indent levels on LaTex export due to tabs

2014-02-16 Thread Nicolas Goaziou
Hello,

Samuel Wales samolog...@gmail.com writes:

 i can't seem to find the -i flag in the manual.  perhaps i used the
 wrong search term?  i looked in literal examples and in working with
 source code.  i am using maint.

Indeed. It doesn't appear in the manual.

I don't use it. Maybe Someone using it can provide a patch for it.

 also:

   - is there another flag to set org-src-preserve-indentation to nil?
   - will -i still work if org-src.preserve-indentation is t?

No.

 i'd be happy with a fixed 2-space indentation, but that is not
 possible in current org.  i find org-src-preserve-indentation to cause
 more issues than it improves, so i am going to transition to it being
 t, which feels safer even though it is not the default and does not
 have the 2 spaces.

FWIW, I'm happy with `org-src-preserve-indentation' set to nil.

Anyway, if you think `org-src-preserve-indentation' needs improvement,
please provide a description (or ECM) of what you expect it to do.


Regards,

-- 
Nicolas Goaziou



Re: [O] parser: verbatim or code?

2014-02-16 Thread Michael Brand
Hi Nicolas

On Sun, Feb 16, 2014 at 11:00 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:
 Indeed, that's the very issue we're discussing in this thread.

 I'm not sure to understand what you mean here.

For me it was not explicit enough that this

((equal marker ~) 'code)
((equal marker =) 'verbatim)

is the part discussed.

I am not sure if it is that simple but just from the word code and
from the usage on Worg I tend to conclude that for inline code
snippets 'code should be preferred and 'verbatim only be used for
non-code things more similar to just like an inline quote. Only if
this distinction should really matter then keeping the above code
unchanged and changing the Org manual from =code= ~verbatim~ to ~code~
=verbatim= would have the following advantage:

The syntax for inline code snippets seems easier to read by human and
to parse with ~ than with = because inline code snippets use ~
less often than =. I avoid ~/ by using $HOME/ in my notes about
shell and shell scripts. Some examples:

Bla ~a = 1~ bla,
bla ~b=2~ bla,
bla ~local my_variable= # Bash shell: Set to empty value.~ bla,
bla ~source $HOME/.profile~ bla.

vs.

Bla =a = 1= bla,
bla =b=2= bla,
bla =local my_variable= # Bash shell: Set to empty value.= bla,
bla =source $HOME/.profile= bla.

Michael



[O] Use date in Easy Templates?

2014-02-16 Thread Rainer M Krug
Hi

is it possible to insert the actual date into Easy Templates?

Thanks,

Rainer


-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug



signature.asc
Description: OpenPGP digital signature


[O] Header in column view?

2014-02-16 Thread Rainer M Krug
Hi

is it possible to get the header into the column view of org, as it is
replaced by the columns (which is nice, but in my case I would like to
be able to have it in the column view)?

Cheers,

Rainer
-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug



signature.asc
Description: OpenPGP digital signature


Re: [O] Use date in Easy Templates?

2014-02-16 Thread Nick Dokos
Rainer M Krug rai...@krugs.de writes:

 is it possible to insert the actual date into Easy Templates?


No - but it's not difficult to crib the %file code and add %date:

--8---cut here---start-8---
(defun org-complete-expand-structure-template (start cell)
  Expand a structure template.
  (let* ((musep (org-bound-and-true-p org-mtags-prefer-muse-templates))
 (rpl (nth (if musep 2 1) cell))
 (ind ))
(delete-region start (point))
(when (string-match \\`#\\+ rpl)
  (cond
   ((bolp))
   ((not (string-match \\S- (buffer-substring (point-at-bol) (point
(setq ind (buffer-substring (point-at-bol) (point
   (t (newline
(setq start (point))
(if (string-match %file rpl)
(setq rpl (replace-match
   (concat
\
(save-match-data
  (abbreviate-file-name (read-file-name Include file: )))
\)
   t t rpl)))
;;; ADDED CODE
(if (string-match %date rpl)
(setq rpl (replace-match
(save-match-data
  (format-time-string %Y-%m-%d (current-time)))
   t t rpl)))
;;; END OF ADDED CODE
(setq rpl (mapconcat 'identity (split-string rpl \n)
 (concat \n ind)))
(insert rpl)
(if (re-search-backward \\? start t) (delete-char 1

--8---cut here---end---8---

However, the next thing somebody will ask is a different format for the
date which will require YACV[fn:1]. But maybe one exists already?

And the next thing is more of these %thingies... so it would be better
to add yet another layer to the function, so that arbitrary %thingies
can be added by customizing YACV, probably an alist of 

 (thingie . thingie-function)

pairs...

Footnotes:

[fn:1] Yet Another Customization Variable :-)

-- 
Nick




Re: [O] Header in column view?

2014-02-16 Thread Nick Dokos
Rainer M Krug rai...@krugs.de writes:

 is it possible to get the header into the column view of org, as it is
 replaced by the columns (which is nice, but in my case I would like to
 be able to have it in the column view)?


I don't know much about column view, which might explain why I don't
understand your question. But you might want to add some detail, maybe
even an example. The best I can do right now is that you want the
heading (the %ITEM) to precede the corresponding row in the table.

E.g. in the following org file

--8---cut here---start-8---
#+COLUMNS: %25ITEM %FOO %BAR
* H1
  :PROPERTIES:
  :FOO:  foo
  :BAR:  bar
  :END:

* H2
  :PROPERTIES:
  :BAR:  bar2
  :FOO:  foo2
  :END:


* Capture

#+BEGIN: columnview :hlines 1 :id global
| ITEM  | FOO  | BAR  |
|---+--+--|
| * H1  | foo  | bar  |
|---+--+--|
| * H2  | foo2 | bar2 |
|---+--+--|
| * Capture |  |  |
#+END:
--8---cut here---end---8---

do you want the table to appear like this?

| ITEM  | FOO  | BAR  |
|---+--+--|
* H1
| * H1  | foo  | bar  |
|---+--+--|
*H2
| * H2  | foo2 | bar2 |
|---+--+--|
| * Capture |  |  |

-- 
Nick




Re: [O] Header in column view?

2014-02-16 Thread Rainer M Krug


On 02/16/14, 19:39 , Nick Dokos wrote:
 Rainer M Krug rai...@krugs.de writes:
 
 is it possible to get the header into the column view of org, as it is
 replaced by the columns (which is nice, but in my case I would like to
 be able to have it in the column view)?

 
 I don't know much about column view, which might explain why I don't
 understand your question. But you might want to add some detail, maybe
 even an example. The best I can do right now is that you want the
 heading (the %ITEM) to precede the corresponding row in the table.

%ITEM is exactly what I was looking for.

Thanks,

Rainer

 
 E.g. in the following org file
 
 --8---cut here---start-8---
 #+COLUMNS: %25ITEM %FOO %BAR
 * H1
   :PROPERTIES:
   :FOO:  foo
   :BAR:  bar
   :END:
 
 * H2
   :PROPERTIES:
   :BAR:  bar2
   :FOO:  foo2
   :END:
 
 
 * Capture
 
 #+BEGIN: columnview :hlines 1 :id global
 | ITEM  | FOO  | BAR  |
 |---+--+--|
 | * H1  | foo  | bar  |
 |---+--+--|
 | * H2  | foo2 | bar2 |
 |---+--+--|
 | * Capture |  |  |
 #+END:
 --8---cut here---end---8---
 
 do you want the table to appear like this?
 
 | ITEM  | FOO  | BAR  |
 |---+--+--|
 * H1
 | * H1  | foo  | bar  |
 |---+--+--|
 *H2
 | * H2  | foo2 | bar2 |
 |---+--+--|
 | * Capture |  |  |
 

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug



signature.asc
Description: OpenPGP digital signature


Re: [O] Use date in Easy Templates?

2014-02-16 Thread Rainer M Krug


On 02/16/14, 19:08 , Nick Dokos wrote:
 Rainer M Krug rai...@krugs.de writes:
 
 is it possible to insert the actual date into Easy Templates?


That's what I thought as well.

 
 No - but it's not difficult to crib the %file code and add %date:
 
 --8---cut here---start-8---
 (defun org-complete-expand-structure-template (start cell)
   Expand a structure template.
   (let* ((musep (org-bound-and-true-p org-mtags-prefer-muse-templates))
(rpl (nth (if musep 2 1) cell))
(ind ))
 (delete-region start (point))
 (when (string-match \\`#\\+ rpl)
   (cond
((bolp))
((not (string-match \\S- (buffer-substring (point-at-bol) (point
   (setq ind (buffer-substring (point-at-bol) (point
(t (newline
 (setq start (point))
 (if (string-match %file rpl)
   (setq rpl (replace-match
  (concat
   \
   (save-match-data
 (abbreviate-file-name (read-file-name Include file: )))
   \)
  t t rpl)))
 ;;; ADDED CODE
 (if (string-match %date rpl)
   (setq rpl (replace-match
   (save-match-data
 (format-time-string %Y-%m-%d (current-time)))
  t t rpl)))
 ;;; END OF ADDED CODE
 (setq rpl (mapconcat 'identity (split-string rpl \n)
(concat \n ind)))
 (insert rpl)
 (if (re-search-backward \\? start t) (delete-char 1
 
 --8---cut here---end---8---
 
 However, the next thing somebody will ask is a different format for the
 date which will require YACV[fn:1]. But maybe one exists already?
 
 And the next thing is more of these %thingies... so it would be better
 to add yet another layer to the function, so that arbitrary %thingies
 can be added by customizing YACV, probably an alist of 
 
  (thingie . thingie-function)
 
 pairs...

That sounds like a good idea which would make the Easy Templates more
powerful.

Cheers,

Rainer

 
 Footnotes:
 
 [fn:1] Yet Another Customization Variable :-)
 

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug



signature.asc
Description: OpenPGP digital signature


Re: [O] Get a list of tasks completed today

2014-02-16 Thread Sebastien Vauban
Sebastien Vauban wrote:
 To get a list of tasks which I've completed today, I guess we must have:

   (setq org-log-done t) ; default

 I mean: I guess it's more dangerous to try and play with the state
 changes information stored in the LOGBOOK drawer as people can easily
 modify them (see `org-log-note-headings').

 Under the above assumption, the request becomes:

 (add-to-list 'org-agenda-custom-commands
  '(. Completed today
((todo DONE|CANX
   ((org-agenda-skip-function '(org-agenda-skip-entry-if 
 'notregexp CLOSED: \\[2014-02-13))
(org-agenda-sorting-strategy '(priority-down)) t)

 ... for today.

 But how can I include today's date in a programmatic way (so that it
 continues to work tomorrow ;-))?

That one is solved by doing this:

#+begin_src emacs-lisp
  (add-to-list 'org-agenda-custom-commands
   '(. Completed today
 ((todo 
((org-agenda-skip-function
  '(org-agenda-skip-entry-if 'notregexp 
(format-time-string CLOSED: \\[%Y-%m-%d)
 (org-agenda-sorting-strategy '(priority-down)) t)
#+end_src

Best regards,
  Seb

-- 
Sebastien Vauban




Re: [O] [patch] Support CUSTOM_ID property in latex export

2014-02-16 Thread Richard Lawrence
Hi Nicolas,

Nicolas Goaziou n.goaz...@gmail.com writes:

 Richard Lawrence richard.lawre...@berkeley.edu writes:

 1) Sometimes I need to refer to a section from within an embedded LaTeX
 block.  In that case, I need to know the appropriate label to use at the
 LaTeX level, not just in Org.  For example:

 * A headline
   :PROPERTIES:
   :CUSTOM_ID: sec:a-headline
   :END:

 # ... stuff ...

 #+BEGIN_LATEX
 % ... more stuff ...
 (see section~\ref{sec:a-headline})
 #+END_LATEX

 I don't think this is a good idea, as the character set allowed in
 \label{...} macros is only a subset of the character set allowed in
 custom id value. Hence the `org-export-solidify-link-text' function.

 If you are cautious, this will not be a problem, but it could bite users
 with little LaTeX knowledge.

Well, I don't quite see the force of this.  After all, isn't there a
general rule to the effect that if you override Org's default behavior,
you're on your own, so be careful?  Users are expected to make sure
that CUSTOM_ID is unique, for example.

It seems to me that if you explicitly specify CUSTOM_ID with the intent
of overriding Org's default labeling, you ought to have some idea what
can go in a \label, and be prepared to debug your LaTeX compilation if
there's an error.  If you're not prepared to do that, you should limit
yourself to the default behavior.  But if you *are* prepared to do that,
why should Org prevent you? 

 This is not possible with the present section labeling in LaTeX export,
 because I have no way of forcing Org to use a particular label for a
 section.

   * A headline
 #+latex: \label{my-section}

 #+BEGIN_LATEX
 % ... more stuff ...
 (see section~\ref{my-section})
 #+END_LATEX

 It also seems more consistent to me: since you want to explicitly write
 the \ref{...}, you are also expected to explicitly write the \label{...}
 part.

But then I would not be able to take advantage of referring to that
label from within plain Org text (i.e., outside an embedded LaTeX block)
using links.  The whole point of this is that I want to be able to refer
to a *single*, unambiguous label from within both contexts.

The strategy you suggest would result in multiple labels in the same
location in the exported document.  This is bad because it introduces
ambiguity and is thus fragile.  The exported document could have two sets
of \refs which point to two different \labels.  Initially, LaTeX
would compile them to the same thing, but if one of the labels got moved
or deleted, one set of refs would break.  

 2) I hope this doesn't happen, but there may come a time when I need to
 move away from Org and just use straight LaTeX.  Having control over the
 labeling will make this transition much easier, because it means I won't
 have to worry about manually changing the labels in a long document from
 Org's default sec-... numbering to my own semantic labels.

 See above. You can even automate that with a hook (i.e., get the custom
 id value and add a corresponding label at the beginning of the
 headline).

I realize that I could automate this if necessary.  That in fact is why
I wrote the patch: I'm trying to do the work of automating it now,
rather than waiting until a moment when I realize in desperation that I
have to convert to LaTeX. :)

For the reasons I cited above, I wouldn't want to use multiple labels,
which is why I prefer to implement my automation this way.  Is it
possible to use a hook to do what this patch does? i.e., to *replace*
Org's default labeling with labels generated from CUSTOM_ID, and have
links exported to \refs using that value instead of the default
labeling?

I sent the patch because I saw on the list that at least one other
person wanted a feature like this.  If it is not accepted, that's OK; I
will work around it, probably using a derived export backend.  But I
have to imagine that other people are doing something similar. I know
there are other people on this list using Org to write long documents
that they compile with LaTeX, and they are probably facing a similar
problem.

 3) This will make the LaTeX exporter's behavior more consistent with the
 HTML exporter's behavior.  The HTML exporter will use CUSTOM_ID if it is
 supplied to construct the id attributes of headlines and divs.  If
 someone is relying on this behavior of the HTML exporter, they might be
 unpleasantly surprised by the LaTeX exporter's behavior.

 One relying on an implementation detail instead of the actual
 specifications has to be prepared for surprises.

Maybe so, but that's actually sort of my point.  At the moment, my
options are:
  1) Use multiple labeling schemes, one accessible to Org, one
 accessible to LaTeX, and use the former in Org text and the latter
 in embedded LaTeX
  2) Avoid using Org's labeling/linking entirely, and just explicitly specify
 all my \labels and \refs
  3) Rely on my understanding of how Org will produce section labels
 when I \ref sections inside 

Re: [O] simple way to call `C-c a v' or a way to bind it to a key?

2014-02-16 Thread Marc Ihm

Hi Yaushi,

how about

(global-set-key (kbd f12) (lambda () (interactive) (execute-kbd-macro (kbd C-c 
a v

?

best regards
Marc

P.s.: In my opinion, the name execute-kbd-macro of this builtin function is 
somewhat misleading;
replay-keys describes this usage closer ...

Am 15.02.2014 14:35, schrieb Yasushi SHOJI:

Hello,

These days I hit `C-c a v' many many times a day, and now feel that
the three key combination is too much. I'd like to improve the
situation by binding the same functionality to a key, say, F12, if
possible.

Looking at the `org-agenda' dispatch code, there are quite a few lines
before calling `org-agenda-list'.  Simply binding `org-agenda-list' to
a key does not seem to work.

Is there a simple way to do it?  Or do I have to re-implement my own
function?

Thanks in advance,







[O] css classes to tables in html export

2014-02-16 Thread Vikas Rawal
How do I add custom css classes to tables while publishing my project?

Vikas