Re: [Orgmode] Insert ampersand in HTML export?

[Carsten Dominik]

On Feb 10, 2011, at 9:25 PM, Uriel Avalos wrote:


How do you insert the actual & character in an HTML export?

I'm trying to write a macro to insert a MATHML snippet but org-mode  
converts & to &.


How can I prevent that behavior?


Hi Uriel,

do you really want everyone here to construct their own test case for  
this?


Please provide an example file with the macro definition and its
use to make it as easy as possible for someone to try it out and fix it.

Thanks

- Carsten


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Automatic noexport tag based on rules?

[Carsten Dominik]

On Feb 9, 2011, at 1:29 AM, John Hendy wrote:


Hi,


My apologies if this has been discussed. I couldn't find it. I write  
everything from work in org-mode for several reasons. Primarily,  
it's my documentation system for research in order to properly  
document Intellectual Property (IP) information. It's also for todos  
and contacts. When it comes to exporting my notes into PDF for use  
in an IP notebook... I dont' want my todos in there.


Is there a way to automatically tag TODOs with :noexport:?



An alternative to using the :noexport: tag, and also to
the other suggestions given here in this thread would
be to use `org-map-entries' to physically remove all
subtrees which match your condition.  You can call the
mapper from one of the preprocessing hooks:

(defun my-export-remove-TODO ()
 (org-map-entries
  ;; The following form will be evaluated at each matching tree
  '(progn
 (outline-mark-subtree)  ; mark tree
 (delete-region (point) (mark))) ; remove it
  ;; Now the tags/property/todo matcher to select trees
  "LEVEL<15+TODO={.}"
  ))

;; Call this after other tree selection has been processed
(add-hook 'org-export-preprocess-after-tree-selection-hook
  'my-export-remove-TODO)

The matcher includes a LEVEL<15 test to make sure this will
not mess with inline tasks.

Export preprocessor hooks are a good place for such tasks.
Also Nick's proposal could be used in such a hook, but not
the same hook as I have used above.  Maybe in
org-export-preprocessor-after-include-files-hook.

Nick, an easy way to set a particular tag is

(org-toggle-tag "noexport" 'on)

The line number stuff  in org-change-tag-in-region is there
to allow people to have point in the line *after* the last
headline to change.  But maybe you can fix this by making
a special case for point and mark in the same line...

- Carsten







Or simply add the TODO category to the noexport category altogether?

I haven't turned up anything quite along these lines. One post  
suggested using "TODO keyword COMMENT" [1], but that just seems to  
perhaps exclude from export (didn't try) but I know for sure it  
removes it from agenda view. I want TODOs in agenda but don't want  
them showing up with my LaTeX export. I typically print out my work  
to-date each month or so and have to comb through my org file for  
that month, manually adding :noexport: to my TODOs. Even if I still  
do this for a few things here and there... it will save me a lot of  
time.


I suppose I could keep a separate "TODO.org" file, but I really like  
the process of being able to add them anywhere -- it seems more  
natural to do that in the flow, particularly in meetings, than to  
constantly switch buffers or even use remember to keep sending  
things related to the current topic away to their own island.


I'm 80% confident that the answer is ridiculously simply and I just  
haven't searched the right thing. Thanks for enlightening me!



Thanks,
John
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode



___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] [BABEL] "unset" :var definitions for subtree

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/10/2011 05:48 PM, Eric Schulte wrote:
> Rainer M Krug  writes:
> 
>> On 02/10/2011 02:27 AM, Eric Schulte wrote:
>>> Rainer M Krug  writes:
>>>
 Hi

 For one project, I am usinr org to write submit scripte to a cluster
 runing torqu. The important bit in this is, that between the shebang and
 the code, no other executable line must occur. As I am using variables
 in org (:var) they will occur just after the shebang, which causes a
 problem for torque. So, my question is, is there a way to "unset"
 variables defined by using :var for a subtree?

>>>
>>> Hi Rainer,
>>>
>>> Interesting question... unfortunately I don't think that removing
>>> variables from header arguments is possible under the current setup.
>>>
>>> Perhaps in your case you could add a function to the post-tangle hook,
>>> which recognizes when it is being called in a just-tangled torqu script
>>> (maybe by searching for a series of #PBS lines), and then removes any
>>> lines between the shebang and the first #PBS line?
>>
>> That is also an option - what I am using at the moment is to use
>> :no-expand as a code block specific header argument. But this raises the
>> other question:
>>
>> Can I set the :no-expand in a properties block? As far as I understand,
>> in the properties block I have the argument and the value - but what do
>> I do with :noexpand?
>>
>> :PROPERTIES:
>> :var: A=13
>> :no-expand
>> :END:
>>
> 
> You can just set it to "yes" or really any value you like (the value
> will be ignored).  I did however have to add "no-expand" to the list of
> header argument names searched for in property blocks -- I just pushed
> up a patch to this effect.

Thanks - I'll try it today and come back if it does not work.

> 
>>
>>>
>>> More generally, I wonder what a natural method would be to allow
>>> unsetting of pre-set header arguments for local blocks or subtrees?
>>> This may only apply to the :var header argument, as most others have a
>>> default setting which can be actively set.  If you have any ideas for a
>>> natural syntax for such an operation I'd be happy to hear it.
>>
>> First solution (probably the easiest to implement) would be along the
>> lines of the :no-expand header argument -
>>
>> :expand-var yes
>> and
>> :expand-var no
>>
>> This could possibly be expanded to
>> :expand-var A B C
>>
>> which would expand only the variables A B and C
>>
>> One step further: one could define groups of variables, like
>> :var-group X=A,B,C
>> or a similar syntax
>>
>> and then
>> :expand-var X
>> would expand A B and C
>>
>> This all would not be real unset - but a possibility for unsetting would be
>>
>> :var B=
>>
>> or
>>
>> :var-unset B
>>
>> i.e. if no value is specified in :var, the variable will be removed
>> (i.e. unset) - one could also use a null value (if it exists in elisp):
>>
>> :var B=(null)
>>
> 
> Thanks for the ideas,
> 
> I think you're right that something along the lines of the above should
> be the easiest to implement, however after reading these suggestions,
> I'm thinking that more generally there are a couple of other header
> arguments which could need to be unset, namely
> - file
> - dir
> - session
> - shebang
> some of these (like session) accept a "none" value which has the effect
> of un-setting the header argument.

True - haven't thought about those (and did not know about :dir useful
one!). And the :session might definitely come in handy - I have cases,
where I reset it manually before evaluating certain sections of the block.

> 
> It would be nice to generalize whatever solution we apply across all
> types of header argument (both for implementation and for user
> simplicity).  

Absolutely - coherent solutions are definitely the best.

> The simplest option would probably be to ensure that
> setting any header argument to :none would remove all instances of that
> header argument.  

Agreed - makes perfect sense. But probably for readibility use something
like:

: header :remove()

or

:header :remove

> The only problem there is cases like var, where you
> might not want to remove all :var's.  Maybe this could be expanded
> s.t. :none could take arguments, e.g.
> 
> :header :none(A, B)
> 
> which would remove all instances of the "header" header argument whose
> value is or is named "A" or "B"?  

I would stick to the name of the variable - that is more consistent.

But instead of :none() I would suggest :remove :

:header :remove(A, B)

and if one wants to remove all variables with *value "A"*, one could use

:header :remove("A")

Or does that look too funky?

No - I like it.

For consistency, one could also have a function :set() which could be
used as follow:

:header :set(A=12, B=13)

to set the "header" header argument A to 12 and B to 13.

And then probably use :unset instead of :remove?

Just thinking along while I am typing...


> 
>>
>> But this raises another question of mine:
>>
>> I tried to us

[Orgmode] Re: [BABEL] "unset" :var definitions for subtree

[Dan Davison]

Rainer M Krug  writes:

> On 02/10/2011 05:48 PM, Eric Schulte wrote:
>> Rainer M Krug  writes:
>> 
>>> On 02/10/2011 02:27 AM, Eric Schulte wrote:
 Rainer M Krug  writes:

> Hi
>
> For one project, I am usinr org to write submit scripte to a cluster
> runing torqu. The important bit in this is, that between the shebang and
> the code, no other executable line must occur. As I am using variables
> in org (:var) they will occur just after the shebang, which causes a
> problem for torque. So, my question is, is there a way to "unset"
> variables defined by using :var for a subtree?
>

 Hi Rainer,

 Interesting question... unfortunately I don't think that removing
 variables from header arguments is possible under the current setup.

 Perhaps in your case you could add a function to the post-tangle hook,
 which recognizes when it is being called in a just-tangled torqu script
 (maybe by searching for a series of #PBS lines), and then removes any
 lines between the shebang and the first #PBS line?
>>>
>>> That is also an option - what I am using at the moment is to use
>>> :no-expand as a code block specific header argument. But this raises the
>>> other question:
>>>
>>> Can I set the :no-expand in a properties block? As far as I understand,
>>> in the properties block I have the argument and the value - but what do
>>> I do with :noexpand?
>>>
>>> :PROPERTIES:
>>> :var: A=13
>>> :no-expand
>>> :END:
>>>
>> 
>> You can just set it to "yes" or really any value you like (the value
>> will be ignored).  I did however have to add "no-expand" to the list of
>> header argument names searched for in property blocks -- I just pushed
>> up a patch to this effect.
>
> Thanks - I'll try it today and come back if it does not work.
>
>> 
>>>

 More generally, I wonder what a natural method would be to allow
 unsetting of pre-set header arguments for local blocks or subtrees?
 This may only apply to the :var header argument, as most others have a
 default setting which can be actively set.  If you have any ideas for a
 natural syntax for such an operation I'd be happy to hear it.
>>>
>>> First solution (probably the easiest to implement) would be along the
>>> lines of the :no-expand header argument -
>>>
>>> :expand-var yes
>>> and
>>> :expand-var no
>>>
>>> This could possibly be expanded to
>>> :expand-var A B C
>>>
>>> which would expand only the variables A B and C
>>>
>>> One step further: one could define groups of variables, like
>>> :var-group X=A,B,C
>>> or a similar syntax
>>>
>>> and then
>>> :expand-var X
>>> would expand A B and C
>>>
>>> This all would not be real unset - but a possibility for unsetting would be
>>>
>>> :var B=
>>>
>>> or
>>>
>>> :var-unset B
>>>
>>> i.e. if no value is specified in :var, the variable will be removed
>>> (i.e. unset) - one could also use a null value (if it exists in elisp):
>>>
>>> :var B=(null)
>>>
>> 
>> Thanks for the ideas,
>> 
>> I think you're right that something along the lines of the above should
>> be the easiest to implement, however after reading these suggestions,
>> I'm thinking that more generally there are a couple of other header
>> arguments which could need to be unset, namely
>> - file
>> - dir
>> - session
>> - shebang
>> some of these (like session) accept a "none" value which has the effect
>> of un-setting the header argument.
>
> True - haven't thought about those (and did not know about :dir useful
> one!). And the :session might definitely come in handy - I have cases,
> where I reset it manually before evaluating certain sections of the block.
>
>> 
>> It would be nice to generalize whatever solution we apply across all
>> types of header argument (both for implementation and for user
>> simplicity).  
>
> Absolutely - coherent solutions are definitely the best.
>
>> The simplest option would probably be to ensure that
>> setting any header argument to :none would remove all instances of that
>> header argument.  
>
> Agreed - makes perfect sense. But probably for readibility use something
> like:
>
> : header :remove()
>
> or
>
> :header :remove
>
>> The only problem there is cases like var, where you
>> might not want to remove all :var's.  Maybe this could be expanded
>> s.t. :none could take arguments, e.g.
>> 
>> :header :none(A, B)
>> 
>> which would remove all instances of the "header" header argument whose
>> value is or is named "A" or "B"?  
>
> I would stick to the name of the variable - that is more consistent.
>
> But instead of :none() I would suggest :remove :
>
> :header :remove(A, B)
>
> and if one wants to remove all variables with *value "A"*, one could use
>
> :header :remove("A")
>
> Or does that look too funky?
>
> No - I like it.

I'm concerned that all this is looking rather complex. And I'm a bit
dubious about the :xxx syntax -- those should correspond to keys in an
association list. Could we step back a moment -- w

Re: [Orgmode] c-c c-e 1 a crashes

[Bastien]

Hi Samuel,

Samuel Wales  writes:

> Also, I was wondering, how often do people export the current file vs.
> the current region vs. the current subtree?

I don't know.

> I almost always export the current subtree.  I wonder if most other
> people are that way also.  If not, how do I make c-c c-e always use a
> prefix of 1?

You can now set `org-export-initial-scope' to 'subtree for this.

Thanks for this idea.

Also, pressing `1' will now switch between buffer/subtree export 
until you select an export command.

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] :export: tag shows up in headings of output pdf

[phaebz]

I am using org-mode 7.3 release.

Problem: A file such as

* heading to be exported :export:

* some other heading

gets exported to

1. heading to be exported :export:

With a literal :export: tag in the pdf output heading. I have not customized 
any relevant export options.

Do I miss something?

Any tips / hints are much appreciated

Michael Bach

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Exporting org-diary-class to icalendar

[Bastien]

Hi Rémi,

Rémi Vanicat  writes:

> For those who want to use the org-diary-class diary sexp, and who want
> to export it to ical (for google calendar consumption for example) Here
> is a code that will do it. Beware that my timezone is hardwired in it
> (search for Europe/Paris).

Quite useful.  Would you like to publicize it on Worg?

Thanks!

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Extracting subtrees in a date-tree org file

[Bastien]

Hi Maurizio,

Maurizio Vitale  writes:

> Is there a way to easily set the region around today's subtree or this
> week's subtree in a date-tree formatted file?

There is none for now, but I would welcome a patch to this effect.

Have a look at the `org-mark-subtree' function for a start.

Thanks,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] $0 replaced with ampersand (&) when invoking `org-edit-special'

[Bastien]

Hi Niels,

niels giesen  writes:

> According to [ (info "(org) Formula syntax for Calc") ], $0
> references the current cell. Pressing C-c C-c on the #+TBLFM line
> below does indeed work, but C-c ' (`org-edit-special') changes the
> $0 reference into a single ampersand (&). Is this a bug?

I can confirm this and I think it's a bug.

Carsten, do you know what happens here?

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Bug: org-store-link only works interactively [7.4]

[Bastien]

Hi Dave,

Dave Abrahams  writes:

> org-stored-links will only be updated if the function is called
> interactively.  I'm not sure why you would want to neuter
> org-store-link otherwise, but the docs for interactive-p say:
>
>   The only known proper use of `interactive-p' is in deciding whether to
>   display a helpful message, or how to display it.  If you're thinking
>   of using it for any other purpose, it is quite likely that you're
>   making a mistake.  

True, thanks for pointing at this.  I agree the user should be able to
call org-store-link non-interactively (programmatically).

Carsten, I see no possible side-effects, but perhaps you had a good
reason for preventing non-interactive calls to `org-store-link'?

Thanks,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Export issue of URL when the text begins with a date

[Bastien]

Hi Vincent,

Vincent Belaïche  writes:

> Here is an example org file:
>
> ---
> * some example
>
> [[file://localhost/c%3A/msys/1.0/temp/example.html][2011-01-01 example]]
> ---
>
> When I export this with `C-c C-e h' I get the following in place of the
> URL:
>
> ---
> 
> [[file://localhost/c%3A/msys/1.0/temp/example.html]  class="timestamp-wrapper"> 2011-01-01
> example]
> 
> ---

I cannot reproduce this problem with latest Org.  Can you confirm it's
gone?

Thanks,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] using (id "Name") target in org-capture-templates

[Bastien]

Hi Gregory,

"Sullivan, Gregory (US SSA)"  writes:

> Thanks for the note.  I did indeed mean to use headings.
>
> I think it would be nice to be able to have the file dynamic but the
> heading static in capture templates.  In my case, I always want to
> find a particular heading in the buffer that the capture originated
> from. So I had to put the whole target spec in a function, as in:

I like the idea of being able to tell capture to use the current file.

This patch against latest Org allows you to use (currentfile) like this:

,
| (setq org-capture-templates
|   '(("j" "Journal" entry (currentfile) "* %a\n\n%i")))
`

Let me know if you find this useful.

>From a276dc40c860e636be7c8d743bd01b401461a8f5 Mon Sep 17 00:00:00 2001
From: Bastien Guerry 
Date: Fri, 11 Feb 2011 11:17:16 +0100
Subject: [PATCH] Allow (currentfile) for capture templates.

* org-capture.el (org-capture-templates): document currentfile
for capture template.
(org-capture-templates): Allow to use currentfile for capture
templates.
(org-capture-set-target-location): Handle currentfile as a way
to setting the capture buffer.

* org.texi (Template elements): document currentfile for
capture templates.
---
 doc/org.texi|4 
 lisp/org-capture.el |   12 
 2 files changed, 16 insertions(+), 0 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index f8a7493..be66b75 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -6314,6 +6314,10 @@ Valid values are:
 @item (file "path/to/file")
 Text will be placed at the beginning or end of that file.
 
+@item (currentfile)
+Text will be placed at the beginning or end of the file 
+@code{org-capture} is called from.
+
 @item (id "id of existing org entry")
 Filing as child of this entry, or in the body of the entry.
 
diff --git a/lisp/org-capture.el b/lisp/org-capture.el
index e258308..2f9b379 100644
--- a/lisp/org-capture.el
+++ b/lisp/org-capture.el
@@ -120,6 +120,10 @@ target   Specification of where the captured item should be placed.
  (file \"path/to/file\")
  Text will be placed at the beginning or end of that file
 
+ (currentfile)
+ Text will be placed at the beginning or end of the file
+ org-capture is called from
+
  (id \"id of existing org entry\")
  File as child of this entry, or in the body of the entry
 
@@ -266,6 +270,8 @@ calendar|  %:type %:date"
 		   (list :tag "File"
 			 (const :format "" file)
 			 (file :tag "  File"))
+		   (list :tag "Current file"
+			 (const :format "" currentfile))
 		   (list :tag "ID"
 			 (const :format "" id)
 			 (string :tag "  ID"))
@@ -632,6 +638,12 @@ already gone.  Any prefix argument will be passed to the refile comand."
 	(set-buffer (org-capture-target-buffer (nth 1 target)))
 	(setq target-entry-p nil))
 
+   ((eq (car target) 'currentfile)
+	(if (not (and (buffer-file-name) (org-mode-p)))
+	(error "Cannot call this capture template outside of an Org buffer")
+	  (set-buffer (org-capture-target-buffer (buffer-file-name)))
+	  (setq target-entry-p nil)))
+
((eq (car target) 'id)
 	(let ((loc (org-id-find (nth 1 target
 	  (if (not loc)
-- 
1.7.4


-- 
 Bastien
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [BABEL] "unset" :var definitions for subtree

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/11/2011 10:32 AM, Dan Davison wrote:
> Rainer M Krug  writes:
> 
>> On 02/10/2011 05:48 PM, Eric Schulte wrote:
>>> Rainer M Krug  writes:
>>>
 On 02/10/2011 02:27 AM, Eric Schulte wrote:
> Rainer M Krug  writes:
>
>> Hi
>>
>> For one project, I am usinr org to write submit scripte to a cluster
>> runing torqu. The important bit in this is, that between the shebang and
>> the code, no other executable line must occur. As I am using variables
>> in org (:var) they will occur just after the shebang, which causes a
>> problem for torque. So, my question is, is there a way to "unset"
>> variables defined by using :var for a subtree?
>>
>
> Hi Rainer,
>
> Interesting question... unfortunately I don't think that removing
> variables from header arguments is possible under the current setup.
>
> Perhaps in your case you could add a function to the post-tangle hook,
> which recognizes when it is being called in a just-tangled torqu script
> (maybe by searching for a series of #PBS lines), and then removes any
> lines between the shebang and the first #PBS line?

 That is also an option - what I am using at the moment is to use
 :no-expand as a code block specific header argument. But this raises the
 other question:

 Can I set the :no-expand in a properties block? As far as I understand,
 in the properties block I have the argument and the value - but what do
 I do with :noexpand?

 :PROPERTIES:
 :var: A=13
 :no-expand
 :END:

>>>
>>> You can just set it to "yes" or really any value you like (the value
>>> will be ignored).  I did however have to add "no-expand" to the list of
>>> header argument names searched for in property blocks -- I just pushed
>>> up a patch to this effect.
>>
>> Thanks - I'll try it today and come back if it does not work.
>>
>>>

>
> More generally, I wonder what a natural method would be to allow
> unsetting of pre-set header arguments for local blocks or subtrees?
> This may only apply to the :var header argument, as most others have a
> default setting which can be actively set.  If you have any ideas for a
> natural syntax for such an operation I'd be happy to hear it.

 First solution (probably the easiest to implement) would be along the
 lines of the :no-expand header argument -

 :expand-var yes
 and
 :expand-var no

 This could possibly be expanded to
 :expand-var A B C

 which would expand only the variables A B and C

 One step further: one could define groups of variables, like
 :var-group X=A,B,C
 or a similar syntax

 and then
 :expand-var X
 would expand A B and C

 This all would not be real unset - but a possibility for unsetting would be

 :var B=

 or

 :var-unset B

 i.e. if no value is specified in :var, the variable will be removed
 (i.e. unset) - one could also use a null value (if it exists in elisp):

 :var B=(null)

>>>
>>> Thanks for the ideas,
>>>
>>> I think you're right that something along the lines of the above should
>>> be the easiest to implement, however after reading these suggestions,
>>> I'm thinking that more generally there are a couple of other header
>>> arguments which could need to be unset, namely
>>> - file
>>> - dir
>>> - session
>>> - shebang
>>> some of these (like session) accept a "none" value which has the effect
>>> of un-setting the header argument.
>>
>> True - haven't thought about those (and did not know about :dir useful
>> one!). And the :session might definitely come in handy - I have cases,
>> where I reset it manually before evaluating certain sections of the block.
>>
>>>
>>> It would be nice to generalize whatever solution we apply across all
>>> types of header argument (both for implementation and for user
>>> simplicity).  
>>
>> Absolutely - coherent solutions are definitely the best.
>>
>>> The simplest option would probably be to ensure that
>>> setting any header argument to :none would remove all instances of that
>>> header argument.  
>>
>> Agreed - makes perfect sense. But probably for readibility use something
>> like:
>>
>> : header :remove()
>>
>> or
>>
>> :header :remove
>>
>>> The only problem there is cases like var, where you
>>> might not want to remove all :var's.  Maybe this could be expanded
>>> s.t. :none could take arguments, e.g.
>>>
>>> :header :none(A, B)
>>>
>>> which would remove all instances of the "header" header argument whose
>>> value is or is named "A" or "B"?  
>>
>> I would stick to the name of the variable - that is more consistent.
>>
>> But instead of :none() I would suggest :remove :
>>
>> :header :remove(A, B)
>>
>> and if one wants to remove all variables with *value "A"*, one could use
>>
>> :header :remove("A")
>>
>> Or does

Re: [Orgmode] Re: Announcing org-contacts, a bbdb-like contact manager for Org

[Tassilo Horn]

Stefan Monnier  writes:

Hi Stefan,

>> Typing 'a' complete to 'aA' (instead of 'Anne ') and
>> then does nothing since aA is not valid.
>
>> I'm not sure completion-at-point-functions is correctly usable in
>> this same condition as message/bbdb completion was. The latter used
>> to return a function which is marked as decouraged in
>> `completion-at-point-functions' docstring. So org-contacts does not
>> use it. OTOH, returning a (START END COLLECTION) triplet is not very
>> usable since if you return a collection that start with a different
>> character set than (buffer-substring start end), it does not work.
>
> I don't fully understand what you're saying, probably for lack of
> context, but at least it's not true that "if you return a collection
> that start with a different character set than (buffer-substring start
> end), it doesn't work".  That simply depends on completion-styles (and
> completion-ignore-case of course).

I've just edebugged Juliens function, and if I try to complete

  To: Stefan Monnier , a

in this message buffer, his function returns

  (376 377 (#("Andreas XXX " 0 12 (org-category "contacts" 
fontified nil

which is correct.  Case didn't get accounted, and that's the only
possible completion.  However, what gets inserted after the "a" is only
a TAB character.

The value of `completion-styles' in the current message buffer is

  (basic initials partial-completion),

which should be ok for that kind of completion.

But the global value of completion-ignore-case is nil.  So the problem
seems to be that Julien's completion at point functions respects the
value of his own `org-contacts-completion-ignore-case' variable when
*calculating* completions, but it is not considered anymore when the
completion style *applies* the completions.

When I do

  (set (make-local-variable 'completion-ignore-case) t)

in the current message buffer and try again, then "a" is correctly
completed to the Andreas Julien's function calculated.  However, I want
case insensitive completion only for contact completion in the headers,
but not in the message body.

So the question is: how can the completion-ignore-case value be
propagated from the completion gathering function in
`completion-at-point-functions' to the function that actually applies
this completion, without having to modify the global or buffer local
value of `completion-ignore-case'?

Bye,
Tassilo

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: Keep URLs from automagically turning into links in HTML export?

[Bastien]

Hi Uriel,

Uriel Avalos  writes:

> Actually, is there some (per file) setting that disables that feature
> all together? 

1. Write a function that convert [[1][2]] into [[][2]] (deleting the
   link in the first brackets) 

2. Add this function to `org-export-preprocess-final-hook'

HTH,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] how to filter CATEGORY entries in org-agenda-custom command (agenda)?

[Bastien]

Hi Rainer,

Rainer Stengele  writes:

> how to filter CATEGORY entries in org-agenda-custom command (agenda)?

You can do this by setting `org-agenda-skip-function' to a function 
that matches CATEGORY.  You can find a subtree's category through 

  (org-entry-get (point) "CATEGORY")

HTH,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Timestamp display behavior in timeline view

[Bastien]

Hi Alex,

Alex Huang  writes:

> 3. current behavior:
>   ( + is unsurprising, ! is surprising, ? is not sure whether to be
> surprised)
>   + entries without time information not displayed
>   + timestamps without text not displayed
>   ! entries with timestamps display the text, but not the timestamp

You used this:

* TODO <2010-12-25 Sat 14:40>-<2010-12-25 Sat 14:50> range with todo

which looks weird.

Better to put the timestamp/range on the next line:

* TODO range with todo
  <2010-12-25 Sat 14:40>-<2010-12-25 Sat 14:50>

You won't get the surprising results you see.

HTH,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] iCalendar selective export

[Bastien]

Hi Juraj,

Juraj Kubelka  writes:

> I found out that exporting agenda files to iCalendar
> (org-export-icalendar-all-agenda-files) ignore
> variable org-export-exclude-tags. Is it right? And is it wanted? I do
> not want to see some tasks in my external calendar (mobile phone).

You now set ̀org-icalendar-honor-noexport-tag' to t to prevent export of
entries with a :noexport: tag.

Thanks for this idea,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: Announcing org-contacts, a bbdb-like contact manager for Org

[Thierry Volpiatto]

Julien Danjou  writes:

> On Thu, Feb 10 2011, Tassilo Horn wrote:
>
>> I'm also using Emacs 24, and for me it doesn't work.
>
> Ok. Anyway I've just double checked, and it worst than that.
>
> Typing 'a' complete to 'aA' (instead of 'Anne ') and then
> does nothing since aA is not valid.
>
> I'm not sure completion-at-point-functions is correctly usable in this
> same dondition as message/bbdb completion was. The latter used to return
> a function which is marked as decouraged in
> `completion-at-point-functions' docstring. So org-contacts does not use
> it. OTOH, returning a (START END COLLECTION) triplet is not very usable
> since if you return a collection that start with a different character
> set than (buffer-substring start end), it does not work.
>
> (Cc'ing emacs-devel, in case someone has an advice on that.)
I am not using anymore bbdb, using only my own addressbook based on
bookmarks.It have completion in message with TAB.
You can get it here:
http://mercurial.intuxication.org/hg/emacs-bookmark-extension/

Maybe it can help for your org-contacts.

-- 
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] [OT] Taskwarrior, nice GTD-oriented CLI thing

[Bastien]

Marcelo de Moraes Serpa  writes:

> Bastien, Carnsten, what do you guys think of Taskwarrior? :)

I think it's pretty neat and that creating an org2taskwarrior export
should be easy so that we can benefit of the nice taskwarrior graphs.

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: S5 export

[Bastien]

Hi Achim,

Achim Gratz  writes:

> Bastien  writes:
>> I would welcome an approach where we factor out some elements of
>> org-export-as-html, so that exporting to s5 would just require the 
>> user to customize those elements.
>
> Sorry for piggy-backing onto this topic, but I seem to remember the
> mention of a "generic exporter" on this list, but I don't remember what
> the outcome of that discussion was.  While looking at the table export I
> realized that there is lots of duplicated code just for exporting the
> tables, which seems wasteful (and error-prone in the longer term). Would
> it seem reasonable to have a "generic export" function that parses the
> org document into a structure of callbacks and lists and then only
> define the callbacks for each backend?

There are now three generic exporters:

- org-export-generic.el in contrib/lisp/ by Wes Hardaker
- org-export.el (in EXPERIMENTAL/)
- the one that Jambunathan and Lennart provide with the odt export

I will document org-export.el -- don't hesitate to have a look.

I will also take time to look more closely at the work Lennart did 
for the odt export to see whether we can refactor some org-parse.el
with the parsing functions in org-export.el.

This requires more time that I have everyday, expect this to happen
after a long week-end!

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: Combination of =code= and Description

[Bastien]

Hi Achim,

Achim Gratz  writes:

> Bastien  writes:
>> But
>>
>>   \item[{\texttt code}]some additional text
>>
>> would do the job.
>
> No, it doesn't - it makes the first "c" character non-bold typewriter
> and the rest "ode" bold sans serif.  There simply is no boldface version
> of the typewriter font in standard LaTeX, so the form of the argument to
> item isn't really responsible for the result.

Thanks, I stand corrected.

> If it were, then I think from a LaTeX perspective \texttt{code} is
> preferred, although the fully braced construct also works in that
> situation.

So let's live with it.

Thanks,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: Small bug in table editing

[Bastien]

Hi Christopher,

Christopher Witte  writes:

> As I said, I can be persuaded otherwise, but saying don't use org-mode
> tables isn't very persuasive.  

:)

> What is the semantic model for "enter"
> when using org-mode tables? Clearly I don't understand it.

Return and TAB reformats the current table line.
Return goes to next-line and same-column cell.
TAB goes to the same-line and next-column cell.

I think reformatting a line starting with |- to |+| 
is the right thing to do.

What did you expect instead?

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Open HTML link in other window?

[Bastien]

Hi Vladimir,

Vladimir Alexiev  writes:

> Is there a way to configure the HTML export to open every 
> *external* link to another window?

#+ATTR_HTML: target="_blank"
[[http://www.w3schools.com/HTML/html_links.asp][link]]

Will add the target attribute to the link.

There is no way to set this as a default for all links,
I don't think this is really necessary.  But feel free to
try to convince me :)

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] More entries able to export to icalendar format

[Bastien]

Hi Niels,

Niels Giesen  writes:

> I took a stab at ameliorating =icalendar--convert-float-to-ical=, and
> would like your early comments before going further.

Can you submit your changes in the form of a patch, precisely describing
your changes?  This way I can more easily try to understand/test them.

Thanks for your work!

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] A couple of suggestions

[Bastien]

Hi Filippo,

"Filippo A. Salustri"  writes:

> I have thought of a couple of ideas.  I wanted to bounce them off the
> community before thinking about trying to implement them myself (I
> used to be pretty good with lisp, a thousand years ago).

I used to reply faster to emails, a thousand years ago ;)

> 1. A bit more structure to page layout.
> In particular I was thinking of this:
> a. one file per day

You can do it.

> b. date and journal name at top

You can do it.

> c. a right "sidebar" of sorts that contains tags, dates, etc for the
> item to its left.  This amounts to basically a tabular page
> arrangement, and each "item" gets a row.

We don't have sidebars but we have the Great Column View.  Browsing
your file while in column view let's you display whatever information
you want about your entries.

HTH,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Extending paste to auto-archive a copied image

[Bastien]

Hi Marcelo,

Marcelo de Moraes Serpa  writes:

> So, I'm usign an emacs extension that renders links to image as the
> image itself, it's a minor mode called iimage.el. It works great, but
> the fact that I need to copy the image somewhere first is a time and
> flow - killer. Is it possible to hook up to the paste command and, if
> it's a image in the clipboard, auto-archive somewhere in the
> filesystem it and then return its URL?

Sorry I don't understand.  Can you give an example?  When you say
"paste", is it pasting from X or from Emacs?

Thanks,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [BABEL] "unset" :var definitions for subtree

[Dan Davison]

Rainer M Krug  writes:

> On 02/11/2011 10:32 AM, Dan Davison wrote:
>> Rainer M Krug  writes:
>>
>>> On 02/10/2011 05:48 PM, Eric Schulte wrote:
 Rainer M Krug  writes:

> On 02/10/2011 02:27 AM, Eric Schulte wrote:
>> Rainer M Krug  writes:
>>
>>> Hi
>>>
>>> For one project, I am usinr org to write submit scripte to a cluster
>>> runing torqu. The important bit in this is, that between the shebang and
>>> the code, no other executable line must occur. As I am using variables
>>> in org (:var) they will occur just after the shebang, which causes a
>>> problem for torque. So, my question is, is there a way to "unset"
>>> variables defined by using :var for a subtree?
>>>
>>
>> Hi Rainer,
>>
>> Interesting question... unfortunately I don't think that removing
>> variables from header arguments is possible under the current setup.
>>
>> Perhaps in your case you could add a function to the post-tangle hook,
>> which recognizes when it is being called in a just-tangled torqu script
>> (maybe by searching for a series of #PBS lines), and then removes any
>> lines between the shebang and the first #PBS line?
>
> That is also an option - what I am using at the moment is to use
> :no-expand as a code block specific header argument. But this raises the
> other question:
>
> Can I set the :no-expand in a properties block? As far as I understand,
> in the properties block I have the argument and the value - but what do
> I do with :noexpand?
>
> :PROPERTIES:
> :var: A=13
> :no-expand
> :END:
>

 You can just set it to "yes" or really any value you like (the value
 will be ignored).  I did however have to add "no-expand" to the list of
 header argument names searched for in property blocks -- I just pushed
 up a patch to this effect.
>>>
>>> Thanks - I'll try it today and come back if it does not work.
>>>

>
>>
>> More generally, I wonder what a natural method would be to allow
>> unsetting of pre-set header arguments for local blocks or subtrees?
>> This may only apply to the :var header argument, as most others have a
>> default setting which can be actively set.  If you have any ideas for a
>> natural syntax for such an operation I'd be happy to hear it.
>
> First solution (probably the easiest to implement) would be along the
> lines of the :no-expand header argument -
>
> :expand-var yes
> and
> :expand-var no
>
> This could possibly be expanded to
> :expand-var A B C
>
> which would expand only the variables A B and C
>
> One step further: one could define groups of variables, like
> :var-group X=A,B,C
> or a similar syntax
>
> and then
> :expand-var X
> would expand A B and C
>
> This all would not be real unset - but a possibility for unsetting would 
> be
>
> :var B=
>
> or
>
> :var-unset B
>
> i.e. if no value is specified in :var, the variable will be removed
> (i.e. unset) - one could also use a null value (if it exists in elisp):
>
> :var B=(null)
>

 Thanks for the ideas,

 I think you're right that something along the lines of the above should
 be the easiest to implement, however after reading these suggestions,
 I'm thinking that more generally there are a couple of other header
 arguments which could need to be unset, namely
 - file
 - dir
 - session
 - shebang
 some of these (like session) accept a "none" value which has the effect
 of un-setting the header argument.
>>>
>>> True - haven't thought about those (and did not know about :dir useful
>>> one!). And the :session might definitely come in handy - I have cases,
>>> where I reset it manually before evaluating certain sections of the block.
>>>

 It would be nice to generalize whatever solution we apply across all
 types of header argument (both for implementation and for user
 simplicity).
>>>
>>> Absolutely - coherent solutions are definitely the best.
>>>
 The simplest option would probably be to ensure that
 setting any header argument to :none would remove all instances of that
 header argument.
>>>
>>> Agreed - makes perfect sense. But probably for readibility use something
>>> like:
>>>
>>> : header :remove()
>>>
>>> or
>>>
>>> :header :remove
>>>
 The only problem there is cases like var, where you
 might not want to remove all :var's.  Maybe this could be expanded
 s.t. :none could take arguments, e.g.

 :header :none(A, B)

 which would remove all instances of the "header" header argument whose
 value is or is named "A" or "B"?
>>>
>>> I would stick to the name of the variable - that is more consistent.
>>>
>>> But instead of :none() I would suggest :remove :
>>>
>>> :header :remove(A, 

Re: [Orgmode] Feature request: Select links by description [7.4]

[Bastien]

Hi Dave,

Dave Abrahams  writes:

> When using org-insert-link, it would be far better for me to have it
> show me the _descriptions_ of links (the default link text), rather
> than showing me the links themselves.  This is especially true of
> email links, which are generally long and unintelligible by
> themselves.
>
> I have something set up that stores a link to every email I send, so I
> can easily link to follow-ups in my active Org items.  As a result, I
> end up with *lots* of stored links, which makes this a real struggle.

`org-insert-link' *does* already displays the description of the links
like this:

http://orgmode.org (Org Mode website)
http://orgmode.org/worg/ (Worg website)

The description is within the parenthese.

I think it's good to have both the link *and* the description.

What would be a better way of presenting the description?

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] A couple of suggestions

[Filippo A. Salustri]

And here I am thinking that I'd read / understood the manual.
*sigh*.  Thanks for the response, no matter how tardy it may be.  Time is
relative anyways; when one considers all the crap I've done between having
sent that note and now, it feels like no time at all has past. :)
Cheers.
Fil

On 11 February 2011 06:48, Bastien  wrote:

> Hi Filippo,
>
> "Filippo A. Salustri"  writes:
>
> > I have thought of a couple of ideas.  I wanted to bounce them off the
> > community before thinking about trying to implement them myself (I
> > used to be pretty good with lisp, a thousand years ago).
>
> I used to reply faster to emails, a thousand years ago ;)
>
> > 1. A bit more structure to page layout.
> > In particular I was thinking of this:
> > a. one file per day
>
> You can do it.
>
> > b. date and journal name at top
>
> You can do it.
>
> > c. a right "sidebar" of sorts that contains tags, dates, etc for the
> > item to its left.  This amounts to basically a tabular page
> > arrangement, and each "item" gets a row.
>
> We don't have sidebars but we have the Great Column View.  Browsing
> your file while in column view let's you display whatever information
> you want about your entries.
>
> HTH,
>
> --
>  Bastien
>



-- 
Filippo A. Salustri, Ph.D., P.Eng.
Mechanical and Industrial Engineering
Ryerson University
350 Victoria St, Toronto, ON
M5B 2K3, Canada
Tel: 416/979-5000 ext 7749
Fax: 416/979-5265
Email: salus...@ryerson.ca
http://deseng.ryerson.ca/~fil/
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] [RFC] Give org-format-agenda-item a real format

[Bastien]

Julien Danjou  writes:

> The ultimate goal of this is to replace `org-agenda-prefix-format' by
> `org-agenda-format' which controls the whole agenda line format and not
> only its prefix. 

Julien recently made progress on this (big) patch.

See his branch here:
  
http://git.naquadah.org/?p=~jd/org-mode.git;a=shortlog;h=refs/heads/jd/agenda-format

There are still a few issues, one being with the column view
not properly displaying the ITEM column.

Please test this branch and report any problems.

Thanks!

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] [RFC] Give org-format-agenda-item a real format

[Carsten Dominik]

On Feb 11, 2011, at 1:13 PM, Bastien wrote:

> Julien Danjou  writes:
> 
>> The ultimate goal of this is to replace `org-agenda-prefix-format' by
>> `org-agenda-format' which controls the whole agenda line format and not
>> only its prefix. 
> 
> Julien recently made progress on this (big) patch.
> 
> See his branch here:
>  
> http://git.naquadah.org/?p=~jd/org-mode.git;a=shortlog;h=refs/heads/jd/agenda-format
> 
> There are still a few issues, one being with the column view
> not properly displaying the ITEM column.
> 
> Please test this branch and report any problems.


Important testing will be to see how the agenda behaves
when metadata is changed from the agenda.  For example,
changing dates with S-left and S-right, changing the TODO
states, tags, priorities etc.

- Carsten


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Tab/S-Tab cycling behavior: how to include #+begin_src and #+results blocks

[Bastien]

Hi Leo,

Leo Alekseyev  writes:

> I rely heavily on org-cycling/org-global-cycling to see an outline
> view of the document.  It would help if I could use  #+begin_src and
> #+results blocks, and possibly some others, in this outline view.
> Specifically, I would like to be able to do the following:
>
> (a) When cycling with S-Tab, between "contents" and "show all" I would
> like a step where all the #+begin_src and #+results blocks are folded.

Not what you're asking for, but this might help:

,[ org-hide-block-startup ]
| Documentation:
| Non-nil means entering Org-mode will fold all blocks.
| This can also be set in on a per-file basis with
| 
| #+STARTUP: hideblocks
| #+STARTUP: showblocks
`

Also, I think org-cycle should only understand the file structure, not
the content structure - and I guess it's reasonable to consider blocks
are part of the content structure.

HTH,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [BABEL] "unset" :var definitions for subtree

[Dan Davison]

"Eric Schulte"  writes:

> Rainer M Krug  writes:
>
>> On 02/10/2011 02:27 AM, Eric Schulte wrote:
>>> Rainer M Krug  writes:
>>>
 Hi

 For one project, I am usinr org to write submit scripte to a cluster
 runing torqu. The important bit in this is, that between the shebang and
 the code, no other executable line must occur. As I am using variables
 in org (:var) they will occur just after the shebang, which causes a
 problem for torque. So, my question is, is there a way to "unset"
 variables defined by using :var for a subtree?

>>>
>>> Hi Rainer,
>>>
>>> Interesting question... unfortunately I don't think that removing
>>> variables from header arguments is possible under the current setup.
>>>
>>> Perhaps in your case you could add a function to the post-tangle hook,
>>> which recognizes when it is being called in a just-tangled torqu script
>>> (maybe by searching for a series of #PBS lines), and then removes any
>>> lines between the shebang and the first #PBS line?
>>
>> That is also an option - what I am using at the moment is to use
>> :no-expand as a code block specific header argument. But this raises the
>> other question:
>>
>> Can I set the :no-expand in a properties block? As far as I understand,
>> in the properties block I have the argument and the value - but what do
>> I do with :noexpand?
>>
>> :PROPERTIES:
>> :var: A=13
>> :no-expand
>> :END:
>>
>
> You can just set it to "yes" or really any value you like (the value
> will be ignored).  I did however have to add "no-expand" to the list of
> header argument names searched for in property blocks -- I just pushed
> up a patch to this effect.
>
>>
>>>
>>> More generally, I wonder what a natural method would be to allow
>>> unsetting of pre-set header arguments for local blocks or subtrees?
>>> This may only apply to the :var header argument, as most others have a
>>> default setting which can be actively set.  If you have any ideas for a
>>> natural syntax for such an operation I'd be happy to hear it.
>>
>> First solution (probably the easiest to implement) would be along the
>> lines of the :no-expand header argument -
>>
>> :expand-var yes
>> and
>> :expand-var no
>>
>> This could possibly be expanded to
>> :expand-var A B C
>>
>> which would expand only the variables A B and C
>>
>> One step further: one could define groups of variables, like
>> :var-group X=A,B,C
>> or a similar syntax
>>
>> and then
>> :expand-var X
>> would expand A B and C
>>
>> This all would not be real unset - but a possibility for unsetting would be
>>
>> :var B=
>>
>> or
>>
>> :var-unset B
>>
>> i.e. if no value is specified in :var, the variable will be removed
>> (i.e. unset) - one could also use a null value (if it exists in elisp):
>>
>> :var B=(null)
>>
>
> Thanks for the ideas,
>
> I think you're right that something along the lines of the above should
> be the easiest to implement, however after reading these suggestions,
> I'm thinking that more generally there are a couple of other header
> arguments which could need to be unset, namely
> - file
> - dir
> - session
> - shebang
> some of these (like session) accept a "none" value which has the effect
> of un-setting the header argument.
>
> It would be nice to generalize whatever solution we apply across all
> types of header argument (both for implementation and for user
> simplicity).

Some half thought-through suggestions. Sorry if this is a bit
disorganized.

I wonder whether we should be using Org property inheritance here. If it
were possible to turn off property inheritance temporarily for the
execution of the block, then it could be prevented from inheriting the
header args that you don't want it to inherit. Perhaps babel could offer
a :bind header argument, which specifies the values of lisp variables in
a let-binding which encloses the src block execution?

#+header: :bind org-babel-use-property-inheritance nil
#+begin_src sh :tangle script.sh :shebang #!/bin/bash
#$ -cwd
#+end_src

with a patch along these lines

+(defvar org-babel-use-property-inheritance t
+  "When looking for org-babel header arguments in in-buffer
+  properties, this variable is passed as the INHERIT argument to
+  the function `org-enrty-get'")
+
 (defvar org-file-properties)
 (defun org-babel-params-from-properties (&optional lang)
   "Retrieve parameters specified as properties.
@@ -864,7 +870,7 @@ may be specified in the properties of the current outline 
entry."
 (lambda (header-arg)
   (and (setq val
  (or (condition-case nil
- (org-entry-get (point) header-arg t)
+ (org-entry-get (point) header-arg 
org-babel-use-property-inheritance)
(error nil))
  (cdr (assoc header-arg org-file-properties
(cons (intern (concat ":" header-arg))


In fact, that might be more widely useful in Org -- it

Re: [Orgmode] Feature request: another Org file for anniversary entries

[Bastien]

Hi Juraj,

thanks for the patch and the explanations.

Juraj Kubelka  writes:

> So, my regular diary events are stored in main.org file and
> anniversaries in anniversary.org file.

Which lets you have two separate .ics files, one containing
anniversaries, the other one not containing them.

I still fail to understand what is needed that cannot be taken
care of by your settings.  

Thanks,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [BABEL] "unset" :var definitions for subtree

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/11/2011 12:55 PM, Dan Davison wrote:
> Rainer M Krug  writes:
> 
>> On 02/11/2011 10:32 AM, Dan Davison wrote:
>>> Rainer M Krug  writes:
>>>
 On 02/10/2011 05:48 PM, Eric Schulte wrote:
> Rainer M Krug  writes:
>
>> On 02/10/2011 02:27 AM, Eric Schulte wrote:
>>> Rainer M Krug  writes:
>>>
 Hi

 For one project, I am usinr org to write submit scripte to a cluster
 runing torqu. The important bit in this is, that between the shebang 
 and
 the code, no other executable line must occur. As I am using variables
 in org (:var) they will occur just after the shebang, which causes a
 problem for torque. So, my question is, is there a way to "unset"
 variables defined by using :var for a subtree?

>>>
>>> Hi Rainer,
>>>
>>> Interesting question... unfortunately I don't think that removing
>>> variables from header arguments is possible under the current setup.
>>>
>>> Perhaps in your case you could add a function to the post-tangle hook,
>>> which recognizes when it is being called in a just-tangled torqu script
>>> (maybe by searching for a series of #PBS lines), and then removes any
>>> lines between the shebang and the first #PBS line?
>>
>> That is also an option - what I am using at the moment is to use
>> :no-expand as a code block specific header argument. But this raises the
>> other question:
>>
>> Can I set the :no-expand in a properties block? As far as I understand,
>> in the properties block I have the argument and the value - but what do
>> I do with :noexpand?
>>
>> :PROPERTIES:
>> :var: A=13
>> :no-expand
>> :END:
>>
>
> You can just set it to "yes" or really any value you like (the value
> will be ignored).  I did however have to add "no-expand" to the list of
> header argument names searched for in property blocks -- I just pushed
> up a patch to this effect.

 Thanks - I'll try it today and come back if it does not work.

>
>>
>>>
>>> More generally, I wonder what a natural method would be to allow
>>> unsetting of pre-set header arguments for local blocks or subtrees?
>>> This may only apply to the :var header argument, as most others have a
>>> default setting which can be actively set.  If you have any ideas for a
>>> natural syntax for such an operation I'd be happy to hear it.
>>
>> First solution (probably the easiest to implement) would be along the
>> lines of the :no-expand header argument -
>>
>> :expand-var yes
>> and
>> :expand-var no
>>
>> This could possibly be expanded to
>> :expand-var A B C
>>
>> which would expand only the variables A B and C
>>
>> One step further: one could define groups of variables, like
>> :var-group X=A,B,C
>> or a similar syntax
>>
>> and then
>> :expand-var X
>> would expand A B and C
>>
>> This all would not be real unset - but a possibility for unsetting would 
>> be
>>
>> :var B=
>>
>> or
>>
>> :var-unset B
>>
>> i.e. if no value is specified in :var, the variable will be removed
>> (i.e. unset) - one could also use a null value (if it exists in elisp):
>>
>> :var B=(null)
>>
>
> Thanks for the ideas,
>
> I think you're right that something along the lines of the above should
> be the easiest to implement, however after reading these suggestions,
> I'm thinking that more generally there are a couple of other header
> arguments which could need to be unset, namely
> - file
> - dir
> - session
> - shebang
> some of these (like session) accept a "none" value which has the effect
> of un-setting the header argument.

 True - haven't thought about those (and did not know about :dir useful
 one!). And the :session might definitely come in handy - I have cases,
 where I reset it manually before evaluating certain sections of the block.

>
> It would be nice to generalize whatever solution we apply across all
> types of header argument (both for implementation and for user
> simplicity).

 Absolutely - coherent solutions are definitely the best.

> The simplest option would probably be to ensure that
> setting any header argument to :none would remove all instances of that
> header argument.

 Agreed - makes perfect sense. But probably for readibility use something
 like:

 : header :remove()

 or

 :header :remove

> The only problem there is cases like var, where you
> might not want to remove all :var's.  Maybe this could be expanded
> s.t. :none could take arguments, e.g.
>
> :header :none(A, B)
>
> which would remove all insta

Re: [Orgmode] [Emacs-orgmode] cannot store link to an info ode?

[Bastien]

Hi Vincent,

Vincent Belaïche  writes:

> This format contradicts the assumption made in the URL package,
> according to URL documentation the format should have been
>
> [[info:org.info#External%20links][some description]]

I've pushed a fix to use this format (with "#") now.

You can still follow info links with the old syntax.

> Finally I make again the same suggestion, it would be good to have also
> a line pointer, especially as it seems that the latest version of info
> also have a line pointer in the index nodes.

Patch welcome!

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] latex table export not centered

[Bastien]

Hi Andreas,

Andreas Leha  writes:

> #+BIND: org-export-latex-tables-centered nil
> #+TITLE:   Test Centered Tables
>
> * Test
>   | col1 | col2 | col3 |
>   |--+--+--|
>   |1 |2 |3 |
>
>
> But this does not work.  The table stays centered.

I just tested this: the table is left aligned here (latest Org, GNU
Emacs 24.0.50.1).

Are you still having this issue?  What version of Org/Emacs?

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [BABEL] "unset" :var definitions for subtree

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/11/2011 01:19 PM, Dan Davison wrote:
> "Eric Schulte"  writes:
> 
>> Rainer M Krug  writes:
>>
>>> On 02/10/2011 02:27 AM, Eric Schulte wrote:
 Rainer M Krug  writes:

> Hi
>
> For one project, I am usinr org to write submit scripte to a cluster
> runing torqu. The important bit in this is, that between the shebang and
> the code, no other executable line must occur. As I am using variables
> in org (:var) they will occur just after the shebang, which causes a
> problem for torque. So, my question is, is there a way to "unset"
> variables defined by using :var for a subtree?
>

 Hi Rainer,

 Interesting question... unfortunately I don't think that removing
 variables from header arguments is possible under the current setup.

 Perhaps in your case you could add a function to the post-tangle hook,
 which recognizes when it is being called in a just-tangled torqu script
 (maybe by searching for a series of #PBS lines), and then removes any
 lines between the shebang and the first #PBS line?
>>>
>>> That is also an option - what I am using at the moment is to use
>>> :no-expand as a code block specific header argument. But this raises the
>>> other question:
>>>
>>> Can I set the :no-expand in a properties block? As far as I understand,
>>> in the properties block I have the argument and the value - but what do
>>> I do with :noexpand?
>>>
>>> :PROPERTIES:
>>> :var: A=13
>>> :no-expand
>>> :END:
>>>
>>
>> You can just set it to "yes" or really any value you like (the value
>> will be ignored).  I did however have to add "no-expand" to the list of
>> header argument names searched for in property blocks -- I just pushed
>> up a patch to this effect.
>>
>>>

 More generally, I wonder what a natural method would be to allow
 unsetting of pre-set header arguments for local blocks or subtrees?
 This may only apply to the :var header argument, as most others have a
 default setting which can be actively set.  If you have any ideas for a
 natural syntax for such an operation I'd be happy to hear it.
>>>
>>> First solution (probably the easiest to implement) would be along the
>>> lines of the :no-expand header argument -
>>>
>>> :expand-var yes
>>> and
>>> :expand-var no
>>>
>>> This could possibly be expanded to
>>> :expand-var A B C
>>>
>>> which would expand only the variables A B and C
>>>
>>> One step further: one could define groups of variables, like
>>> :var-group X=A,B,C
>>> or a similar syntax
>>>
>>> and then
>>> :expand-var X
>>> would expand A B and C
>>>
>>> This all would not be real unset - but a possibility for unsetting would be
>>>
>>> :var B=
>>>
>>> or
>>>
>>> :var-unset B
>>>
>>> i.e. if no value is specified in :var, the variable will be removed
>>> (i.e. unset) - one could also use a null value (if it exists in elisp):
>>>
>>> :var B=(null)
>>>
>>
>> Thanks for the ideas,
>>
>> I think you're right that something along the lines of the above should
>> be the easiest to implement, however after reading these suggestions,
>> I'm thinking that more generally there are a couple of other header
>> arguments which could need to be unset, namely
>> - file
>> - dir
>> - session
>> - shebang
>> some of these (like session) accept a "none" value which has the effect
>> of un-setting the header argument.
>>
>> It would be nice to generalize whatever solution we apply across all
>> types of header argument (both for implementation and for user
>> simplicity).
> 
> Some half thought-through suggestions. Sorry if this is a bit
> disorganized.
> 
> I wonder whether we should be using Org property inheritance here. If it
> were possible to turn off property inheritance temporarily for the
> execution of the block, then it could be prevented from inheriting the
> header args that you don't want it to inherit. Perhaps babel could offer
> a :bind header argument, which specifies the values of lisp variables in
> a let-binding which encloses the src block execution?

The whole logic in org is that, if I understand correctly, of the
smaller unit (e.g. file -> subtree -> ... -> code block) inheriting
properties, variables, ... from the next larger unit - introducing a
possibility to disable inheritance, would introduce a completely new
level of complexity. I think that one should rather introduce a way of
unsetting e.g. variable values to have the same effect, but still
sticking with the whole inheritance logic.
I reslly think that it might be dangerous to open the possibility to
break this inheritance principle.

> 
> #+header: :bind org-babel-use-property-inheritance nil
> #+begin_src sh :tangle script.sh :shebang #!/bin/bash
> #$ -cwd
> #+end_src
> 
> with a patch along these lines
> 
> +(defvar org-babel-use-property-inheritance t
> +  "When looking for org-babel header arguments in in-buffer
> +  properties, this variable is passed as the INHERIT argu

Re: [Orgmode] [BUG] export of table.el tables

[Bastien]

David Maus  writes:

>> Summary: table.el tables with row and col spans are not getting exported
>> as expected on html export.
>>
>> Looks like the table markers gets recognized as strikethroughs, mdashes
>> and ndashes. This apparrently is getting in the way of proper
>> export.
>>
>> Furthermore I see no rowspans and colspans in the generated html.

As a workaround, one can try to export table.el tables to org-mode
tables before export.

Quick hack:

#+begin_src emacs-lisp
(defun org-convert-table-el-all ()
  (interactive)
  (save-excursion
(goto-char (point-min))
(while (re-search-forward "^[ \t]*\\+-+.+\\+[ \t]*$" nil t)
  (when (org-at-table.el-p)
(org-table-create-with-table.el)
#+end_src

Hook this to org-export-preprocess-before-selecting-backend-code-hook
and you'll be prompted whether you want to convert tables or not.

Not tested, but you get the idea.

HTH,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] [RFC] Give org-format-agenda-item a real format

[Bastien]

Carsten Dominik  writes:

> Important testing will be to see how the agenda behaves
> when metadata is changed from the agenda.  For example,
> changing dates with S-left and S-right, changing the TODO
> states, tags, priorities etc.

Indeed.

Some testing for Julien:

- Setting TODO keyword is okay (although there are some glitches with
  the fontification of the agenda line.)

- Setting the priority cookie does not work: it insert the char (65)
  instead of the string ([#A])

- Changing timestamps doesn't work at all.

Yep, some more work to do in this area.

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Inconsistencies in email and author export

[Bastien]

Hi Lawrence,

Lawrence Mitchell  writes:

> The decision for when to add email and author information to an
> exported document seems to be treated somewhat inconsistently
> between export backends.

Yes, it is a bit inconsistent.  However, I'd rather discuss the way
author/email information are inserted *per backend*: if one backend 
does the wrong thing, let's fix this backend.

If every backend behaves wisely, then no need to set rules for all
backends at once.

What do you think?

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] org-stow (Proof of concept)

[Bastien]

"Tom Breton (Tehom)"  writes:

> Any interest in trying this out?  I can push it if anyone else wants to
> try it out.

I'm interested!  Please let me know where I can read some code.

Thanks :)

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [BABEL] "unset" :var definitions for subtree

[Dan Davison]

Rainer M Krug  writes:

> On 02/11/2011 01:19 PM, Dan Davison wrote:
>> "Eric Schulte"  writes:
>>
>>> Rainer M Krug  writes:
>>>
 On 02/10/2011 02:27 AM, Eric Schulte wrote:
> Rainer M Krug  writes:
>
>> Hi
>>
>> For one project, I am usinr org to write submit scripte to a cluster
>> runing torqu. The important bit in this is, that between the shebang and
>> the code, no other executable line must occur. As I am using variables
>> in org (:var) they will occur just after the shebang, which causes a
>> problem for torque. So, my question is, is there a way to "unset"
>> variables defined by using :var for a subtree?
>>
>
> Hi Rainer,
>
> Interesting question... unfortunately I don't think that removing
> variables from header arguments is possible under the current setup.
>
> Perhaps in your case you could add a function to the post-tangle hook,
> which recognizes when it is being called in a just-tangled torqu script
> (maybe by searching for a series of #PBS lines), and then removes any
> lines between the shebang and the first #PBS line?

 That is also an option - what I am using at the moment is to use
 :no-expand as a code block specific header argument. But this raises the
 other question:

 Can I set the :no-expand in a properties block? As far as I understand,
 in the properties block I have the argument and the value - but what do
 I do with :noexpand?

 :PROPERTIES:
 :var: A=13
 :no-expand
 :END:

>>>
>>> You can just set it to "yes" or really any value you like (the value
>>> will be ignored).  I did however have to add "no-expand" to the list of
>>> header argument names searched for in property blocks -- I just pushed
>>> up a patch to this effect.
>>>

>
> More generally, I wonder what a natural method would be to allow
> unsetting of pre-set header arguments for local blocks or subtrees?
> This may only apply to the :var header argument, as most others have a
> default setting which can be actively set.  If you have any ideas for a
> natural syntax for such an operation I'd be happy to hear it.

 First solution (probably the easiest to implement) would be along the
 lines of the :no-expand header argument -

 :expand-var yes
 and
 :expand-var no

 This could possibly be expanded to
 :expand-var A B C

 which would expand only the variables A B and C

 One step further: one could define groups of variables, like
 :var-group X=A,B,C
 or a similar syntax

 and then
 :expand-var X
 would expand A B and C

 This all would not be real unset - but a possibility for unsetting would be

 :var B=

 or

 :var-unset B

 i.e. if no value is specified in :var, the variable will be removed
 (i.e. unset) - one could also use a null value (if it exists in elisp):

 :var B=(null)

>>>
>>> Thanks for the ideas,
>>>
>>> I think you're right that something along the lines of the above should
>>> be the easiest to implement, however after reading these suggestions,
>>> I'm thinking that more generally there are a couple of other header
>>> arguments which could need to be unset, namely
>>> - file
>>> - dir
>>> - session
>>> - shebang
>>> some of these (like session) accept a "none" value which has the effect
>>> of un-setting the header argument.
>>>
>>> It would be nice to generalize whatever solution we apply across all
>>> types of header argument (both for implementation and for user
>>> simplicity).
>>
>> Some half thought-through suggestions. Sorry if this is a bit
>> disorganized.

>> I wonder whether we should be using Org property inheritance here. If it
>> were possible to turn off property inheritance temporarily for the
>> execution of the block, then it could be prevented from inheriting the
>> header args that you don't want it to inherit. Perhaps babel could offer
>> a :bind header argument, which specifies the values of lisp variables in
>> a let-binding which encloses the src block execution?

>
> The whole logic in org is that, if I understand correctly, of the
> smaller unit (e.g. file -> subtree -> ... -> code block) inheriting
> properties, variables, ... from the next larger unit - introducing a
> possibility to disable inheritance, would introduce a completely new
> level of complexity.
> I think that one should rather introduce a way of
> unsetting e.g. variable values to have the same effect, but still
> sticking with the whole inheritance logic.
> I reslly think that it might be dangerous to open the possibility to
> break this inheritance principle.

Hi Rainer,

Org already has a way to disable inheritance in general, and on a
property-by-property basis. See

http://orgmode.org/manual/Property-inheritance.html#Property-inheritance

and the docstrings for the variable org-use-property-

[Orgmode] Re: [BABEL] "unset" :var definitions for subtree

[Dan Davison]

[...]
>> 2. It should be possible somehow to include the options together with
>>the shebang, or to replace :shebang with a more general "preamble"
>>concept. Or to make :shebang accept a code block as its value.
>> 
>> 
>> #+BABEL: :var A=13
>> #+BABEL: :var B=14
>> 
>> #+header: :shebang #!/bin/bash #$ -cwd
>> #+begin_src sh :tangle script.sh
>> # empty
>> #+end_src
>> 
>
> Similar to above - should work, but now the options for torque are
> hidden in the shebang - which is not to nice, but should work - although
> changing the options is not nearly as nice as if the options are in the
> source block.

It seems that we should be able to put the preamble lines in a src
block. This works, but only after making an alteration to the sbe
function (below) so that it will allow multiple line results. Maybe Eric
will have some ideas here.

---
#+BABEL: :var A=13
#+BABEL: :var B=14

#+srcname: sheb
#+begin_src sh :results output
echo '#!/bin/bash'
echo '#$ -cwd'
#+end_src

#+header: :shebang (sbe sheb)
#+begin_src sh :tangle script.sh
# empty
#+end_src
---


   (setq source-block (symbol-name source-block)))
-(org-babel-table-truncate-at-newline ;; org-table cells can't be multi-line
  (if (and source-block (> (length source-block) 0))
  (let ((params
 (eval `(org-babel-parse-header-arguments
@@ -116,7 +115,7 @@ example above."
 ")")
(org-babel-execute-src-block
 nil (list "emacs-lisp" "results" params) '((:results . "silent"
-   ""
+   "")))


Dan

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re-map global key while in the agenda?

[Nathan Neff]

Hello,

I have  i mapped to 'org-clock-in and I would also like  i to
clock in while I'm in the agenda.

I have  i bound using global-set-key like this:
(global-set-key (kbd " i") 'org-clock-in)

And I tried using "define-key" to redefine F3-i in agenda mode
like this:

(add-hook 'org-agenda-mode-hook
 '(lambda ()
(define-key org-agenda-mode-map (kbd " i")
'org-agenda-clock-in)
))

But, when I'm in the agenda,  i is always mapped to 'org-clock-in,
not 'org-agenda-clock-in

Is it possible to redefine a global key mapping in the agenda?

Thanks,
--Nate

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] org-git-link does not support locational information within file

[Bastien]

Hi Gregor,

Gregor Kappler  writes:

>  2. use git versioned files transparently, i.e. org-git-store-link
> should support search (org-ids and text files) in linked git
> revisions of files.

I've look into this.  We could code things to add a search string:

  [[git:~/my.org::master@{2011-02-07}::Org code]]
 ^^

... but I'm reluctant to change the general syntax of links, even 
if that's just for git links.

>  3. define an interactive function that can update the revision
> information of a link at mark to the current branch head of the
> file (so I can update all links to new FS folder structure.)

You mean update

  [[git:~/my.org::master@{2011-02-07}::Org code]]

to 

  [[git:~/my.org::master@{2011-02-11}::Org code]]

?

Can you provide an explicit example?

> I am still lame at elisp - so my implementation skills are
> limited. With the great work in org-git-link all backend stuff seems
> there, only needing more glue. Any hints how to achieve this would be
> very welcome!

org-git-link.el is quite readable, and I'd welcome ideas on how to
extend it to fulfill your wishes without extending Org's link syntax 
too much...

Thanks!

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [BABEL] "unset" :var definitions for subtree

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/11/2011 02:41 PM, Dan Davison wrote:
> Rainer M Krug  writes:
> 
>> On 02/11/2011 01:19 PM, Dan Davison wrote:
>>> "Eric Schulte"  writes:
>>>
 Rainer M Krug  writes:

> On 02/10/2011 02:27 AM, Eric Schulte wrote:
>> Rainer M Krug  writes:
>>
>>> Hi
>>>
>>> For one project, I am usinr org to write submit scripte to a cluster
>>> runing torqu. The important bit in this is, that between the shebang and
>>> the code, no other executable line must occur. As I am using variables
>>> in org (:var) they will occur just after the shebang, which causes a
>>> problem for torque. So, my question is, is there a way to "unset"
>>> variables defined by using :var for a subtree?
>>>
>>
>> Hi Rainer,
>>
>> Interesting question... unfortunately I don't think that removing
>> variables from header arguments is possible under the current setup.
>>
>> Perhaps in your case you could add a function to the post-tangle hook,
>> which recognizes when it is being called in a just-tangled torqu script
>> (maybe by searching for a series of #PBS lines), and then removes any
>> lines between the shebang and the first #PBS line?
>
> That is also an option - what I am using at the moment is to use
> :no-expand as a code block specific header argument. But this raises the
> other question:
>
> Can I set the :no-expand in a properties block? As far as I understand,
> in the properties block I have the argument and the value - but what do
> I do with :noexpand?
>
> :PROPERTIES:
> :var: A=13
> :no-expand
> :END:
>

 You can just set it to "yes" or really any value you like (the value
 will be ignored).  I did however have to add "no-expand" to the list of
 header argument names searched for in property blocks -- I just pushed
 up a patch to this effect.

>
>>
>> More generally, I wonder what a natural method would be to allow
>> unsetting of pre-set header arguments for local blocks or subtrees?
>> This may only apply to the :var header argument, as most others have a
>> default setting which can be actively set.  If you have any ideas for a
>> natural syntax for such an operation I'd be happy to hear it.
>
> First solution (probably the easiest to implement) would be along the
> lines of the :no-expand header argument -
>
> :expand-var yes
> and
> :expand-var no
>
> This could possibly be expanded to
> :expand-var A B C
>
> which would expand only the variables A B and C
>
> One step further: one could define groups of variables, like
> :var-group X=A,B,C
> or a similar syntax
>
> and then
> :expand-var X
> would expand A B and C
>
> This all would not be real unset - but a possibility for unsetting would 
> be
>
> :var B=
>
> or
>
> :var-unset B
>
> i.e. if no value is specified in :var, the variable will be removed
> (i.e. unset) - one could also use a null value (if it exists in elisp):
>
> :var B=(null)
>

 Thanks for the ideas,

 I think you're right that something along the lines of the above should
 be the easiest to implement, however after reading these suggestions,
 I'm thinking that more generally there are a couple of other header
 arguments which could need to be unset, namely
 - file
 - dir
 - session
 - shebang
 some of these (like session) accept a "none" value which has the effect
 of un-setting the header argument.

 It would be nice to generalize whatever solution we apply across all
 types of header argument (both for implementation and for user
 simplicity).
>>>
>>> Some half thought-through suggestions. Sorry if this is a bit
>>> disorganized.
> 
>>> I wonder whether we should be using Org property inheritance here. If it
>>> were possible to turn off property inheritance temporarily for the
>>> execution of the block, then it could be prevented from inheriting the
>>> header args that you don't want it to inherit. Perhaps babel could offer
>>> a :bind header argument, which specifies the values of lisp variables in
>>> a let-binding which encloses the src block execution?
> 
>>
>> The whole logic in org is that, if I understand correctly, of the
>> smaller unit (e.g. file -> subtree -> ... -> code block) inheriting
>> properties, variables, ... from the next larger unit - introducing a
>> possibility to disable inheritance, would introduce a completely new
>> level of complexity.
>> I think that one should rather introduce a way of
>> unsetting e.g. variable values to have the same effect, but still
>> sticking with the whole inheritance logic.
>> I reslly think that it might be dangerous to open the possibility to
>> break this inheritance principle.
> 
> Hi R

Re: [Orgmode] question about opening a file in .emacs

[Filippo A. Salustri]

That's fine. I just thought I'd ask.
Cheers.
Fil

On 11 February 2011 09:22, Bastien  wrote:

> "Filippo A. Salustri"  writes:
>
> > It might be something wrong with the code I use, or it might be an
> > Aquamacs issue, or it might be a general emacs issue.
>
> In any case, not an Org issue -- better to ask on the Aquamacs list :)
>
> --
>  Bastien
>



-- 
Filippo A. Salustri, Ph.D., P.Eng.
Mechanical and Industrial Engineering
Ryerson University
350 Victoria St, Toronto, ON
M5B 2K3, Canada
Tel: 416/979-5000 ext 7749
Fax: 416/979-5265
Email: salus...@ryerson.ca
http://deseng.ryerson.ca/~fil/
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: Announcing org-contacts, a bbdb-like contact manager for Org

[Stefan Monnier]

> So the question is: how can the completion-ignore-case value be
> propagated from the completion gathering function in
> `completion-at-point-functions' to the function that actually applies
> this completion, without having to modify the global or buffer local
> value of `completion-ignore-case'?

Assuming you have a completion table in variable `table', you should be
able to construct a new completion table that's case-insensitive with
something like the untested code below:

(defun completion-table-case-fold (table string pred action)
  (let ((completion-ignore-case t))
(complete-with-action action table string pred)))

[...]
   (let ((newtable
  (apply-partially #'completion-table-case-fold table)))
 [...])

where completion-table-case-fold is an auxiliary function which
(c|sh)ould be added to minibuffer.el.

The case-sensitivity of the completion code is indeed problematic.
Here's for example an excerpt from minibuffer.el:

;; - case-sensitivity currently confuses two issues:
;;   - whether or not a particular completion table should be case-sensitive
;; (i.e. whether strings that differ only by case are semantically
;; equivalent)
;;   - whether the user wants completion to pay attention to case.
;;   e.g. we may want to make it possible for the user to say "first try
;;   completion case-sensitively, and if that fails, try to ignore case".


Stefan

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Missing line breaks in ps export of agenda

[Bastien]

Hi Julia,

Julia Jacobson  writes:

> The export of an agenda to a Postscript file doesn't seem break lines.

I cannot reproduce this.

What version of Org/Emacs are you using?

The result of wrapped lines is not very nice anyway, so better to try
sticking to short agenda headings.

Best,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] automatic regression test (again)

[Eric Schulte]

Michael Brand  writes:

> (this is a fork of
> http://thread.gmane.org/gmane.emacs.orgmode/35415/focus=37389)
>
> Hi Bastien
>
> On Thu, Feb 10, 2011 at 15:35, Bastien  wrote:
>> Michael, thanks for the detailed step-by-step way of reproducing the
>> problem with a bare emacs!  Quite useful.
>
> If a regression test set would already be implemented or integrated in
> Org I would like a lot to add by myself also these test cases above as
> automatic test cases. _This_ would be really useful. Regression test
> would be on the very top on my wish list for Org, like it is for any
> project.
>

Hi Michael,

These previous discussion resulted in the creation of a unit test suite
for Org-mode.  Look in the testing, specifically at

testing/README.org
testing/org-test.el

Any contributions to the test suite would be most appreciated!

Thanks -- Eric

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] question about opening a file in .emacs

[Bastien]

"Filippo A. Salustri"  writes:

> It might be something wrong with the code I use, or it might be an
> Aquamacs issue, or it might be a general emacs issue.

In any case, not an Org issue -- better to ask on the Aquamacs list :)

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [BABEL] "unset" :var definitions for subtree

[Dan Davison]

"Eric Schulte"  writes:

> Hi Dan,
>
> Many interesting suggestions, but I don't see how any of them are
> simpler (either conceptually or in terms of implementation) than
> defining a way to "unset" a variable previously set at a higher level of
> generality. Is it the concept or the syntax of the previous suggestions
> that you find objectionable?
>
> I thought that either the :remove or :unset options suggested by Rainer
> seemed intuitive.  I understand your point about not using a keyword,
> and I agree (especially as our parsing is currently based on the
> assumption that keywords are header arguments).  So maybe the
> following...
>
> this would unset all variables
> #+begin_src emacs-lisp :var unset
>   ;; code
> #+end_src
>
> this would unset only the variable A
> #+begin_src emacs-lisp :var unset(A)
>   ;; code
> #+end_src
>
> approaching this from another direction, we could have an :unset header
> argument, which takes as arguments the names of other header arguments
> to unset.  Could be used like this...
>
> #+begin_src emacs-lisp :unset '(var noweb)
>   ;; code
> #+end_src
>
> although it's not clear how to use such a construct to unset particular
> variables...
>
> So what do you think?  Should we explore syntactic options, or is there
> something wrong with the very idea of a way of unsetting previously
> bound header arguments?

I agree, the things I was talking about don't end up being simpler in
terms of usage for this case. My thinking was that variable unsetting
might be something that would be required fairly rarely, and so it might
be worth appropriate to support it as part of a more general/powerful
mechanism tied into Org properties, or even that hook.

Before we proceed with the variable unsetting, could someone provide a
motivating example, just to convince ourselves that the extra features
are justified? (The conclusion of another message was that the torque
script example was more a motivating example for shebang/preamble
processing than for variable unsetting.)

Dan

>
> Thanks -- Eric
>
> More Comments in-line below:
>
> [...]
>>>
>>> It would be nice to generalize whatever solution we apply across all
>>> types of header argument (both for implementation and for user
>>> simplicity).
>>
>> Some half thought-through suggestions. Sorry if this is a bit
>> disorganized.
>>
>> I wonder whether we should be using Org property inheritance here. If
>> it were possible to turn off property inheritance temporarily for the
>> execution of the block, then it could be prevented from inheriting the
>> header args that you don't want it to inherit.
>
> Turning off property inheritance would break inheritance of *all* types
> of header argument (which is probably not desirable) and would not be
> useful for default values set in e.g., org-babel-default-header-args.
>
> Also, how is this simpler than unsetting header arguments?
>
>> Perhaps babel could offer a :bind header argument, which specifies the
>> values of lisp variables in a let-binding which encloses the src block
>> execution?
>>
>
> hmm, that is certainly an interesting Idea, and (separate from this
> discussion of the need to unset variables) may be very useful in some
> contexts -- although changing the lexical scope during the execution of
> a code block probably wouldn't be normal usage.  In fact in many cases
> this would have no effect because we explicitly ensure variables have
> the value needed my our code, so often the user would end up with
> situations like the following
>
> ;; babel code
> (let ((some-org-variable 'user-desired-value))
>   ;; more babel processing
>   ;; ...
>   ;; variable is about to be used
>   (let ((some-org-variable 'babel-default-value)) ; <- we set explicitly
> ;; code that uses `some-org-variable'
> ))
>
>>
>> #+header: :bind org-babel-use-property-inheritance nil
>> #+begin_src sh :tangle script.sh :shebang #!/bin/bash
>> #$ -cwd
>> #+end_src
>>
>> with a patch along these lines
>>
>> +(defvar org-babel-use-property-inheritance t
>> +  "When looking for org-babel header arguments in in-buffer
>> +  properties, this variable is passed as the INHERIT argument to
>> +  the function `org-enrty-get'")
>> +
>>  (defvar org-file-properties)
>>  (defun org-babel-params-from-properties (&optional lang)
>>"Retrieve parameters specified as properties.
>> @@ -864,7 +870,7 @@ may be specified in the properties of the current 
>> outline entry."
>>   (lambda (header-arg)
>> (and (setq val
>>(or (condition-case nil
>> -  (org-entry-get (point) header-arg t)
>> +  (org-entry-get (point) header-arg 
>> org-babel-use-property-inheritance)
>>  (error nil))
>>(cdr (assoc header-arg org-file-properties
>>  (cons (intern (concat ":" header-arg))
>>
>
> So you dealt with the issue I noticed above by defining a separate
> vari

[Orgmode] Better sitemap formating

[Manuel Giraud]

Hi,

Here's a patch that make the sitemap entry formating coherent with the
new html-pre/postamble one. 

While here I was trying to add some documentation about this feature in
org.texi but I end up copy/pasting or paraphrasing the docstring of
correspondant customs. Is it acceptable for the documentation or plain
useless?

>From 766b0db7d0189d2edb0d8799c3424d62f9ac4e47 Mon Sep 17 00:00:00 2001
From: Manuel Giraud 
Date: Fri, 11 Feb 2011 15:32:58 +0100
Subject: [PATCH] org-publish.el: sitemap formating coherent with new preamble

Adopt downcase for format directive to be coherent with the new
pre/postamble formating.

Use `format-spec' function instead of `org-replace-escapes'.
---
 lisp/org-publish.el |   21 ++---
 1 files changed, 10 insertions(+), 11 deletions(-)

diff --git a/lisp/org-publish.el b/lisp/org-publish.el
index a7aaee2..3a29d06 100644
--- a/lisp/org-publish.el
+++ b/lisp/org-publish.el
@@ -55,6 +55,7 @@
   (require 'cl))
 (require 'org)
 (require 'org-exp)
+(require 'format-spec)
 
 (eval-and-compile
   (unless (fboundp 'declare-function)
@@ -271,13 +272,13 @@ in the sitemap."
   :group 'org-publish
   :type 'string)
 
-(defcustom org-publish-sitemap-file-entry-format "%T"
+(defcustom org-publish-sitemap-file-entry-format "%t"
   "How a sitemap file entry is formated.
 You could use brackets to delimit on what part the link will be.
 
-%T is the title.
-%A is the author.
-%D is the date formated using `org-publish-sitemap-date-format'."
+%t is the title.
+%a is the author.
+%d is the date formated using `org-publish-sitemap-date-format'."
   :group 'org-publish
   :type 'string)
 
@@ -816,13 +817,11 @@ Default for SITEMAP-FILENAME is 'sitemap.org'."
 (or visiting (kill-buffer sitemap-buffer
 
 (defun org-publish-format-file-entry (fmt file project-plist)
-  (org-replace-escapes fmt
-		   (list (cons "%T" (org-publish-find-title file))
-			 (cons "%D" (format-time-string 
-	 sitemap-date-format 
-	 (org-publish-find-date file)))
-			 (cons "%A" (or (plist-get project-plist :author)
-	user-full-name)
+  (format-spec fmt
+	 `((?t . ,(org-publish-find-title file))
+	   (?d . ,(format-time-string sitemap-date-format 
+	  (org-publish-find-date file)))
+	   (?a . ,(or (plist-get project-plist :author) user-full-name)
 			
 (defun org-publish-find-title (file)
   "Find the title of FILE in project."
-- 
1.7.1


-- 
Manuel Giraud
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Preview link to text file inline?

[Bastien]

Hi Piter,

Piter_  writes:

> Preview link to text file inline? Is it possible in orgmode?

No it's not.  You can view the file in another window with C-c C-o.

HTH,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Mails with icalendar appointments (Was: Org support for the notmuch mail client)

[Andreas Amann]

I get quite a few emails in icalendar format which are requests for
appointments. To avoid unnecessary distraction, I would like to quickly
convert them into org-mode TODO list items. What is the recommended way
to do this? Can the org-capture framework be used for this?

I use notmuch to access email, and org-notmuch.el as capture interface
but I guess the same problem occurs for users of gnus or other email
clients. Do solutions exist for them?

I also experimented a bit with "icalendar-import-buffer", which gives a
diary entry that can show up in the agenda. Are there any better
options? Any pointers welcome. 

Andreas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Org support for the notmuch mail client"

[Bart Bunting]

+1 from me also.

Bart


On Wed, 09 Feb 2011 20:42:44 +, Andreas Amann  wrote:
> Hi Bastien,
> 
> > I'm not using notmuch myself and I would welcome feedback from notmuch
> > Org users.  I would happily add it to org-mode/contrib/lisp if this is
> > proves useful to several people around.
> 
> Just to say that I use Matthieu's code to do my daily "email to
> todolist" conversion. Nothing spectacular but works reliably as
> advertised. In my opinion it would be a useful addition to org-mode.
> 
> Andreas
> 
> 
> 
> ___
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

-- 

Bart Bunting

URSYS Pty. Ltd 
461 Parramatta Rd. Leichhardt NSW  2040  Australia
Ph.   +61 2 8745 2811
Fax  +61 2 8745 2828

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Insert ampersand in HTML export?

[Uriel Avalos]

On Fri, 11 Feb 2011 09:34:08 +0100
Carsten Dominik  wrote:

> 
> On Feb 10, 2011, at 9:25 PM, Uriel Avalos wrote:
> 
> > How do you insert the actual & character in an HTML export?
> >
> > I'm trying to write a macro to insert a MATHML snippet but org-mode  
> > converts & to &.
> >
> > How can I prevent that behavior?
> 
> Hi Uriel,
> 
> do you really want everyone here to construct their own test case for  
> this?
> 
> Please provide an example file with the macro definition and its
> use to make it as easy as possible for someone to try it out and fix it.
> 
> Thanks
> 
> - Carsten
> 

Look, there isn't really a "test" case. I'm just asking if this feature is 
available.
The docs just say that & exports to & in HTML export and \$ in latex 
export. 
I'm asking if there's a way to disable that feature on a case-by-case basis 
i.e., 
I want & to export to & in HTML export for some situations. Hope that's clear 
enough.

Here's a test macro:

#+MACRO: ANG @@@&x2220;@@$1@@@/math>

This should be "angle $1". The MATML snippet works fine in a HTML file in 
firefox linux but the macro does not. I get this in the HTML export:

  & #x2220;   ...   

& gets incorrectly converted to &

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Accepted] [Orgmode] Better sitemap formating

[Bastien Guerry]

Patch 594 (http://patchwork.newartisans.com/patch/594/) is now "Accepted".

Maintainer comment: none

This relates to the following submission:

http://mid.gmane.org/%3C87lj1m7hts.fsf%40univ-nantes.fr%3E

Here is the original message containing the patch:

> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [Orgmode] Better sitemap formating
> Date: Fri, 11 Feb 2011 19:43:11 -
> From: Manuel Giraud 
> X-Patchwork-Id: 594
> Message-Id: <87lj1m7hts@univ-nantes.fr>
> To: emacs-orgmode 
> 
> Hi,
> 
> Here's a patch that make the sitemap entry formating coherent with the
> new html-pre/postamble one. 
> 
> While here I was trying to add some documentation about this feature in
> org.texi but I end up copy/pasting or paraphrasing the docstring of
> correspondant customs. Is it acceptable for the documentation or plain
> useless?
> 
> 
> >From 766b0db7d0189d2edb0d8799c3424d62f9ac4e47 Mon Sep 17 00:00:00 2001
> From: Manuel Giraud 
> Date: Fri, 11 Feb 2011 15:32:58 +0100
> Subject: [PATCH] org-publish.el: sitemap formating coherent with new preamble
> 
> Adopt downcase for format directive to be coherent with the new
> pre/postamble formating.
> 
> Use `format-spec' function instead of `org-replace-escapes'.
> ---
>  lisp/org-publish.el |   21 ++---
>  1 files changed, 10 insertions(+), 11 deletions(-)
> 
> diff --git a/lisp/org-publish.el b/lisp/org-publish.el
> index a7aaee2..3a29d06 100644
> --- a/lisp/org-publish.el
> +++ b/lisp/org-publish.el
> @@ -55,6 +55,7 @@
>(require 'cl))
>  (require 'org)
>  (require 'org-exp)
> +(require 'format-spec)
>  
>  (eval-and-compile
>(unless (fboundp 'declare-function)
> @@ -271,13 +272,13 @@ in the sitemap."
>:group 'org-publish
>:type 'string)
>  
> -(defcustom org-publish-sitemap-file-entry-format "%T"
> +(defcustom org-publish-sitemap-file-entry-format "%t"
>"How a sitemap file entry is formated.
>  You could use brackets to delimit on what part the link will be.
>  
> -%T is the title.
> -%A is the author.
> -%D is the date formated using `org-publish-sitemap-date-format'."
> +%t is the title.
> +%a is the author.
> +%d is the date formated using `org-publish-sitemap-date-format'."
>:group 'org-publish
>:type 'string)
>  
> @@ -816,13 +817,11 @@ Default for SITEMAP-FILENAME is 'sitemap.org'."
>  (or visiting (kill-buffer sitemap-buffer
>  
>  (defun org-publish-format-file-entry (fmt file project-plist)
> -  (org-replace-escapes fmt
> -(list (cons "%T" (org-publish-find-title file))
> -  (cons "%D" (format-time-string 
> -  sitemap-date-format 
> -  (org-publish-find-date file)))
> -  (cons "%A" (or (plist-get project-plist :author)
> - user-full-name)
> +  (format-spec fmt
> +  `((?t . ,(org-publish-find-title file))
> +(?d . ,(format-time-string sitemap-date-format 
> +   (org-publish-find-date file)))
> +(?a . ,(or (plist-get project-plist :author) user-full-name)
>   
>  (defun org-publish-find-title (file)
>"Find the title of FILE in project."
> -- 
> 1.7.1
> 
> 

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [BABEL] "unset" :var definitions for subtree

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/11/2011 02:49 PM, Dan Davison wrote:
> [...]
>>> 2. It should be possible somehow to include the options together with
>>>the shebang, or to replace :shebang with a more general "preamble"
>>>concept. Or to make :shebang accept a code block as its value.
>>>
>>> 
>>> #+BABEL: :var A=13
>>> #+BABEL: :var B=14
>>>
>>> #+header: :shebang #!/bin/bash #$ -cwd
>>> #+begin_src sh :tangle script.sh
>>> # empty
>>> #+end_src
>>> 
>>
>> Similar to above - should work, but now the options for torque are
>> hidden in the shebang - which is not to nice, but should work - although
>> changing the options is not nearly as nice as if the options are in the
>> source block.
> 
> It seems that we should be able to put the preamble lines in a src
> block. This works, but only after making an alteration to the sbe
> function (below) so that it will allow multiple line results. Maybe Eric
> will have some ideas here.

I think that would be a good idea and make it much more flexible.
If one could then have a source block which would only consist of the
text and not with e.g. echo '', I think it would be perfect.


> 
> ---
> #+BABEL: :var A=13
> #+BABEL: :var B=14
> 
> #+srcname: sheb
> #+begin_src sh :results output
> echo '#!/bin/bash'
> echo '#$ -cwd'
> #+end_src
> 
> #+header: :shebang (sbe sheb)
> #+begin_src sh :tangle script.sh
> # empty
> #+end_src
> ---
> 
> 
>(setq source-block (symbol-name source-block)))
> -(org-babel-table-truncate-at-newline ;; org-table cells can't be 
> multi-line
>   (if (and source-block (> (length source-block) 0))
>   (let ((params
>  (eval `(org-babel-parse-header-arguments
> @@ -116,7 +115,7 @@ example above."
>  ")")
> (org-babel-execute-src-block
>  nil (list "emacs-lisp" "results" params) '((:results . 
> "silent"
> -   ""
> +   "")))
> 
> 
> Dan


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

Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa

Tel:+33 - (0)9 53 10 27 44
Cell:   +27 - (0)8 39 47 90 42
Fax (SA):   +27 - (0)8 65 16 27 82
Fax (D) :   +49 - (0)3 21 21 25 22 44
Fax (FR):   +33 - (0)9 58 10 27 44
email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1VQCEACgkQoYgNqgF2egqnvgCcDSl/VCKmgUqXsegDSxuQOAyo
4RgAnj+I+sunbYC5UtY67llifgdgw8Vr
=lRR9
-END PGP SIGNATURE-

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Announcing org-contacts, a bbdb-like contact manager for Org

[Darlan Cavalcante Moreira]

This is awesome. I always wanted to move from bbdb to org for my contacts.
Any chance this will work with other Emacs mail clients, such as
Wanderlust?

--
Darlan

At Wed, 09 Feb 2011 10:02:58 +0100,
Julien Danjou  wrote:
> 
> [1  ]
> [1.1  ]
> Hi,
> 
> Following my short presentation at the Paris OrgCamp, I've now written a
> page and officially released org-contacts. It is a contact manager based
> on Org, that can possibly replace BBDB for certain usage.
> 
>http://julien.danjou.info/org-contacts.html
> 
> -- 
> Julien Danjou
> ❱ http://julien.danjou.info
> [1.2  ]
> 
> [2  ]
> ___
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Agenda and one-line diary display

[Bastien]

Hi Rasmus,

Rasmus Pank Roulund  writes:

> I have finally found a tolerable solution to include Google calendars
> into Emacs and thus Org using "emacs-google"[1].
>
> However, one thing is bothering me about the way Org agenda view handles
> my newly populated diary file. It shows too much information! Basically,
> I want /one line per entry/. If I want more info I'll just hit the
> entry. The reason is that I will often include a lot of extra
> information for each calendar/diary entry. When needed, I will fetch it
> but it usually preclude the overview that I wish to obtain in the agenda
> view.
>
> Here is a simple agenda example: 
>
> ,
> |   Diary:  Semester start
> |   Diary:  Location: Lund University
> |   Diary:  Status: CONFIRMED (UID: 
> 5g7mb67iupjvf75cdorlr1b...@google.com)
> `
>
> And the corresponding diary code:
>
> ,
> | %%(and (diary-block 1 17 2011 1 17 2011)) Semester start
> |Location: Lund University
> |Status: CONFIRMED(UID: 
> 5g7mb67iupjvf75cdorlr1b...@google.com)
> `
>
> What I want to agenda view to show is merely: 
>
> ,
> |   Diary:  Semester start
> `
>
> Or, even better:
>
> ,
> |   Diary:  Semester start (Lund University)
> `

We can hack around to display multilines diary entries on a single agenda
line but then this diary entry would not properly sneak into the agenda:

02/11/2011
  Bill B. visits Princeton today
  2pm Cognitive Studies Committee meeting
  2:30-5:30 Liz at Lawrenceville
  4:00pm Dentist appt
  7:30pm Dinner at George's
  8:00-10:00pm concert

I guess many people have such multilines entries.

So I'd say for now no, you cannot reduce your diary entry to just one
line.

Best,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] A way to export agenda with links into org-files to html ?

[Bastien]

Hi Marc-Oliver,

Marc-Oliver Ihm  writes:

> The html exporter gives excellent results for all of my org-files and
> with org-write-agenda it is very easy to write the agenda to file.
>
> However, in the html-version of the agenda there are no links.

Actually, htmlize.el is designed to handle links.

  (setq htmlize-generate-hyperlinks t)

should do.

Sadly enough, htmlize.el only handles  links. 

Patch to make htmlize.el handle org links welcome!

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: :export: tag shows up in headings of output pdf

[phaebz]

On 02/11/2011 11:49 AM, phaebz wrote:
> I am using org-mode 7.3 release.
>
> Problem: A file such as
>
> * heading to be exported :export:
>
> * some other heading
>
> gets exported to
>
> 1. heading to be exported :export:
>
> With a literal :export: tag in the pdf output heading. I have not customized 
> any relevant export options.
>
> Do I miss something?
>
> Any tips / hints are much appreciated
>
> Michael Bach

never mind. I sorted it out, my own mistake. For completeness: One way is 
"tags:nil" in a #+OPTION: line...

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] multiple agenda buffers

[Bastien]

Hi Suvayu,

suvayu ali  writes:

> I was wondering whether it was possible to have multiple agenda buffers
> at the same time. My use case is when I want to look for two differnt
> but related things, or when I want to search while having my daily (or
> weekly) agenda visible. I found references in the archives[fn:1] stating
> that it was not possible at the time. Has the situation changed?

No, the situation has not changed to this respect.

I reckon your use-case makes sense, but I'm not sure how useful it would
be in general.

It would be a bit like being able to open several email inboxes at the
same time, for the sake of comparing informations from various folders.

Email inboxes and agenda views are made to be _processed_: having more
than one open at the same time might lead to the bad habit of fiddling
with buffers instead of processing agenda items...

Not a strong opinion, just a thought,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Better sitemap formating

[Bastien]

Hi Manuel,

Manuel Giraud  writes:

> Here's a patch that make the sitemap entry formating coherent with the
> new html-pre/postamble one. 

Applied, thanks.

> While here I was trying to add some documentation about this feature in
> org.texi but I end up copy/pasting or paraphrasing the docstring of
> correspondant customs. Is it acceptable for the documentation or plain
> useless?

I guess it's acceptable -- please provide a patch.

Thanks!

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] how to create a one page weekly schedule

[Bastien]

Hi Detlef,

Detlef Steuer  writes:

> Now I _really_ would like to see or export to something like:
>
> * Schedule for  17.1. - 21.1.2011 
> |   | Mo | Tu  | We| Th | Fr|
> |   8-9 || |   ||   |
> |  9-10 | 9:00 lecture b | |   ||   |
> | 10-11 | -- 10:30   | |   ||   |
> |   ... | ..and so on| ... |   | .. | ..|
> | 16-17 || |   || lecture a |
> | 17-18 || |   ||   |
> | 19-20 || | sport ||   |
> | 20-21 || | sport ||   |
>
>
> Is that already possible? Has anyone implemented such a scheme?
> Any ideas how to achieve such a look, may be using external tools?

That'd be quite an amount of work and I won't undertake it myself.

Maybe have a look at contrib/scripts/org2hpda -- it creates great
printed calendars.

HTH,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Agenda and one-line diary display

[Rasmus Pank Roulund]

Hi Bastien,

Thanks for your reply.


02/11/2011
   Bill B. visits Princeton today
   2pm Cognitive Studies Committee meeting

Sounds interesting.

   2:30-5:30 Liz at Lawrenceville
   4:00pm Dentist appt
   7:30pm Dinner at George's
   8:00-10:00pm concert

Busy day :)

Here is an example of a diary going all wrong

,
|
| Friday 11 February 2011
|8:00.. 
|   10:00.. 
|   12:00.. 
|   14:00.. 
|   Diary:  14:00-15:30 Professor Jesper Jespersen – 40 års jubilæum 
i statens tjeneste

|   16:00.. 
|   18:00.. 
|   Diary:  18:00-23:55 Fest
|   20:00.. 
|   overview:   In   3 d.:  TODO 
[[file:institutions/assignment2.tex][Assignment 2]]
|   overview:   In   7 d.:  TODO 
[[file:growth/assignment1.tex][Assignment 1]]

|   overview:   In   7 d.:  TODO [[file:labor/lab/lab1.Rnw][Lab1]]
|   Diary:  Location: Sabina
|   Diary:  Status: CONFIRMED		(UID: 
n14pdnolar20orvikj8996i...@google.com)
|   Diary:  Desc: 1. Politisk økonomi - Fra ADAM til DREAM:  Jesper 
Jespersen

|   Diary:  2. Politisk rådgivning:fhv. departementschef Jørgen Rosted
|   Diary:  3. Politisk praksis:fhv. økonomiminister Marianne Jelved, MF
|   Diary:  Location: Roskilde Universitet (RUC) hus 25.2
|   Diary:  Status: CONFIRMED		(UID: 
sul5dt2e6kbnp9j3lk2vuaa...@google.com)

`

It is a bit of a SNAFU. Here is the diary

,
| 2/11/2011 18:00-23:55 Fest
|Location: Sabina
|Status: CONFIRMED  (UID: n14pdnolar20orvikj8996i...@google.com)
|
| [...] omitting 22 lines [...]
|
| 2/11/2011 14:00-15:30 Professor Jesper Jespersen – 40 års jubilæum i 
statens tjeneste

|Desc: 1. Politisk økonomi - Fra ADAM til DREAM:  Jesper Jespersen
|  2. Politisk rådgivning:fhv. departementschef Jørgen Rosted
|  3. Politisk praksis:fhv. økonomiminister Marianne Jelved, MF
|Location: Roskilde Universitet (RUC) hus 25.2
|Status: CONFIRMED  (UID: sul5dt2e6kbnp9j3lk2vuaa...@google.com)
`

,
|
| Friday 11 February 2011
|8:00.. 
|   10:00.. 
|   12:00.. 
|   14:00.. 
|   Diary:  14:00-15:30 Professor Jesper Jespersen – 40 års jubilæum 
i statens tjeneste

|   16:00.. 
|   18:00.. 
|   Diary:  18:00-23:55 Fest
|   overview:   In   3 d.:  TODO 
[[file:institutions/assignment2.tex][Assignment 2]]
|   overview:   In   7 d.:  TODO 
[[file:growth/assignment1.tex][Assignment 1]]

|   overview:   In   7 d.:  TODO [[file:labor/lab/lab1.Rnw][Lab1]]
`


So what I'd want was just to display. If I'd want more info I'd just RET
the line.

The fuss might be caused by an auto-generated diary. I don't know.




So I'd say for now no, you cannot reduce your diary entry to just one
line.


Too bad.


Have a nice weekend.

—Rasmus

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [BABEL] "unset" :var definitions for subtree

[Eric Schulte]

Hi Dan,

Many interesting suggestions, but I don't see how any of them are
simpler (either conceptually or in terms of implementation) than
defining a way to "unset" a variable previously set at a higher level of
generality.  Is it the concept or the syntax of the previous suggestions
that you find objectionable?

I thought that either the :remove or :unset options suggested by Rainer
seemed intuitive.  I understand your point about not using a keyword,
and I agree (especially as our parsing is currently based on the
assumption that keywords are header arguments).  So maybe the
following...

this would unset all variables
#+begin_src emacs-lisp :var unset
  ;; code
#+end_src

this would unset only the variable A
#+begin_src emacs-lisp :var unset(A)
  ;; code
#+end_src

approaching this from another direction, we could have an :unset header
argument, which takes as arguments the names of other header arguments
to unset.  Could be used like this...

#+begin_src emacs-lisp :unset '(var noweb)
  ;; code
#+end_src

although it's not clear how to use such a construct to unset particular
variables...

So what do you think?  Should we explore syntactic options, or is there
something wrong with the very idea of a way of unsetting previously
bound header arguments?

Thanks -- Eric

More Comments in-line below:

[...]
>>
>> It would be nice to generalize whatever solution we apply across all
>> types of header argument (both for implementation and for user
>> simplicity).
>
> Some half thought-through suggestions. Sorry if this is a bit
> disorganized.
>
> I wonder whether we should be using Org property inheritance here. If
> it were possible to turn off property inheritance temporarily for the
> execution of the block, then it could be prevented from inheriting the
> header args that you don't want it to inherit.

Turning off property inheritance would break inheritance of *all* types
of header argument (which is probably not desirable) and would not be
useful for default values set in e.g., org-babel-default-header-args.

Also, how is this simpler than unsetting header arguments?

> Perhaps babel could offer a :bind header argument, which specifies the
> values of lisp variables in a let-binding which encloses the src block
> execution?
>

hmm, that is certainly an interesting Idea, and (separate from this
discussion of the need to unset variables) may be very useful in some
contexts -- although changing the lexical scope during the execution of
a code block probably wouldn't be normal usage.  In fact in many cases
this would have no effect because we explicitly ensure variables have
the value needed my our code, so often the user would end up with
situations like the following

;; babel code
(let ((some-org-variable 'user-desired-value))
  ;; more babel processing
  ;; ...
  ;; variable is about to be used
  (let ((some-org-variable 'babel-default-value)) ; <- we set explicitly
;; code that uses `some-org-variable'
))

>
> #+header: :bind org-babel-use-property-inheritance nil
> #+begin_src sh :tangle script.sh :shebang #!/bin/bash
> #$ -cwd
> #+end_src
>
> with a patch along these lines
>
> +(defvar org-babel-use-property-inheritance t
> +  "When looking for org-babel header arguments in in-buffer
> +  properties, this variable is passed as the INHERIT argument to
> +  the function `org-enrty-get'")
> +
>  (defvar org-file-properties)
>  (defun org-babel-params-from-properties (&optional lang)
>"Retrieve parameters specified as properties.
> @@ -864,7 +870,7 @@ may be specified in the properties of the current outline 
> entry."
>(lambda (header-arg)
>  (and (setq val
> (or (condition-case nil
> -   (org-entry-get (point) header-arg t)
> +   (org-entry-get (point) header-arg 
> org-babel-use-property-inheritance)
>   (error nil))
> (cdr (assoc header-arg org-file-properties
>   (cons (intern (concat ":" header-arg))
>

So you dealt with the issue I noticed above by defining a separate
variable which the user *could* override with a `let'.  This would work
but would require
- rewriting of our code to use custom babel versions of many emacs variables
- requiring users to know both the normal and babel names of these
  variables to effectively modify them using this :bind header argument

Again, this seems much more complex than introducing a way to unset
header arguments.

[...]
>
> On a related note, I wonder whether the #+BABEL line should be
> re-implemented so that it works via setting org-file-properties?
> I.e. made equivalent to a #+PROPERTIES line?
>

Could we just remove #+Babel: lines entirely and use #+property: lines,
which I guess would mean reading in org-file-properties rather than
parsing #+Babel lines.  I agree this sounds like a good idea.

>
> Finally, a feature for babel power users could be to offer a hoo

Re: [Orgmode] re: iCalendar selective export / org-icalendar-verify-function

[Bastien]

Hi Arun,

Arun Persaud  writes:

> I ran into the same problem. I know that there is
> org-icalendar-verify-function, but I'm not sure how to use it... I would
> like to filter for org-export-exclude-tags and also only export entries
> that have a time specified in the schedule timestamp (many of my items
> just have a date).

Please test Org from latest git repo: 

  (setq org-icalendar-honor-noexport-tag t)

and icalendar export will skip :noexport: entries.

HTH,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Hints for scheduling using Agenda

[Bastien]

Hi Nathan,

Nathan Neff  writes:

> I'm starting to use column mode in the Agenda, where the estimated
> effort for each TODO item is shown.  The sums of the estimated
> effort is totaled for each day.  I like this feature, and want to use it
> to determine when to schedule TODO items.
>
> Does anyone else use column mode in the Agenda to find time slots to
> for scheduling?
>
> My quandry is this:  I use the agenda to show me the TODO items that aren't
> scheduled -- but if I'm already using the agenda to show me the upcoming week
> and the open time-slots, then I have to bounce back and forth between
> the agenda views.

Maybe you can combine these two agendas in a block agenda?

  info:org#Block agenda

HTH,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Go to today in Calendar

[Bastien]

Hi Nathan,

Nathan Neff  writes:

> I just found that you can press "." in the Calendar to jump to today's
> date.

Nice one, I didn't know that!

Thanks for the tip,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] multiple agenda buffers

[Suvayu Ali]

Hi Bastien,

On Fri, 11 Feb 2011 16:20:08 +0100
Bastien  wrote:

> I reckon your use-case makes sense, but I'm not sure how useful it
> would be in general.
> 
> It would be a bit like being able to open several email inboxes at the
> same time, for the sake of comparing informations from various
> folders.
> 
> Email inboxes and agenda views are made to be _processed_: having more
> than one open at the same time might lead to the bad habit of fiddling
> with buffers instead of processing agenda items...
> 
> Not a strong opinion, just a thought,

This is indeed very true. I do fall prey to that sometimes.

However I was wondering, block agenda commands might work at least for
doing multiple searches. But I don't think there is any interactive
interface to it.

If we could have some syntax for specifying prompts for custom agenda
commands (something like capture templates) then it might be possible.
Is that a feasible request?

-- 
Suvayu

Open source is the future. It sets us free.

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Automatic noexport tag based on rules?

[John Hendy]

On Fri, Feb 11, 2011 at 2:34 AM, Carsten Dominik
wrote:

>
> On Feb 9, 2011, at 1:29 AM, John Hendy wrote:
>
> An alternative to using the :noexport: tag, and also to
> the other suggestions given here in this thread would
> be to use `org-map-entries' to physically remove all
> subtrees which match your condition.


And this physically removes the TODOs from the "blob" being exported, not
from my .org files, right? If so, perhaps that would be an option. Strip it
from the stream headed for export.

Thanks for giving the code.


John


> You can call the
> mapper from one of the preprocessing hooks:
>
> (defun my-export-remove-TODO ()
>  (org-map-entries
>  ;; The following form will be evaluated at each matching tree
>  '(progn
> (outline-mark-subtree)  ; mark tree
> (delete-region (point) (mark))) ; remove it
>  ;; Now the tags/property/todo matcher to select trees
>  "LEVEL<15+TODO={.}"
>  ))
>
> ;; Call this after other tree selection has been processed
> (add-hook 'org-export-preprocess-after-tree-selection-hook
>  'my-export-remove-TODO)
>
> The matcher includes a LEVEL<15 test to make sure this will
> not mess with inline tasks.
>
> Export preprocessor hooks are a good place for such tasks.
> Also Nick's proposal could be used in such a hook, but not
> the same hook as I have used above.  Maybe in
> org-export-preprocessor-after-include-files-hook.
>
>
> - Carsten
>
>
>
>
>
>
>> Or simply add the TODO category to the noexport category altogether?
>>
>> I haven't turned up anything quite along these lines. One post suggested
>> using "TODO keyword COMMENT" [1], but that just seems to perhaps exclude
>> from export (didn't try) but I know for sure it removes it from agenda view.
>> I want TODOs in agenda but don't want them showing up with my LaTeX export.
>> I typically print out my work to-date each month or so and have to comb
>> through my org file for that month, manually adding :noexport: to my TODOs.
>> Even if I still do this for a few things here and there... it will save me a
>> lot of time.
>>
>> I suppose I could keep a separate "TODO.org" file, but I really like the
>> process of being able to add them anywhere -- it seems more natural to do
>> that in the flow, particularly in meetings, than to constantly switch
>> buffers or even use remember to keep sending things related to the current
>> topic away to their own island.
>>
>> I'm 80% confident that the answer is ridiculously simply and I just
>> haven't searched the right thing. Thanks for enlightening me!
>>
>>
>> Thanks,
>> John
>> ___
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>
>
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] org-git-link does not support locational information within file

[Samuel Wales]

Hi Bastien,

I think your reluctance to change the syntax is understandable.  Then
again, I'm a proponent of simple syntax.  That is one reason I like
Lisp.

> org-git-link.el is quite readable, and I'd welcome ideas on how to
> extend it to fulfill your wishes without extending Org's link syntax
> too much...

It can be done without extending Org's link syntax at all.

I think questions of syntax are important.  Over time, syntaxes get
complicated, and we need more features, but fear to add them.
Sometimes we end up stuck in the middle, with complicated regexps, not
always factored, not quite sure how it will export or whether it can
be nested or combined or what other syntaxes it will work with or how
search will find it, but also lacking a feature somebody wants.
Adding a feature can sometimes raise questions of how to quote or
escape literal strings that look exactly like the special syntax for
the feature.  I wrote about this in a post called parsing risk with
greater care than I can apply here.

For new features, I think it would be good to consider extensible
syntax, which is a specific, documented proposal for a universal
syntax in which you can add things without breaking other things.  A
very small amount of code is necessary to add a new subfeature to a
feature, and it is even possible to open it up to users.  The parsing
and semantics are worked out once, and apply to all uses of extensible
syntax for all future features and subfeatures.  You can have
confidence that the feature or subfeature you are adding will not have
syntax problems.

(By the way, extensible syntax is a specific proposal for org that
enables many different possible future features, not the general idea
of extending syntax.  Important not to be confused about that.  If you
want to add to link syntax, you are not doing extensible syntax.  But
you can use extensible syntax to implement /any type of link you want
with any subfeatures you want including git features/.  For example, I
supplied an example that allows link coloring according to whether the
link was visited recently.  And I have been wanting another where you
can have bidirectional links using Org-IDs so that you can move both
ends of the link anywhere you want -- and automatic labels.  All of
this is feasible with a single syntax, so we don't have to pull our
hair out over unintended consequences.)

In the case of git links, we can add as many new git features as we
want without breaking anything.  The syntax can follow git's syntax
without having to figure out how to translate it or delimit it or work
out special cases.

I have more notes on this but cannot supply them now.

Some previous posts:

  http://www.mail-archive.com/emacs-orgmode@gnu.org/msg28464.html
  http://thread.gmane.org/gmane.emacs.orgmode/11896
  http://thread.gmane.org/gmane.emacs.orgmode/10204/focus=10240

Perhaps this is something to consider.

Samuel

-- 
The Kafka Pandemic:
http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forces_9182.html
I support the Whittemore-Peterson Institute (WPI)
===
I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MLV paper.

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] org-git-link does not support locational information within file

[Samuel Wales]

For a concise and relevant post:
http://www.mail-archive.com/emacs-orgmode@gnu.org/msg28464.html

-- 
The Kafka Pandemic:
http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forces_9182.html
I support the Whittemore-Peterson Institute (WPI)
===
I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MLV paper.

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] [ANN] OpenDocumentText/OpenOffice Exporter - 0.6 Release

[Gary Oberbrunner]

I just joined the list recently and am very excited to try direct odt
export!  I checked out Jambunathan's git repo.  I'm already running org-mode
from its git master; is your repo a fork of the master, or is it its own
thing?  It seems like it contains everything, so I should use it instead of
the main one?

Once I enabled png images in my Windows emacs (by copying the appropriate
DLLs), the following worked fine for me in my .emacs:

#+begin_example
;; Org-mode ODT (Open Document) export, EXPERIMENTAL:
(custom-set-variables
 '(org-export-latex-default-packages-alist (quote (("AUTO" "inputenc" t
 '(org-export-with-LaTeX-fragments (quote dvipng))
 )
(setq org-odt-base-dir "c:/Program Files (x86)/emacs/site-lisp/org-jambu") ;
only used for odt export
(load-file (expand-file-name "contrib/odt/setup.el" org-odt-base-dir))
#+end_example

I think this causes the jambu repo to be used for everything (org-mode.el
and all the other exports).  Is that OK?

I have to say, great work so far!  Amazingly useful.

I suppose one addition would be to allow for customized ODT character and
paragraph styles, e.g. customizing the styles.xml that gets included into
the doc.

-- 
-- Gary
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: Timestamp display behavior in timeline view

[Sébastien Vauban]

Hi Bastien,

Bastien wrote:
> You used this:
>
> * TODO <2010-12-25 Sat 14:40>-<2010-12-25 Sat 14:50> range with todo
>
> which looks weird.
>
> Better to put the timestamp/range on the next line:
>
> * TODO range with todo
>   <2010-12-25 Sat 14:40>-<2010-12-25 Sat 14:50>
>
> You won't get the surprising results you see.

Isn't it -- (two dashes) for the range purpose?

Best regards,
  Seb

-- 
Sébastien Vauban


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: Timestamp display behavior in timeline view

[Bernt Hansen]

Bastien  writes:

> Hi Alex,
>
> Alex Huang  writes:
>
>> 3. current behavior:
>>   ( + is unsurprising, ! is surprising, ? is not sure whether to be
>> surprised)
>>   + entries without time information not displayed
>>   + timestamps without text not displayed
>>   ! entries with timestamps display the text, but not the timestamp
>
> You used this:
>
> * TODO <2010-12-25 Sat 14:40>-<2010-12-25 Sat 14:50> range with todo
>
> which looks weird.
>
> Better to put the timestamp/range on the next line:
>
> * TODO range with todo
>   <2010-12-25 Sat 14:40>-<2010-12-25 Sat 14:50>

Shouldn't these timestamps have two dashes between them?
   <2010-12-25 Sat 14:40>--<2010-12-25 Sat 14:50>
or
   <2010-12-25 Sat 14:40-14:50>

?

-Bernt

>
> You won't get the surprising results you see.
>
> HTH,

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] More entries able to export to icalendar format

[Niels Giesen]

Hi Bastien,

> Can you submit your changes in the form of a patch, precisely describing
> your changes?  This way I can more easily try to understand/test them.

I will do so. What is the preferred way to do so: attaching those patches or 
quoting them
in-line?

Niels
-- 
http://pft.github.com/

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: Timestamp display behavior in timeline view

[Bastien]

Hi Bernt,

Bernt Hansen  writes:

>> * TODO range with todo
>>   <2010-12-25 Sat 14:40>-<2010-12-25 Sat 14:50>
>
> Shouldn't these timestamps have two dashes between them?
><2010-12-25 Sat 14:40>--<2010-12-25 Sat 14:50>
> or
><2010-12-25 Sat 14:40-14:50>

The manual advertize two dashes but both work fine here.

I'm myself using two dashes, I just copied the example of 
the OP too hastly.

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Accessing CATEGORY for custom agenda command

[Markus Heller]

Hi all,

I'm trying to get the following to work:

(org-add-agenda-custom-command
 '("X" tags "Task"
   ((org-agenda-skip-function '(org-agenda-skip-entry-if 
'notregexp "Admin"))
(org-agenda-overriding-header "  Test"


I want all entries that have the tag "TASK" and that have the category
"Admin" shown in the agenda.

I set the category in my org files like this:

#+CATEGORY: Admin
#+FILETAGS: ADMIN
* Tasks [5/6]  :TASK:
** TODO Drop off Stuff
** DONE F'up on other stuff

I also tried using 'notregexp "ADMIN" to go after the FILETAG, but
either way, the search yields no hits.

I have the feeling that I'm misunderstanding something pretty badly and
would appreciate any help :-)

Thanks and Cheers
Markus


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Accessing CATEGORY for custom agenda command

[Bastien]

Hi Markus,

Markus Heller  writes:

> I'm trying to get the following to work:
>
> (org-add-agenda-custom-command
>  '("X" tags "Task"
>((org-agenda-skip-function '(org-agenda-skip-entry-if 
>   'notregexp "Admin"))
> (org-agenda-overriding-header "  Test"
>
>
> I want all entries that have the tag "TASK" and that have the category
> "Admin" shown in the agenda.
>
> I set the category in my org files like this:
>
> #+CATEGORY: Admin
> #+FILETAGS: ADMIN
> * Tasks [5/6]:TASK:
> ** TODO Drop off Stuff
> ** DONE F'up on other stuff

Two problems:

- the tag is "TASK" and your custom agenda command looks for "Task":
  beware of the case

- '(org-agenda-skip-entry-if 'notregexp "Admin") is looking for an
  actual occurrence of the string "Admin" in the subtree -- and there 
  is no such occurrence in your .org example.

I suggest you use the CATEGORY property like this:

,
| #+FILETAGS: ADMIN
| 
| * Tasks [5/6] 
:Task:
|   :PROPERTIES:
|   :CATEGORY: Admin
|   :END:
|   
| ** TODO Drop off Stuff
| ** DONE F'up on other stuff
`

With this file, your agenda custom command works.

> I also tried using 'notregexp "ADMIN" to go after the FILETAG, but
> either way, the search yields no hits.

No, 'notregexp will go after actual text in the subtree, not inherited
properties.  If you look for properties, try org-entry-get instead in a 
org-agenda-skip-function instead.

> I have the feeling that I'm misunderstanding something pretty badly and
> would appreciate any help :-)

Hope you feel better :)

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] More entries able to export to icalendar format

[Bastien]

Hi Niels,

Niels Giesen  writes:

> Hi Bastien,
>
>> Can you submit your changes in the form of a patch, precisely describing
>> your changes?  This way I can more easily try to understand/test them.
>
> I will do so. 

Thanks!

> What is the preferred way to do so: attaching those patches or quoting
> them in-line?

Both attaching and quoting patches should be fine.

Please read this:
  http://orgmode.org/worg/org-contribute.html#sec-3

The best way to make a patch is to work on a separate branch, to make
one or several commit(s) then to create patches from this branch with

  ~$ git format-patch master

This way we have the proper ChangeLog etc.  The more explanations we
have on what the patch does, the better.

Best,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re-map global key while in the agenda?

[Bastien]

Hi Nathan,

Nathan Neff  writes:

> I have  i mapped to 'org-clock-in and I would also like  i to
> clock in while I'm in the agenda.

How is that useful outside an org-mode buffer?

> Is it possible to redefine a global key mapping in the agenda?

No.  Better to define your key in org-mode-map and org-agenda-mode-map,
no need for a global key IMHO.

HTH,

-- 
 Bastien

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] [OT] Taskwarrior, nice GTD-oriented CLI thing

[Marcelo de Moraes Serpa]

That's a nice idea. Integration would be cool, besides, a
taskwarrior2org (to sync back to the original org files) would be
useful. Since CLI is a simpler interface, it could be used from
anywhere where ssh is available... smartphones, for example; although
we already have mobile-org. Food for thought.

Cheers,

Marcelo.

On Fri, Feb 11, 2011 at 5:14 AM, Bastien  wrote:
> Marcelo de Moraes Serpa  writes:
>
>> Bastien, Carnsten, what do you guys think of Taskwarrior? :)
>
> I think it's pretty neat and that creating an org2taskwarrior export
> should be easy so that we can benefit of the nice taskwarrior graphs.
>
> --
>  Bastien
>

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Extending paste to auto-archive a copied image

[Marcelo de Moraes Serpa]

Hi Bastien,

Let's say I copy a file from my desktop. If I copy it (C-c) and then
yank into emacs, the filename is pasted.

Now, if I drag and drop it into an emacs buffer, emacs inserts the
contents of the file.

These two scenarios sum up something I think would be an awesome
addition to org, if only we could handle them differently.

For example, when taking notes in org, I often have different
reference sources open (web pages, word documents, pdfs etc), and
would like to insert images. I can already do that manually, and emacs
will even render them. But it takes too much time, and gets me out of
my productive zone.

What I am suggesting is, somehow hook into the moment the file is
pasted/dragged and run some code. This code would get a reference to
the file/contents of the file, save it in a org data directory and
return a URL to it, which would then be pasted in the document like a
regular link, and then iimage-mode would come into action and render
it.

Thanks,

Marcelo.

On Fri, Feb 11, 2011 at 5:50 AM, Bastien  wrote:
> Hi Marcelo,
>
> Marcelo de Moraes Serpa  writes:
>
>> So, I'm usign an emacs extension that renders links to image as the
>> image itself, it's a minor mode called iimage.el. It works great, but
>> the fact that I need to copy the image somewhere first is a time and
>> flow - killer. Is it possible to hook up to the paste command and, if
>> it's a image in the clipboard, auto-archive somewhere in the
>> filesystem it and then return its URL?
>
> Sorry I don't understand.  Can you give an example?  When you say
> "paste", is it pasting from X or from Emacs?
>
> Thanks,
>
> --
>  Bastien
>

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: Announcing org-contacts, a bbdb-like contact manager for Org

[Tassilo Horn]

Stefan Monnier  writes:

Hi Stefan,

>> So the question is: how can the completion-ignore-case value be
>> propagated from the completion gathering function in
>> `completion-at-point-functions' to the function that actually applies
>> this completion, without having to modify the global or buffer local
>> value of `completion-ignore-case'?
>
> Assuming you have a completion table in variable `table', you should
> be able to construct a new completion table that's case-insensitive
> with something like the untested code below:
>
> (defun completion-table-case-fold (table string pred action)
>   (let ((completion-ignore-case t))
> (complete-with-action action table string pred)))
>
> [...]
>(let ((newtable
>   (apply-partially #'completion-table-case-fold table)))
>  [...])
>
> where completion-table-case-fold is an auxiliary function which
> (c|sh)ould be added to minibuffer.el.

Hm, why not simply add a property :ignore-case to the PROPS a function
in `completion-at-point-functions' may return in addition to the
existing :predicate and :annotation-function?  Then
`completion-at-point' could simply bind `completion-ignore-case'
according to that property when calling `completion-in-region'.

Bye,
Tassilo

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] automatic regression test (again)

[Michael Brand]

Hi Eric

On Fri, Feb 11, 2011 at 16:09, Eric Schulte  wrote:
> These previous discussion resulted in the creation of a unit test suite
> for Org-mode.  Look in the testing, specifically at
>
> testing/README.org
> testing/org-test.el
>
> Any contributions to the test suite would be most appreciated!

Thank you for the hint, I will look into this later.

Michael

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Bug: startup hidestars also hides the point (square at point) [6.33x]

[Arne Babenhauserheide]

On Thursday 10 February 2011 16:50:43 Bastien wrote:
> Arne Babenhauserheide  writes:
> > Is it possible to disable the blinking statically and set the point to
> > visible?
> 
> Sorry I don't know...

No problem. Thank you for caring! 

Best wishes, 
Arne


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] [CRASH] org-pretty-entities causes emacs to take 100% CPU

[Eric Schulte]

Vladimir Alexiev  writes:

> 1. Evaluate this:
> (setq org-entities-user  ; name latex math-p html ascii latin1 utf8
>   '(("ok" nil nil "ચ" "OK" "OK" "✔")
> ("nok" nil nil "ઞ" "NOK" "NOK" "✘")))
> (setq org-pretty-entities t); \ok -> ✔ in buffer
>
> 2. Put this in an org buffer
> - \ok Deploy on x
> - \nok Deploy on y
> - \nok Use a hosted version 
> It should display the UTF graphic chars above (checkmark and cross)
>
> 3. Step on the mark and move around
> - left/right: ok
> - up: gives error "Args out of range"
> - down: causes emacs to take 100% CPU, no response, have to kill it
> GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600) of 2010-11-10 on SHAN-PC
>
> Not 100% sure the above is reproducible (got tired of having to kill my 
> emacs),
> but if someone takes up debugging, I'll give more precise steps
>

I followed your recipe above, and could not reproduce the error you
describe.  As a side note, I would suggest changing the
org-entities-user value to the following for correct html rendering (at
least using my browser -- chrome)

(setq org-entities-user  ; name latex math-p html ascii latin1 utf8
  '(("ok" nil nil "✔" "OK" "OK" "✔")
("nok" nil nil "✘" "NOK" "NOK" "✘")))

Best -- Eric

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: Announcing org-contacts, a bbdb-like contact manager for Org

[Stefan Monnier]

>>> So the question is: how can the completion-ignore-case value be
>>> propagated from the completion gathering function in
>>> `completion-at-point-functions' to the function that actually applies
>>> this completion, without having to modify the global or buffer local
>>> value of `completion-ignore-case'?
>> 
>> Assuming you have a completion table in variable `table', you should
>> be able to construct a new completion table that's case-insensitive
>> with something like the untested code below:
>> 
>> (defun completion-table-case-fold (table string pred action)
>> (let ((completion-ignore-case t))
>> (complete-with-action action table string pred)))
>> 
>> [...]
>> (let ((newtable
>> (apply-partially #'completion-table-case-fold table)))
>> [...])
>> 
>> where completion-table-case-fold is an auxiliary function which
>> (c|sh)ould be added to minibuffer.el.

> Hm, why not simply add a property :ignore-case to the PROPS a function
> in `completion-at-point-functions' may return in addition to the
> existing :predicate and :annotation-function?  Then
> `completion-at-point' could simply bind `completion-ignore-case'
> according to that property when calling `completion-in-region'.

That could work as well, but it's more complexity in
completion-at-point, compared to completion-table-case-fold which can be
added without touching any existing code.

Another reason why doing it inside the completion table is right is
because of the comment I quoted: in your case, it is really a property
of the completion table you return, rather than some user preference
that's locally overridden.

For more complex cases, there is also the issue of what to do when some
parts of the completion are case-sensitive and other parts aren't
(e.g. completion of case-sensitive envvars in case-insensitive file
names), although this is less important for  completion-at-point than
for minibuffer completion since you don't have to return a table that
covers the completion of the whole field (composed of file names and
env-vars, for example), and instead you can just limit the completion to
the particular subfield.


Stefan

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: Accessing CATEGORY for custom agenda command

[Markus Heller]

Bastien  writes:

> Hi Markus,
>
> Markus Heller  writes:
>
>> I'm trying to get the following to work:
>>
>> (org-add-agenda-custom-command
>>  '("X" tags "Task"
>>((org-agenda-skip-function '(org-agenda-skip-entry-if 
>>  'notregexp "Admin"))
>> (org-agenda-overriding-header "  Test"
>>
>>
>> I want all entries that have the tag "TASK" and that have the category
>> "Admin" shown in the agenda.
>>
>> I set the category in my org files like this:
>>
>> #+CATEGORY: Admin
>> #+FILETAGS: ADMIN
>> * Tasks [5/6]   
>> :TASK:
>> ** TODO Drop off Stuff
>> ** DONE F'up on other stuff
>
> Two problems:
>
> - the tag is "TASK" and your custom agenda command looks for "Task":
>   beware of the case
>
> - '(org-agenda-skip-entry-if 'notregexp "Admin") is looking for an
>   actual occurrence of the string "Admin" in the subtree -- and there 
>   is no such occurrence in your .org example.
>
> I suggest you use the CATEGORY property like this:
>
> ,
> | #+FILETAGS: ADMIN
> | 
> | * Tasks [5/6]   
> :Task:
> |   :PROPERTIES:
> |   :CATEGORY: Admin
> |   :END:
> |   
> | ** TODO Drop off Stuff
> | ** DONE F'up on other stuff
> `
>
> With this file, your agenda custom command works.
>
>> I also tried using 'notregexp "ADMIN" to go after the FILETAG, but
>> either way, the search yields no hits.
>
> No, 'notregexp will go after actual text in the subtree, not inherited
> properties.  If you look for properties, try org-entry-get instead in a 
> org-agenda-skip-function instead.
>
>> I have the feeling that I'm misunderstanding something pretty badly and
>> would appreciate any help :-)
>
> Hope you feel better :)

Hi Bastien,

thanks for you reply.  Yup, makes me feel better, because I think I'm
beginning to understand how to use properties more effectively.

Cheers
Markus


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: Re-map global key while in the agenda?

[Bernt Hansen]

Bastien  writes:

> Hi Nathan,
>
> Nathan Neff  writes:
>
>> I have  i mapped to 'org-clock-in and I would also like  i to
>> clock in while I'm in the agenda.
>
> How is that useful outside an org-mode buffer?

It's useful with a C-u prefix to pick another task off the recently
clocked items menu. I use this in non-org-mode buffers.  I agree that
without the prefix it's not useful outside of org-mode.

-Bernt

>
>> Is it possible to redefine a global key mapping in the agenda?
>
> No.  Better to define your key in org-mode-map and org-agenda-mode-map,
> no need for a global key IMHO.
>
> HTH,

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] c-c c-e 1 a crashes

[Samuel Wales]

Thanks, Bastien.

-- 
The Kafka Pandemic:
http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forces_9182.html
I support the Whittemore-Peterson Institute (WPI)
===
I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MLV paper.

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] [ANN] Changes to lists

[Samuel Wales]

Hi Nicolas,

I tried c-c - on

  - indented text and it worked perfectly, preserving hierarchy
  - headlines and it did not preserve hierarchy

I tried c-c * on

  - indented text and it did not preserve hierarchy
  - a list and it did not preserve hierarchy

Latest git.

Samuel

On 2011-02-10, Nicolas Goaziou  wrote:
> Hello,
>
>> Samuel Wales writes:
>
>> I'd like to see c-c - on headlines preserve hierarchy.
>
> This is now implemented, and hopefully working.
>
> Thanks for suggesting this,
>
> Regards,
>
> --
> Nicolas
>


-- 
The Kafka Pandemic:
http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forces_9182.html
I support the Whittemore-Peterson Institute (WPI)
===
I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MLV paper.

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] org+emacs vs CLI

[Marcelo de Moraes Serpa]

Hi list,

Being a geek that I am, I ended up ditching Things.app in favor of
org. However, being a geek also means being bombarded by other tools
like Taskwarrior. Taskwarrior is great, but I don't think it can beat
the speed of org + emacs, considering of course, you are already a
seasoned emacs and org user.

I do think CLI clients for org would be nice, as discussed in the
taskwarrior thread, but really, IMO, emacs+org will always be faster
to input and query org data.

What do you think?

Cheers,

Marcelo.

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] org-stow (Proof of concept)

[brian powell]

You asked to hear from interested OrgMode users:

STOW is great software; yes, please push it--its great for testing and
sofware configuration (STOW is) it will be very interesting and maybe very
useful to see what you have in mind.

STOW reminds me of AUFS/UNIONFS and there may be other uses for people like
myself; people that are interested in using OrgMode in non-traditional ways:
You could use it in a real-time brainstorming group meeting---back-in and
back-out of one version of a plan/agenda.  Maybe you could make "contingency
plans" or "Plan B's" or "Plan 9 From Outer Space" agendas!

Recently I stumbled on "NIX" which supports the config. of several software
versions of different and concurrent packaging systems like APT and RPM
co-existing in harmony.  Ideas, agendas and notes in OrgMode can be seen the
same way maybe.   GNU STOW was interesting for similar reasons.  NIX can
help you escape from "library or version conflict hell"--ideas and notes in
OrgMode are like ideas that may be  good; but, you may want to put them on
the back-burner or "org-stow" them away.
http://savannah.gnu.org/projects/stow (I believe this is what you are
refering to) claims "Stow is a package manager for people who don't use
package managers"--NIX and other meta-packaging systems are trying to
sidestep package management problems--regardless of the (usual) software
conflict problems.

One may use something like an "org-stow" to write a plan/story/script (in
outline OrgMode form) with many different versions for example.

There are org-drawers remember: http://orgmode.org/manual/Drawers.html

---can you org-stow things in org-drawers? like org-socks?

enough comedy; seriously though, yes please, I'm interested.


On Fri, Feb 11, 2011 at 8:37 AM, Bastien wrote:

> "Tom Breton (Tehom)"  writes:
>
> > Any interest in trying this out?  I can push it if anyone else wants to
> > try it out.
>
> I'm interested!  Please let me know where I can read some code.
>
> Thanks :)
>
> --
>  Bastien
>
> ___
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] OT: medical practice software with all functions including machine learning

[Samuel Wales]

This is totally OT, but I thought some of you would have ideas.  You
share my software sensibilities.

I know a person who is creating a nonprofit, large, extremely
important translational medicine clinic. This means that the clinic
will be tightly integrated with basic and clinical research.

One thing that is needed is good software.  Perhaps some of you know
of the open source options here.  EVERYTHING is needed: scanning,
billing, grepping, reports, machine learning, etc.  Preferably all
integrated for nontechnical but very intelligent people.

Effectiveness of treatments will be fed back into research.  Research
will be fed back into treatments and the most promising cases will
need to be found.  Keeping track of scanned medical records, data
about people, histories taken, results of treatments, etc. is
necessary.

It is a large challenge for software.  I am asking on the chance that
some of you knows something that can help (or, perhaps even, can help
set something up).

This is an open-ended question.

Thanks.

Samuel

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode