Re: [O] Small patch for pw client, fix typo in error message

[Bastien]

Hi David,

David Maus  writes:

> Not sure what the commit policy for the pw client in UTITLITES is, so
> this patch first over the list: It fixes a confusing typo in an error
> message.

Applied, thanks.

-- 
 Bastien

Re: [O] [DEV] New git workflow

[Achim Gratz]

Bastien  writes:
> The main problem I see With this workflow is that releases are made
> from two different branches: bugfix releases are made from maint and
> major releases are made from master.  This doesn't look right to me.

That ain't necessarily so.  IMHO, the release always has to be done from
maint (that's the whole purpose of it), preceded by a merge from master
if and only if a major release is done.

> So I suggest to use three branches with these rules:
>
> - master: the main persistent branch.  This is were regular development
>   goes.  This branch is merged back to the maint branch when we release
>   a new major version.  No release happens directly from this branch.
>
> - maint: the "production" persistent branch.  This branch is dedicated
>   to the release process: when hot fixes are hot enough, we merge the
>   hotfix branch to the maint branch and release a bugfix release.  When
>   the master branch (where hot fixes are also merged to) is mature and
>   well tested, we merge master into maint and release a major version.

So far no deviation from today.

> - hotfix-7.XX.XX: the transient branch for hotfixes.  Severe bugs are
>   fixed there first, then merged back to maint when this makes sense.
>   The branch is created when we need it and deleted when we don't need
>   it anymore.

You would have to push this branch out to the public repo, otherwise the
other people with access to the repo can't use it.  For instance,
Carsten has already committed to maint again, because he can't see your
bugfix branch.  All things considered, the hotfix branch and maint
should almost always point to the same commit.  In other words, all
hotfix branches should merge into maint first and then maint back into
master.  The only advantage of version-specific hotfix branches I can
see is if you want to be able to fix bugs in several releases seperately
(e.g. 7.8.06 in Emacs 24.1, 7.x.yy in Emacs 24.2 etc.).  Also, the setup
would have to be slightly different in that case: branch the hotfix from
the release commit and then keep adding bugfixes and merging into maint.
That would require an enormous amount of coordination and discipline
from all maintainers and committers, as several branches would have to
keep merging into both maint and master.

> This workflow looks clearer to me.

I suggest you try this first in a disposable repo clone, if possible
together with all other commiters to the public repo.  It is a valid
setup and suppports some things that you can't do very well today, but
it makes things more complicated than the current workflow (which maybe
need to be spelled out more explicitly).

>  Here are the advantages I see:
>
> 1) *all releases happen on the same branch* (the maint branch): it is
>easier to keep this branch in sync with Emacs and we can also add
>git hooks to automate the release process.

See above, that was always how it was supposed to work.

> 2) the master branch *is* the development branch: yes, pretty unusual.

Not really unusual, there are more examples of this.

>At least as unusual as not having two mailing lists, one for users
>and one for devs.  But I want to stick to what makes this list a
>great place: regular users are invited to live on the bleeding edge
>and to contribute patches on the "development" branch, the one they
>will clone first.
>
> So, what's next?
>
> I will merge 7.8.06 into Emacs.
>
> Nothing should be committed to maint anymore before the next release.
>
> Important bug fixes for 7.8.06 all go to a new branch hotfix-7.8.06.
>
> Usual development goes to master, from where we regularily merge the
> hotfix branch.
>
> We'll get rid of the hotfix branch when releasing 7.8.07 or 7.9.

Once you've pushed it out to the repo you shouldn't delete it, even when
merged back into maint.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [O] how to specify table width in HTML export

[Michael Hannon]

> From: Nick Dokos 
>
> Stephen J. Barr  wrote:
>
>> Hello,
>>
>> This seems like a simple question but I can't seem to find the answer?
>> How do I specify the table width for an org-table that I will export
>> to HTML?
>>
>
> Not sure about the real HTMl syntax, or whether this is the best
> solution (I'd imagine CSS would be better *if* it can be done with CSS)
> but the following:
>
> #+ATTR_HTML: width="100"
> | col1 | col2 |
> |--+--|
> |    1 |    3 |
> |  |  |
>
> gets translated into an HTML table with an opening tag like this:
>
>  cellpadding="6" rules="groups" frame="hsides"
> width="100">
>
> Does that do the trick?

Indeed, I think CSS would be a better approach.  And of course I don't know
what this particular application is, but it's usually better to specify the
width of objects as a percentage of the overall width.

This is discussed, for instance, at:

    http://www.w3schools.com/css/css_table.asp

Here's a line from one of my old .org files that shows the syntax:

    #+STYLE:    

It's also possible to embed the styling information directly in the Org-mode
file, but I find that to be less convenient, as you then have to re-export to
make a change to the style.

Caveat: I haven't done any HTML exporting to speak of lately, certainly none
that has involved CSS, so it may be that the syntax has changed (i.e.,
compared to the above STYLE directive).

-- Mike

Re: [O] [DEV] New git workflow

[Achim Gratz]

Achim Gratz  writes:
> You would have to push this branch out to the public repo, otherwise the
> other people with access to the repo can't use it.

I see you already did, had to reconfigure my refspecs for it to show up.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

[O] hotfix-7.8.06 (org-ditaa-jar-path): Debugger entered--Lisp error: (error "Too many arguments"))

[Jambunathan K]

Debugger entered--Lisp error: (error "Too many arguments")
  (defvar org-ditaa-jar-path (expand-file-name "ditaa.jar" 
(file-name-as-directory (expand-file-name "scripts" (file-name-as-directory 
(expand-file-name "../contrib" (file-name-directory (find-library-name 
"org"))) "Path to the ditaa jar executable." :group (quote org-babel) :type 
(quote string))
  eval-buffer(#> nil "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-exp-blocks.el" 
nil t)  ; Reading at buffer position 8915
  load-with-code-conversion("c:/Documents and Settings/kjambunathan/My 
Documents/My Data/src/org-mode/lisp/org-exp-blocks.el" "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-exp-blocks.el" 
nil t)
  require(org-exp-blocks)
  eval-buffer(#> nil "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-exp.el" nil t) 
 ; Reading at buffer position 1133
  load-with-code-conversion("c:/Documents and Settings/kjambunathan/My 
Documents/My Data/src/org-mode/lisp/org-exp.el" "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-exp.el" nil t)
  require(org-exp)
  eval-buffer(#> nil "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-lparse.el" nil 
t)  ; Reading at buffer position 1906
  load-with-code-conversion("c:/Documents and Settings/kjambunathan/My 
Documents/My Data/src/org-mode/lisp/org-lparse.el" "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-lparse.el" nil 
t)
  require(org-lparse)
  eval-buffer(#> nil "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-odt.el" nil t) 
 ; Reading at buffer position 1012
  load-with-code-conversion("c:/Documents and Settings/kjambunathan/My 
Documents/My Data/src/org-mode/lisp/org-odt.el" "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-odt.el" nil 
nil)
  load("org-odt")
  load-library("org-odt")
  call-interactively(load-library t nil)
  execute-extended-command(nil)
  call-interactively(execute-extended-command nil nil)
  recursive-edit()
  debug(error (error "Too many arguments"))
  (defvar org-ditaa-jar-path (expand-file-name "ditaa.jar" 
(file-name-as-directory (expand-file-name "scripts" (file-name-as-directory 
(expand-file-name "../contrib" (file-name-directory (find-library-name 
"org"))) "Path to the ditaa jar executable." :group (quote org-babel) :type 
(quote string))
  eval-region(8566 8915 t (lambda (ignore) (goto-char 8915) (quote (defvar 
org-ditaa-jar-path (expand-file-name "ditaa.jar" (file-name-as-directory 
(expand-file-name "scripts" (file-name-as-directory (expand-file-name 
"../contrib" ...) "Path to the ditaa jar executable." :group (quote 
org-babel) :type (quote string)  ; Reading at buffer position 8915
  apply(eval-region (8566 8915 t (lambda (ignore) (goto-char 8915) (quote 
(defvar org-ditaa-jar-path (expand-file-name "ditaa.jar" 
(file-name-as-directory (expand-file-name "scripts" (file-name-as-directory 
... "Path to the ditaa jar executable." :group (quote org-babel) :type 
(quote string))
  eval-defun-2()
  eval-defun(nil)
  call-interactively(eval-defun nil nil)
  recursive-edit()
  debug(error (error "Too many arguments"))
  (defvar org-ditaa-jar-path (expand-file-name "ditaa.jar" 
(file-name-as-directory (expand-file-name "scripts" (file-name-as-directory 
(expand-file-name "../contrib" (file-name-directory (find-library-name 
"org"))) "Path to the ditaa jar executable." :group (quote org-babel) :type 
(quote string))
  eval-buffer(#> nil "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-exp-blocks.el" 
nil t)  ; Reading at buffer position 8915
  load-with-code-conversion("c:/Documents and Settings/kjambunathan/My 
Documents/My Data/src/org-mode/lisp/org-exp-blocks.el" "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-exp-blocks.el" 
nil t)
  require(org-exp-blocks)
  eval-buffer(#> nil "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-exp.el" nil t) 
 ; Reading at buffer position 1133
  load-with-code-conversion("c:/Documents and Settings/kjambunathan/My 
Documents/My Data/src/org-mode/lisp/org-exp.el" "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-exp.el" nil t)
  require(org-exp)
  eval-buffer(#> nil "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-lparse.el" nil 
t)  ; Reading at buffer position 1906
  load-with-code-conversion("c:/Documents and Settings/kjambunathan/My 
Documents/My Data/src/org-mode/lisp/org-lparse.el" "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-lparse.el" nil 
t)
  require(org-lparse)
  eval-buffer(# nil "c:/Documents and Settings/kjambunathan/My 
Documents/My Data/src/org-mode/lisp/org-odt.el" nil t)  ; Reading at buffer 
position 

Re: [O] hotfix-7.8.06 (org-ditaa-jar-path): Debugger entered--Lisp error: (error "Too many arguments"))

[Jambunathan K]

Another crash related to this.  Please fix this as well.

Debugger entered--Lisp error: (void-function find-library-name)
  (find-library-name "org")
  (file-name-directory (find-library-name "org"))
  (expand-file-name "../contrib" (file-name-directory (find-library-name 
"org")))
  (file-name-as-directory (expand-file-name "../contrib" (file-name-directory 
(find-library-name "org"
  (expand-file-name "scripts" (file-name-as-directory (expand-file-name 
"../contrib" (file-name-directory (find-library-name "org")
  (file-name-as-directory (expand-file-name "scripts" (file-name-as-directory 
(expand-file-name "../contrib" (file-name-directory (find-library-name 
"org"))
  (expand-file-name "ditaa.jar" (file-name-as-directory (expand-file-name 
"scripts" (file-name-as-directory (expand-file-name "../contrib" 
(file-name-directory (find-library-name "org")))
  (defvar org-ditaa-jar-path (expand-file-name "ditaa.jar" 
(file-name-as-directory (expand-file-name "scripts" (file-name-as-directory 
(expand-file-name "../contrib" (file-name-directory (find-library-name 
"org"))) "Path to the ditaa jar executable.")
  eval-buffer(#> nil "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-exp-blocks.el" 
nil t)  ; Reading at buffer position 8879
  load-with-code-conversion("c:/Documents and Settings/kjambunathan/My 
Documents/My Data/src/org-mode/lisp/org-exp-blocks.el" "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-exp-blocks.el" 
nil t)
  require(org-exp-blocks)
  eval-buffer(#> nil "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-exp.el" nil t) 
 ; Reading at buffer position 1133
  load-with-code-conversion("c:/Documents and Settings/kjambunathan/My 
Documents/My Data/src/org-mode/lisp/org-exp.el" "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-exp.el" nil t)
  require(org-exp)
  eval-buffer(#> nil "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-lparse.el" nil 
t)  ; Reading at buffer position 1906
  load-with-code-conversion("c:/Documents and Settings/kjambunathan/My 
Documents/My Data/src/org-mode/lisp/org-lparse.el" "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-lparse.el" nil 
t)
  require(org-lparse)
  eval-buffer(# nil "c:/Documents and Settings/kjambunathan/My 
Documents/My Data/src/org-mode/lisp/org-odt.el" nil t)  ; Reading at buffer 
position 1012
  load-with-code-conversion("c:/Documents and Settings/kjambunathan/My 
Documents/My Data/src/org-mode/lisp/org-odt.el" "c:/Documents and 
Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-odt.el" nil 
nil)
  load("org-odt")
  load-library("org-odt")
  call-interactively(load-library t nil)
  execute-extended-command(nil)
  call-interactively(execute-extended-command nil nil)

[O] Multiple :LOGBOOK: blocks "allowed" without unwanted side effects?

[Rainer Stengele]

Hi all,

I want to be sure that multiple :LOBGOOK: blocks in sequence are making no 
trouble.


As an example I have this:

* NEXT A task
  :LOGBOOK:
  CLOCK: [2012-03-19 Mo 16:45]--[2012-03-19 Mo 17:00] =>  0:15
  CLOCK: [2012-03-12 Mo 14:15]--[2012-03-12 Mo 14:30] =>  0:15
  CLOCK: [2012-03-07 Mi 11:15]--[2012-03-07 Mi 11:30] =>  0:15
  CLOCK: [2012-02-24 Fr 16:30]--[2012-02-24 Fr 16:45] =>  0:15
  CLOCK: [2012-02-14 Di 13:15]--[2012-02-14 Di 13:30] =>  0:15
  CLOCK: [2012-02-03 Fr 09:15]--[2012-02-03 Fr 09:30] =>  0:15
  CLOCK: [2012-02-01 Mi 12:00]--[2012-02-01 Mi 12:15] =>  0:15
  CLOCK: [2012-01-30 Mo 16:45]--[2012-01-30 Mo 17:00] =>  0:15
  CLOCK: [2012-01-30 Mo 09:30]--[2012-01-30 Mo 09:45] =>  0:15
  CLOCK: [2012-01-25 Mi 14:45]--[2012-01-25 Mi 15:00] =>  0:15
  CLOCK: [2012-01-13 Fr 17:00]--[2012-01-13 Fr 17:15] =>  0:15
  CLOCK: [2011-12-19 Mo 16:45]--[2011-12-19 Mo 17:00] =>  0:15
  CLOCK: [2011-12-02 Fr 11:45]--[2011-12-02 Fr 12:00] =>  0:15
  CLOCK: [2011-11-17 Do 10:15]--[2011-11-17 Do 10:30] =>  0:15
  CLOCK: [2011-11-10 Do 08:45]--[2011-11-10 Do 09:00] =>  0:15
  CLOCK: [2011-11-08 Di 09:45]--[2011-11-08 Di 10:15] =>  0:30
  CLOCK: [2011-10-25 Di 09:45]--[2011-10-25 Di 10:00] =>  0:15
  CLOCK: [2011-10-10 Mo 13:30]--[2011-10-10 Mo 14:00] =>  0:30
  CLOCK: [2011-10-04 Di 15:15]--[2011-10-04 Di 15:30] =>  0:15
  CLOCK: [2011-10-04 Di 08:30]--[2011-10-04 Di 09:00] =>  0:30
  CLOCK: [2011-09-23 Fr 10:30]--[2011-09-23 Fr 10:45] =>  0:15
  CLOCK: [2011-09-13 Di 10:45]--[2011-09-13 Di 11:15] =>  0:30
  CLOCK: [2011-08-30 Di 14:15]--[2011-08-30 Di 14:45] =>  0:30
  CLOCK: [2011-08-08 Mo 13:30]--[2011-08-08 Mo 14:00] =>  0:30
  CLOCK: [2011-07-08 Fr 23:00]--[2011-07-09 Sa 01:00] =>  2:00
  CLOCK: [2011-07-08 Fr 18:15]--[2011-07-08 Fr 18:45] =>  0:30
  CLOCK: [2011-07-08 Fr 17:15]--[2011-07-08 Fr 17:45] =>  0:30
  CLOCK: [2011-06-27 Mo 09:30]--[2011-06-27 Mo 09:45] =>  0:15
  CLOCK: [2011-05-25 Mi 09:00]--[2011-05-25 Mi 09:15] =>  0:15
  CLOCK: [2011-05-13 Fr 16:15]--[2011-05-13 Fr 16:30] =>  0:15
  CLOCK: [2011-04-11 Mo 08:30]--[2011-04-11 Mo 08:45] =>  0:15
  CLOCK: [2011-03-22 Di 14:00]--[2011-03-22 Di 14:15] =>  0:15
  CLOCK: [2011-02-23 Mi 13:00]--[2011-02-23 Mi 13:15] =>  0:15
  CLOCK: [2011-02-09 Mi 07:30]--[2011-02-09 Mi 08:00] =>  0:30
  CLOCK: [2011-01-26 Mi 09:30]--[2011-01-26 Mi 10:00] =>  0:30
  CLOCK: [2011-01-11 Di 13:30]--[2011-01-11 Di 13:45] =>  0:15
  CLOCK: [2010-12-02 Do 10:00]--[2010-12-02 Do 10:45] =>  0:45
  CLOCK: [2010-11-25 Do 08:30]--[2010-11-25 Do 09:30] =>  1:00
  CLOCK: [2010-10-14 Do 08:30]--[2010-10-14 Do 08:45] =>  0:15
  CLOCK: [2010-09-27 Mo 08:00]--[2010-09-27 Mo 08:15] =>  0:15
  CLOCK: [2010-09-21 Di 16:30]--[2010-09-21 Di 16:45] =>  0:15
  CLOCK: [2010-09-13 Mo 08:30]--[2010-09-13 Mo 08:45] =>  0:15
  CLOCK: [2010-08-10 Di 09:30]--[2010-08-10 Di 09:45] =>  0:15
  CLOCK: [2010-08-04 Mi 08:00]--[2010-08-04 Mi 08:15] =>  0:15
  CLOCK: [2010-08-03 Di 09:45]--[2010-08-03 Di 10:00] =>  0:15
  CLOCK: [2010-06-29 Di 11:30]--[2010-06-29 Di 12:00] =>  0:30
  CLOCK: [2010-06-11 Fr 16:30]--[2010-06-11 Fr 16:55] =>  0:25
  CLOCK: [2010-06-01 Di 09:05]--[2010-06-01 Di 09:12] =>  0:07
  CLOCK: [2010-05-31 Mo 10:40]--[2010-05-31 Mo 10:50] =>  0:10
  CLOCK: [2010-04-16 Fr 12:45]--[2010-04-16 Fr 13:06] =>  0:21
  CLOCK: [2010-03-12 Fr 09:13]--[2010-03-12 Fr 09:19] =>  0:06
  CLOCK: [2010-03-12 Fr 08:55]--[2010-03-12 Fr 09:11] =>  0:16
  :END:


Most times I manually have to adjust the latest CLOCK entry.
In order to do this I have to open the :LOGBOOK: drawer, which fills my screen 
with all the old entries,
Therefore I cannot see the contents belonging to the headline.

Is it ok to put let's say all entries older than 2012 in a separate :LOBGOOK 
block and all the 2012 entries
in another block:

  :LOGBOOK:
  CLOCK: [2012-03-19 Mo 16:45]--[2012-03-19 Mo 17:00] =>  0:15
  CLOCK: [2012-03-12 Mo 14:15]--[2012-03-12 Mo 14:30] =>  0:15
  CLOCK: [2012-03-07 Mi 11:15]--[2012-03-07 Mi 11:30] =>  0:15
  CLOCK: [2012-02-24 Fr 16:30]--[2012-02-24 Fr 16:45] =>  0:15
  CLOCK: [2012-02-14 Di 13:15]--[2012-02-14 Di 13:30] =>  0:15
  CLOCK: [2012-02-03 Fr 09:15]--[2012-02-03 Fr 09:30] =>  0:15
  CLOCK: [2012-02-01 Mi 12:00]--[2012-02-01 Mi 12:15] =>  0:15
  CLOCK: [2012-01-30 Mo 16:45]--[2012-01-30 Mo 17:00] =>  0:15
  CLOCK: [2012-01-30 Mo 09:30]--[2012-01-30 Mo 09:45] =>  0:15
  CLOCK: [2012-01-25 Mi 14:45]--[2012-01-25 Mi 15:00] =>  0:15
  CLOCK: [2012-01-13 Fr 17:00]--[2012-01-13 Fr 17:15] =>  0:15
  :END:
  :LOGBOOK:
  CLOCK: [2011-12-19 Mo 16:45]--[2011-12-19 Mo 17:00] =>  0:15
  CLOCK: [2011-12-02 Fr 11:45]--[2011-12-02 Fr 12:00] =>  0:15
  CLOCK: [2011-11-17 Do 10:15]--[2011-11-17 Do 10:30] =>  0:15
  

Re: [O] Multiple :LOGBOOK: blocks "allowed" without unwanted side effects?

[Achim Gratz]

Rainer Stengele  online.de> writes:
> I want to be sure that multiple :LOBGOOK: blocks in sequence are making no
trouble.

I don't know about having multiple LOGBOOK drawers, that feels dirty...  What I
do is having a CLOSED drawer defined, putting it directly behind the LOGBOOK
drawer and then just shift the boundary between the two (the two lines
:END:\n:CLOSED:\n) whenever I feel like it (at the end of the week, mainly).

:LOGBOOK:
...whatever
:END:
:CLOSED:
...whatever else
:END:

Achim.

Re: [O] hotfix-7.8.06 (org-ditaa-jar-path): Debugger entered--Lisp error: (error "Too many arguments"))

[Bastien]

Hi Jambunathan,

Jambunathan K  writes:

> Debugger entered--Lisp error: (error "Too many arguments")
>   (defvar org-ditaa-jar-path (expand-file-name "ditaa.jar"

Fixed, thanks!

-- 
 Bastien

Re: [O] hotfix-7.8.06 (org-ditaa-jar-path): Debugger entered--Lisp error: (error "Too many arguments"))

[Bastien]

Hi Jambunathan,

Jambunathan K  writes:

> Another crash related to this.  Please fix this as well.
>
> Debugger entered--Lisp error: (void-function find-library-name)

Fixed, thanks.

-- 
 Bastien

Re: [O] [DEV] New git workflow

[Bastien]

Hi Achim,

Achim Gratz  writes:

> Bastien  writes:
>> The main problem I see With this workflow is that releases are made
>> from two different branches: bugfix releases are made from maint and
>> major releases are made from master.  This doesn't look right to me.
>
> That ain't necessarily so.  IMHO, the release always has to be done from
> maint (that's the whole purpose of it), preceded by a merge from master
> if and only if a major release is done.

Agreed.  What I want on top of this is a to have a branch where *every*
commit corresponds to a single release.

>> - master: the main persistent branch.  This is were regular development
>>   goes.  This branch is merged back to the maint branch when we release
>>   a new major version.  No release happens directly from this branch.
>>
>> - maint: the "production" persistent branch.  This branch is dedicated
>>   to the release process: when hot fixes are hot enough, we merge the
>>   hotfix branch to the maint branch and release a bugfix release.  When
>>   the master branch (where hot fixes are also merged to) is mature and
>>   well tested, we merge master into maint and release a major version.
>
> So far no deviation from today.

There is one important deviation: so far we could commit changes to
maint and _not_ make a release.  From now on, every commit to maint
should correspond to a release.

> All things considered, the hotfix branch and maint
> should almost always point to the same commit.  In other words, all
> hotfix branches should merge into maint first and then maint back into
> master.  

No.  All hotfix branches should merge into master regularily.  When
hotfix contains enough fixes for a bugfix release, then we merge it to
maint, and process with release.

My main goal is this: have a branch with one commit = one release.

>>  Here are the advantages I see:
>>
>> 1) *all releases happen on the same branch* (the maint branch): it is
>>easier to keep this branch in sync with Emacs and we can also add
>>git hooks to automate the release process.
>
> See above, that was always how it was supposed to work.

Yes.  

-- 
 Bastien

Re: [O] [DEV] New git workflow

[Bastien]

Let me summarise why I propose this new workflow:

1. Users will have a way to track *only releases* from git.

2. We will be able to use git hooks in order to automate the
   release process on the server.

3. The workflow looks clearer to me (may be 100% subjective.)

The cost of the new setup is 0: instead of committing fixes
to maint, we commit them to hotfix-*.

-- 
 Bastien

Re: [O] [PATCH] imenu: Added a check that looking-at succeeds before using the match results.

[Bastien]

Hi Ilya,

Ilya Shlyakhter  writes:

> On 3/8/2012 2:39 PM, Achim Gratz wrote:
>> Your patch got completely mangled, try again as an attachment of type
>> (text/plain).
> here, also at http://ilya.cc/imenu.patch

Applied, thanks.

-- 
 Bastien

Re: [O] AUCTeX conflicting with org-mode

[Bastien]

Hi Yagnesh,

Yagnesh Raghava Yakkala  writes:

> Thanks for the analysis. I think you are right. With my limited elisp skills I
> would say its a *bug* and coming from org.
>
> If I take that let-binding off and setting the TeX-master by checking with
> if it ever bound seems fixing this problem.
>
> this patch fixing the problem. (can be further improved)

Applied, thanks.

-- 
 Bastien

Re: [O] [PATCH] Allow customization of date and time format

[Bastien]

Hi Sébastien,

"Sebastien Vauban"  writes:

>>From d4d2f7f32e659269c885a934a131c7aea1ec4798 Mon Sep 17 00:00:00 2001
> From: Sebastien Vauban 
> Date: Thu, 8 Mar 2012 11:04:00 +0100
> Subject: [PATCH] Allow customization of date and time format
>
> Allow customization of date and time format
>
>   * org-html.el (org-export-as-html): Use a variable format
>   string for export of date and time.

I applied a slightly different version, using a defcustom instead 
of a defvar.

Thanks for the patch!

-- 
 Bastien

Re: [O] [PATCH] doc/org.texi: add tiny stylistic improvements

[Bastien]

Applied, thanks.

-- 
 Bastien

Re: [O] [PATCH] doc/org.texi: remove duplicated keybinding for 'org-refile-cache-clear'

[Bastien]

Hi Julian,

Julian Gehring  writes:

>>From e56f7f204014ce6e2b83a75caeb248dd63a6c74f Mon Sep 17 00:00:00 2001
> From: Julian Gehring 
> Date: Sun, 26 Feb 2012 13:51:22 +0100
> Subject: [PATCH] doc/org.texi: remove duplicated keybinding for
>  'org-refile-cache-clear'

Applied, thanks.

-- 
 Bastien

[O] Referencing a cell from a clockview table looks impossible

[Sebastien Vauban]

Hello,

I need to access to the "Total time" cell of a clocktable view. I've named it
properly, but references to a given cell all return "#ERROR".

* Work

Some tasks with CLOCK lines, for showing the problem.

** TODO Do this
   :LOGBOOK:
   CLOCK: [2012-03-19 Mon 09:00]--[2012-03-19 Mon 10:11] =>  1:11
   :END:

** TODO Do that
   :LOGBOOK:
   CLOCK: [2012-03-20 Tue 10:00]--[2012-03-20 Tue 12:22] =>  2:22
   :END:

* Report

** Dynamic block

The dynamic block captures the fact that I've worked 1:11 hours yesterday, on
some task of this file.

#+TBLNAME: hours-yesterday
#+BEGIN: clocktable :maxlevel 4 :scope file :block yesterday
Clock summary at [2012-03-20 Tue 11:59], for Monday, March 19, 2012.

| Headline | Time |  |
|--+--+--|
| *Total time*   | *1:11* |  |
|--+--+--|
| Work | 1:11 |  |
| TODO Do this |  | 1:11 |
#+END:

** Table with remote reference

As I need the above time to be converted first to a float, then to money, I'm
using a remote reference to the above "Total Time", and a table which shows
the intermediate results:

| Tasks | HH:MM  | Float | USD|
|---++---+|
| Yesterday | #ERROR |  0.00 | #ERROR |
|---++---+|
|   ||0. | 0  |
#+TBLFM: $3='(/ (float (org-hh:mm-string-to-minutes $2)) 
60.);%.2f::$4=$2*30::@2$2=remote(hours-yesterday,@2$2)::@3$3=vsum(@-I..@-II)

But the remote reference fails with whichever referenced cell.

Any idea?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] PATCH: doc for column groups

[Bastien]

Hi Rustom,

Rustom Mody  writes:

> I spent some hours scratching my head trying to get tables out with
> vertical lines, until Jambunathan suggested that I try not to put
> space between the '<' and '>'
> The patch adds a few words to the org.texi file to that effect.
>
> WARNING: Ive never given a patch before! Nor used texi

I applied the patch, thanks!

To improve future patches:

- take care of not adding whitespaces (just run M-x
  delete-trailing-whitespace RET when you're done editing.)

- add a ChangeLog (go to your edits, type `C-x 4 a' to create a
  ChangeLog message for your edit, and add this as the commit 
  message.)

More detailed information on the website.

Thanks!

-- 
 Bastien

Re: [O] [patch] Add three "xelatex" config items to "org-latex-to-pdf-process"

[Bastien]

Hi FengShu,

FengShu  writes:

> Xelatex should be pdflatex with enhanced font handling capability.
> and its fonts configure for Chinese is  much much  more simple than 
> pdflatex, for it can use *ttf* *otf* fonts in the system easily.

Applied in master, thanks.

Please use git format-patch for future patches, it saves me a lot 
of time.

-- 
 Bastien

Re: [O] Timezone/Encoding issues when exporting as ics and importing to Google Calendar

[Bastien]

Hi Kevin,

Kevin Brubeck Unhammer  writes:

> I guess I'll have to upgrade my org-mode version (6.33x) to get
> org-icalendar-date-time-format?

Not sure this will fix your problem, but yes, 6.33x is kinda 
prehistoric now.

Best,

-- 
 Bastien

Re: [O] Bug: Bug reporting doesn't work [7.8.03 (release_7.8.03.583.gd7943.dirty)]

[Bastien]

Hi Shaun,

Shaun Johnson  writes:

> Attempting to send a bug report using org-submit-bug-report results in
> the following backtrace:

This should be fixed now, thanks.

-- 
 Bastien

Re: [O] [PATCH] Add "Time-stamp: <>" in (first 8 lines of) export template

[Bastien]

Hi Sébastien,

"Sebastien Vauban"  writes:

>>From 74f376c12cceae196f5a856eac1a39cdbcc8e360 Mon Sep 17 00:00:00 2001
> From: Sebastien Vauban 
> Date: Thu, 16 Feb 2012 15:48:37 +0100
> Subject: [PATCH] Add Time-stamp in export template
>
> ---
>  lisp/org-exp.el |1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)

I'm not applying this patch.

I see how it can be useful for those who use 

(add-hook 'before-save-hook 'time-stamp)

but #+Time-stamp is *not* an Org option... so unless we find 
a way to use it without confusing the user, I won't apply it.

If you have another proposal, please provide a commit message
with your patch!

Thanks,

-- 
 Bastien

Re: [O] [PATCH] Fixed compiler warnings including one small bug in ob-lilypond

[Bastien]

Achim Gratz  writes:

> Ilya Shlyakhter  writes:
>
>> +(require 'format-spec)
> [...]
>> +(declare-function format-spec "format-spec" (format specification))
>
> Only one of these two lines should be necessary?

That's right.  I removed the declare-function. 

Thanks,

-- 
 Bastien

Re: [O] [bug] org-agenda-write does not handle date stamps without day of week

[Karl Voit]

* Carsten Dominik  wrote:
> I have just pushed the new version of this regexp into master.

Very cool!

> Karl, let me know if it fixes the issues you where having
> with writing agendas.

My agenda looks fine. But generating the ics file still results in
events without the time information:

,[ my function generating the ics ]
| (defun vk-export-agenda()
|   "Exports monthly Org-mode agenda to agenda.ics file"
|   (interactive)
|   (org-agenda-list nil nil 60)
|   (org-agenda-write "~/share/all/org-mode/agenda.ics")
| )
`

with:

,[ example events ]
| ** <2012-03-20 8:00-9:30> Test
| :PROPERTIES:
| :CREATED: [2012-03-20 Tue 10:38]
| :END:
|
| ** <2012-03-20 8:12-13:12> Test
| :PROPERTIES:
| :CREATED: [2012-03-20 Tue 10:40]
| :END:
`

results in:

,[ ics result ]
| vk@gary ~all/org-mode (git)-[master] % grep -C 2 Test agenda.ics
| DTSTART;VALUE=DATE:20120320
| DTEND;VALUE=DATE:20120320
| SUMMARY: Test
| CATEGORIES:misc
| END:VEVENT
| --
| DTSTART;VALUE=DATE:20120320
| DTEND;VALUE=DATE:20120320
| SUMMARY: Test
| CATEGORIES:misc
| END:VEVENT
| vk@gary ~all/org-mode (git)-[master] %
`

-- 
Karl Voit

Re: [O] Timezone/Encoding issues when exporting as ics and importing to Google Calendar

[Kevin Brubeck Unhammer]

Bastien  writes:

> Hi Kevin,
>
> Kevin Brubeck Unhammer  writes:
>
>> I guess I'll have to upgrade my org-mode version (6.33x) to get
>> org-icalendar-date-time-format?
>
> Not sure this will fix your problem, but yes, 6.33x is kinda 
> prehistoric now.
>
> Best,

I ended up making a function to turn local time into UTC
(http://paste.pocoo.org/raw/568445/ , probably could've been a lot
simpler, but I don't really understand all the various time formats
floating around), seems to work so far. And of course had to redefine
org-ical-ts-to-string to take org-icalendar-date-time-format
(":%Y%m%dT%H%M%SZ") into account, and use time-to-utc before formatting
(http://paste.pocoo.org/raw/568448/). 

It works :-/


-Kevin

Re: [O] [PATCH] Add "Time-stamp: <>" in (first 8 lines of) export template

[Sebastien Vauban]

Hi Bastien,

Bastien wrote:
> "Sebastien Vauban"  writes:
>
>>>From 74f376c12cceae196f5a856eac1a39cdbcc8e360 Mon Sep 17 00:00:00 2001
>> From: Sebastien Vauban 
>> Date: Thu, 16 Feb 2012 15:48:37 +0100
>> Subject: [PATCH] Add Time-stamp in export template
>>
>> ---
>>  lisp/org-exp.el |1 +
>>  1 files changed, 1 insertions(+), 0 deletions(-)
>
> I'm not applying this patch.
>
> I see how it can be useful for those who use
>
> (add-hook 'before-save-hook 'time-stamp)
>
> but #+Time-stamp is *not* an Org option... so unless we find
> a way to use it without confusing the user, I won't apply it.

OK, so what about adding it as an Org option?

Even if, by default, it must be capitalized as in the example, I can make it
become case-insensitive, so that `#+time-stamp', `#+Time-stamp' and
`#+TIME-STAMP' all are accepted.

Then, I can provide a patch with `time-stamp' function added to
`before-save-hook' in Org mode.

> If you have another proposal, please provide a commit message
> with your patch!

I'll do.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] Referencing a cell from a clockview table looks impossible

[Sebastien Vauban]

Hello,

I just found the reason: it's because *the "Total time" is in bold*, with `*'
before and after the total (for example: *3:33*).

* Design

Some tasks with CLOCK lines, for showing the problem.

** TODO Do this
   :LOGBOOK:
   CLOCK: [2012-03-19 Mon 09:00]--[2012-03-19 Mon 10:11] =>  1:11
   :END:

* Develop

** TODO Do that
   :LOGBOOK:
   CLOCK: [2012-03-19 Mon 10:00]--[2012-03-19 Mon 12:22] =>  2:22
   CLOCK: [2012-03-20 Tue 10:01]--[2012-03-20 Tue 12:35] =>  2:34
   :END:

* Report

** Dynamic block

The dynamic block captures the fact that I've worked 3:33 hours yesterday, on
2 different tasks.

#+TBLNAME: hours-yesterday
#+BEGIN: clocktable :maxlevel 4 :scope file :block yesterday
Clock summary at [2012-03-20 Tue 14:12], for Monday, March 19, 2012.

| Headline | Time |  |
|--+--+--|
| *Total time*   | *3:33* |  |
|--+--+--|
| Design   | 1:11 |  |
| TODO Do this |  | 1:11 |
| Develop  | 2:22 |  |
| TODO Do that |  | 2:22 |
#+END:

** Table with remote reference

As said above, referencing an "regular" (not bold) total does work, as in:

| Tasks | HH:MM | Float | USD |
|---+---+---+-|
| Yesterday | 1:11  |  1.18 | 30:11   |
|---+---+---+-|
|   | Time  |  1.18 | 30 Time |
#+TBLFM: $3='(/ (float (org-hh:mm-string-to-minutes $2)) 
60.);%.2f::$4=$2*30::@2$2=remote(hours-yesterday,@3$2)::@3$3=vsum(@-I..@-II)

But the real grand total is not referencable:

| Tasks | HH:MM  | Float | USD|
|---++---+|
| Yesterday | #ERROR |  0.00 | #ERROR |
|---++---+|
|   ||0. | 0  |
#+TBLFM: $3='(/ (float (org-hh:mm-string-to-minutes $2)) 
60.);%.2f::$4=$2*30::@2$2=remote(hours-yesterday,@2$2)::@3$3=vsum(@-I..@-II)

Any idea how to work around this?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] [bug] org-agenda-write does not handle date stamps without day of week

[Nick Dokos]

Karl Voit  wrote:

> * Carsten Dominik  wrote:
> > I have just pushed the new version of this regexp into master.
> 
> Very cool!
> 
> > Karl, let me know if it fixes the issues you where having
> > with writing agendas.
> 
> My agenda looks fine. But generating the ics file still results in
> events without the time information:
> 
> ,[ my function generating the ics ]
> | (defun vk-export-agenda()
> |   "Exports monthly Org-mode agenda to agenda.ics file"
> |   (interactive)
> |   (org-agenda-list nil nil 60)
> |   (org-agenda-write "~/share/all/org-mode/agenda.ics")
> | )
> `
> 
> with:
> 
> ,[ example events ]
> | ** <2012-03-20 8:00-9:30> Test
> | :PROPERTIES:
> | :CREATED: [2012-03-20 Tue 10:38]
> | :END:
> |
> | ** <2012-03-20 8:12-13:12> Test
> | :PROPERTIES:
> | :CREATED: [2012-03-20 Tue 10:40]
> | :END:
> `
> 
> results in:
> 
> ,[ ics result ]
> | vk@gary ~all/org-mode (git)-[master] % grep -C 2 Test agenda.ics
> | DTSTART;VALUE=DATE:20120320
> | DTEND;VALUE=DATE:20120320
> | SUMMARY: Test
> | CATEGORIES:misc
> | END:VEVENT
> | --
> | DTSTART;VALUE=DATE:20120320
> | DTEND;VALUE=DATE:20120320
> | SUMMARY: Test
> | CATEGORIES:misc
> | END:VEVENT
> | vk@gary ~all/org-mode (git)-[master] %
> `
> 

I get

BEGIN:VEVENT
UID: TS-11c60341-06a6-4b6f-bb22-2ccd739bbdc8
DTSTART:20120320T08
DTEND:20120320T093000
SUMMARY: Test
CATEGORIES:foo
END:VEVENT

BEGIN:VEVENT
UID: TS-dc99f34e-e24a-4ecc-add5-fa67649b005e
DTSTART:20120320T081200
DTEND:20120320T131200
SUMMARY: Test
CATEGORIES:foo
END:VEVENT

which looks correct to me.

Check that you picked up Carsten's fix (commit ):

  git show 7d84b300f4cba8b726662113d4ce4ff40a76c5b5

If you did M-x org-reload RET only, then that's probably the reason:
check to see if the value of org-ts-regexp0 has been updated; in my case
it hadn't and I ended up doing M-x load-file RET /path/to/org.el RET.
Alternatively, restart emacs.

Nick

Re: [O] [bug] org-agenda-write does not handle date stamps without day of week

[Carsten Dominik]

Hi Karl,

I am not able to reproduce this.  I am getting

BEGIN:VEVENT
UID: TS-13B9F6A7-BF2B-445C-84CA-7FB8ED15E0C1
DTSTART:20120320T08
DTEND:20120320T093000
SUMMARY: Test
CATEGORIES:x
END:VEVENT
BEGIN:VEVENT
UID: TS-AF0458B6-C5D6-4419-9DBB-FAB0651EF870
DTSTART:20120320T081200
DTEND:20120320T131200
SUMMARY: Test
CATEGORIES:x
END:VEVENT

Looks right to me.

- Carsten

On 20.3.2012, at 13:26, Karl Voit wrote:

> * Carsten Dominik  wrote:
>> I have just pushed the new version of this regexp into master.
> 
> Very cool!
> 
>> Karl, let me know if it fixes the issues you where having
>> with writing agendas.
> 
> My agenda looks fine. But generating the ics file still results in
> events without the time information:
> 
> ,[ my function generating the ics ]
> | (defun vk-export-agenda()
> |   "Exports monthly Org-mode agenda to agenda.ics file"
> |   (interactive)
> |   (org-agenda-list nil nil 60)
> |   (org-agenda-write "~/share/all/org-mode/agenda.ics")
> | )
> `
> 
> with:
> 
> ,[ example events ]
> | ** <2012-03-20 8:00-9:30> Test
> | :PROPERTIES:
> | :CREATED: [2012-03-20 Tue 10:38]
> | :END:
> |
> | ** <2012-03-20 8:12-13:12> Test
> | :PROPERTIES:
> | :CREATED: [2012-03-20 Tue 10:40]
> | :END:
> `
> 
> results in:
> 
> ,[ ics result ]
> | vk@gary ~all/org-mode (git)-[master] % grep -C 2 Test agenda.ics
> | DTSTART;VALUE=DATE:20120320
> | DTEND;VALUE=DATE:20120320
> | SUMMARY: Test
> | CATEGORIES:misc
> | END:VEVENT
> | --
> | DTSTART;VALUE=DATE:20120320
> | DTEND;VALUE=DATE:20120320
> | SUMMARY: Test
> | CATEGORIES:misc
> | END:VEVENT
> | vk@gary ~all/org-mode (git)-[master] %
> `
> 
> -- 
> Karl Voit
> 
> 

[O] HTML Export Error : org-export-replace-src-segments-and-examples: Args out of range: 0, 0

[Sankalp]

Hi,

I'm facing a strange issue. On exporting the attached .org file to HTML, I
often have to do it in 2 passes.

Most of the times the 1st pass throws an error, and the output in the
*Messages* buffer is like this :

OVERVIEW
Export buffer:
Exporting...
(New file)
org-babel-exp processing...
OVERVIEW
Position saved to mark ring, go back with C-c &.
OVERVIEW
executing Python code block...
Code block evaluation complete.
org-babel-exp processing...
OVERVIEW
Position saved to mark ring, go back with C-c &.
OVERVIEW
executing Python code block...
Code block evaluation complete.
org-babel-exp processing...
OVERVIEW
Position saved to mark ring, go back with C-c &.
OVERVIEW
executing Python code block...
Code block evaluation complete.
org-babel-exp processing...
OVERVIEW
Position saved to mark ring, go back with C-c &.
OVERVIEW
executing Python code block...
Code block evaluation complete.
org-babel-exp processing...
OVERVIEW
Position saved to mark ring, go back with C-c &.
OVERVIEW
executing Python code block...
Code block evaluation complete.
org-babel-exp processing...
OVERVIEW [2 times]
executing Python code block...
Code block evaluation complete.
org-babel-exp processing...
OVERVIEW
Position saved to mark ring, go back with C-c &.
OVERVIEW
executing Python code block...
Code block evaluation complete.
org-babel-exp processing...
OVERVIEW
Position saved to mark ring, go back with C-c &.
OVERVIEW
executing Python code block...
Code block evaluation complete.
org-babel-exp processing...
OVERVIEW
Position saved to mark ring, go back with C-c &.
OVERVIEW
executing Python code block...
Code block evaluation complete.
org-babel-exp processing...
OVERVIEW
Position saved to mark ring, go back with C-c &.
OVERVIEW
executing Python code block...
Code block evaluation complete.
org-babel-exp processing...
OVERVIEW
Position saved to mark ring, go back with C-c &.
OVERVIEW
executing Python code block...
Code block evaluation complete.
org-babel-exp processing...
OVERVIEW
Position saved to mark ring, go back with C-c &.
OVERVIEW
executing Python code block...
Code block evaluation complete.
Fontifying  org-src-fontification:python-mode... (regexps..)
Code block evaluation complete.
Fontifying  org-src-fontification:python-mode... (regexps..)
Code block evaluation complete.
Fontifying  org-src-fontification:python-mode... (regexps..)
Code block evaluation complete.
Fontifying  org-src-fontification:python-mode... (regexps..)
Code block evaluation complete.
Fontifying  org-src-fontification:python-mode... (regexps..)
Code block evaluation complete.
Fontifying  org-src-fontification:python-mode... (regexps..)
Code block evaluation complete.
Fontifying  org-src-fontification:python-mode... (regexps..)
Code block evaluation complete.
Fontifying  org-src-fontification:python-mode... (regexps..)
Code block evaluation complete.
Fontifying  org-src-fontification:python-mode... (regexps..)
Code block evaluation complete.
Fontifying  org-src-fontification:python-mode... (regexps..)
Code block evaluation complete.
Fontifying  org-src-fontification:python-mode... (regexps..)
Code block evaluation complete.
Fontifying  *temp*<2>... (regexps..)
Code block evaluation complete.
org-export-replace-src-segments-and-examples: Args out of range: 0, 0

i.e. at the end I get this error - Args out of range: 0, 0

Strangely, doing an export for the 2nd time, without deleting the output
html file manages to do it successfully without throwing any errors.

Could someone examine the attached file and throw some light on what I
might be doing wrong?

Thanks,
--
Sankalp

***
If humans could mate with software, I'd have org-mode's
babies.
  --- Chris League on Twitter.
   http://orgmode.org/worg/org-quotes.html
***

Ps: Sorry about the long output transcript...


regex-python.org
Description: Lotus Organizer

[O] [bug] Assigning "0:00" to cell gives an error

[Sebastien Vauban]

Hello,

As shown by this example, we can't assign the value "0:00" to a cell:

| Task|  HH:MM |
|-+|
| This|   1:23 |
| Nothing | #ERROR |
| That|   1:23 |
#+TBLFM: @2$2=1:23::@3$2=0:00::@4$2=4:56

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] [bug] Assigning "0:00" to cell gives an error

[Carsten Dominik]

Hi Sebastien,

you can use @3$2=string("0:00")

- Carsten

On 20.3.2012, at 14:59, Sebastien Vauban wrote:

> Hello,
> 
> As shown by this example, we can't assign the value "0:00" to a cell:
> 
> | Task|  HH:MM |
> |-+|
> | This|   1:23 |
> | Nothing | #ERROR |
> | That|   1:23 |
> #+TBLFM: @2$2=1:23::@3$2=0:00::@4$2=4:56
> 
> Best regards,
>  Seb
> 
> -- 
> Sebastien Vauban
> 
> 

[O] Missing date in Org-Agenda Day buffer

[Rasmus Rempling]

Dear group,

When scheduling may working day I use the Org-Agenda Day view and the 
column mode with the format as given below. This work very well and I am 
happy with the set-up. However, as shown in the attached png file the 
date is missing. My initial thought was that it is the same color as the 
shadowy highlight of the table headlines, but this is the same as the 
effort-sum. I have tried to find a solution, but not succeded.


I have tried two different background/foreground with the same result 
(black/white and reverse).


Is there more users having the same problem? And if anyone could help 
out I would be pleased.


(setq org-columns-default-format "%60ITEM(Details) %5PRIORITY(PRIO) 
%12SCHEDULED(Scheduled) %15TAGS(Context) %7TODO(To Do) 
%5Effort(Effort){:} %6CLOCKSUM ")


Emacs v. 23.3.1

Org-mode v. 7.6

--
/rasmus

<>

Re: [O] how to specify table width in HTML export

[Nick Dokos]

Michael Hannon  wrote:

> > From: Nick Dokos 
> >
> > Stephen J. Barr  wrote:
> >
> >> Hello,
> >>
> >> This seems like a simple question but I can't seem to find the answer?
> >> How do I specify the table width for an org-table that I will export
> >> to HTML?
> >>
> >
> > Not sure about the real HTMl syntax, or whether this is the best
> > solution (I'd imagine CSS would be better *if* it can be done with CSS)
> > but the following:
> >
> > #+ATTR_HTML: width="100"
> > | col1 | col2 |
> > |--+--|
> > |    1 |    3 |
> > |  |  |
> >
> > gets translated into an HTML table with an opening tag like this:
> >
> >  > cellpadding="6" rules="groups" frame="hsides"
> > width="100">
> >
> > Does that do the trick?
> 
> Indeed, I think CSS would be a better approach.  And of course I don't know
> what this particular application is, but it's usually better to specify the
> width of objects as a percentage of the overall width.
> 

Just to make sure

#+ATTR_HTML: width="50%"

is just the "same" as far as the HTML exporter is concerned: it'll just blindly
tack it to the  tag.

> This is discussed, for instance, at:
> 
>     http://www.w3schools.com/css/css_table.asp
> 

Nice reference, thanks! Particularly for those (like me) whose CSS fu is
weak to non-existent.

> Here's a line from one of my old .org files that shows the syntax:
> 
>     #+STYLE:    
> 
> It's also possible to embed the styling information directly in the Org-mode
> file, but I find that to be less convenient, as you then have to re-export to
> make a change to the style.
> 
> Caveat: I haven't done any HTML exporting to speak of lately, certainly none
> that has involved CSS, so it may be that the syntax has changed (i.e.,
> compared to the above STYLE directive).
> 

I think things have not changed in this area.

Nick

Re: [O] AUCTeX conflicting with org-mode

[suvayu ali]

Hi Bastien and Yagnesh,

On Tue, Mar 20, 2012 at 12:02, Bastien  wrote:
> Hi Yagnesh,
>
> Yagnesh Raghava Yakkala  writes:
>
>> Thanks for the analysis. I think you are right. With my limited elisp skills 
>> I
>> would say its a *bug* and coming from org.
>>
>> If I take that let-binding off and setting the TeX-master by checking with
>> if it ever bound seems fixing this problem.
>>
>> this patch fixing the problem. (can be further improved)
>
> Applied, thanks.
>

I wanted to comment earlier but it slipped my mind, sorry about that.

I am not sure if this patch is quite corect. It removes the let bind and
instead conditionally uses setq to bind it to t. From the docs I see the
variable becomes buffer local when set in any fashion, but does that
still mean it is okay to use setq?

I can imagine in a complicated publishing project, an org file might
need to set the value to something. I suppose this will override any
such custom config. Is my analysis correct? It might be worth thinking
about before applying the patch.

Is a conditional let binding possible, it might be the safer choice in
that case.

Thanks,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] [PATCH] org-mobile agenda title

[Bastien]

Hi Henning,

Henning Weiss  writes:

> I have a little revision to the patch to remove the matching
> criterion from "normal" (ie. non-block) agendas as well. See below.

Applied in master, thanks.

-- 
 Bastien

Re: [O] [PATCH] Add "Time-stamp: <>" in (first 8 lines of) export template

[Brian Wightman]

On Tue, Mar 20, 2012 at 7:45 AM, Sebastien Vauban
 wrote:
> Then, I can provide a patch with `time-stamp' function added to
> `before-save-hook' in Org mode.

I would lobby against this being the default template, as these time
stamps really mess up the ability to merge org files from multiple
branches without conflicts.

A --- B --- D
\ /
 \C/

At the merge, D would have a conflict to resolve by hand.

I used timestamps and the save hook mentioned above for a while and
ended up needing to do unnecessary (and in the context of a rev
control like GIT - non-useful) manual conflict resolution, so have
since removed them from every file I had previously added them to.

Just my $0.02.

Brian
---
midlife...@wightmanfam.org

Re: [O] O[PATCH] org-export-generic table exporting

[Bastien]

Hi there,

Wes Hardaker  writes:

> TA> This is my first post to this mailing list, and my first ever
> TA> contribution to an open-source project so I look forward to feedback
> TA> and be kind when you point out any sort of mailing list etiquette I
> TA> might have broken.
>
> Well, I think you've certainly given a good first shot at a
> contribution!
>
> [Hopefully someone with write access will apply it soon]

Applied in master.  

Thanks Tom for the patch and Wes for the check!

-- 
 Bastien

Re: [O] Multiple :LOGBOOK: blocks "allowed" without unwanted side effects?

[Rainer Stengele]

Am 20.03.2012 10:52, schrieb Achim Gratz:
> Rainer Stengele  online.de> writes:
>> I want to be sure that multiple :LOBGOOK: blocks in sequence are making no
> trouble.
> 
> I don't know about having multiple LOGBOOK drawers, that feels dirty...  What 
> I
> do is having a CLOSED drawer defined, putting it directly behind the LOGBOOK
> drawer and then just shift the boundary between the two (the two lines
> :END:\n:CLOSED:\n) whenever I feel like it (at the end of the week, mainly).
> 
> :LOGBOOK:
> whatever
> :END:
> :CLOSED:
> whatever else
> :END:
> 
> Achim.
> 
> 
> 

I wonder if any of the clocking table functions is looking at the drawer names 
or begin end markers or
is simply collecting all CLOCK entries, which would say that the 
"management/hiding" of the
CLOCK entries by drawer names is no problem.

Rainer

Re: [O] AUCTeX conflicting with org-mode

[Bastien]

Hi Suvayu,

suvayu ali  writes:

> I wanted to comment earlier but it slipped my mind, sorry about that.
>
> I am not sure if this patch is quite corect. It removes the let bind and
> instead conditionally uses setq to bind it to t. From the docs I see the
> variable becomes buffer local when set in any fashion, but does that
> still mean it is okay to use setq?
>
> I can imagine in a complicated publishing project, an org file might
> need to set the value to something. I suppose this will override any
> such custom config. Is my analysis correct? It might be worth thinking
> about before applying the patch.
>
> Is a conditional let binding possible, it might be the safer choice in
> that case.

I applied a patch into hotfix-7.8.06 using the let binding -- let me
know if this works correctly.

Thanks!

-- 
 Bastien

[O] graphiclog in browser of public git repo

[Michael Brand]

Hi all

The browser of the mirror of the public git repo
http://repo.or.cz/w/org-mode.git
has a link "graphiclog" that shows a line for each branch and merge
and a dot for each commit. I hope that such a link could also be added
to the browser of the public git repo
http://orgmode.org/w/org-mode.git
to make the visualization of the git workflow easier to access and more notable.

Michael

Re: [O] Missing date in Org-Agenda Day buffer

[Nick Dokos]

Rasmus Rempling  wrote:

> Dear group,
> 
> When scheduling may working day I use the Org-Agenda Day view and the
> column mode with the format as given below. This work very well and I
> am happy with the set-up. However, as shown in the attached png file
> the date is missing. My initial thought was that it is the same color
> as the shadowy highlight of the table headlines, but this is the same
> as the effort-sum. I have tried to find a solution, but not succeded.
> 
> I have tried two different background/foreground with the same result
> (black/white and reverse).
> 
> Is there more users having the same problem? And if anyone could help
> out I would be pleased.
> 
> (setq org-columns-default-format "%60ITEM(Details) %5PRIORITY(PRIO)
> %12SCHEDULED(Scheduled) %15TAGS(Context) %7TODO(To Do)
> %5Effort(Effort){:} %6CLOCKSUM ")
> 

Yes, I can reproduce that and it does seem like a bug. I traced it
down to 

 org-agenda-columns -->
  org-agenda-colview-summarize -->
   org-columns-display-here

but I don't have time to take it further. As you surmised, the dates are
there: if you do C-u C-x = at the appropriate places, you'll see the
chars, but I guess the fg/bg colors are the same. I append the report I
get from one such (the first char on tomorrow's date). It may be that
the (:foreground unspecified) below is the culprit, but I'm just guessing.

Nick

---
character: W (87, #o127, #x57)
preferred charset: ascii (ASCII (ISO646 IRV))
   code point: 0x57
   syntax: wwhich means: word
 category: .:Base, L:Left-to-right (strong), a:ASCII, l:Latin, r:Roman
  buffer code: #x57
file code: #x57 (encoded by coding system utf-8-unix)
  display: by this font (glyph code)
x:-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso8859-1 (#x57)

Character code properties: customize what to show
  name: LATIN CAPITAL LETTER W
  old-name: 
  general-category: Lu (Letter, Uppercase)
  decomposition: (87) ('W')

There are 2 overlays here:
 From 999 to 1024
  face hl-line
  window   nil
 From 999 to 1000
  display  "
 | "
  face ((:foreground unspecified) org-agenda-column-dateline 
org-agenda-date)
  keymap   [Show]
  line-prefix  ""
  org-columns-format   "%-60.60s | "
  org-columns-key  "ITEM"
  org-columns-pom  nil
  org-columns-valuenil
  org-columns-value-modified ""
  wrap-prefix  ""


There are text properties here:
  day  734583
  face org-agenda-date
  org-agenda-date-header t
  org-agenda-type  agenda
  org-date-linet
  org-day-cnt  2
  read-only"Type `e' to edit property"

[O] [Jambunathan K] Re: Figure and table captions in org-odt.el

[Jambunathan K]

Martin Gürtler  writes:

> Hi,
>
> I was trying to localise the captions of figures or tables. This seems
> not to be built-in (in contrast to the built-in localisation of
> table-of-contents). I wonder whether it is easily possible to get
> "Abbildung 1: ..." instead of the automatic "Figure 1: ..."  in figure
> (and table) captions.

I have added support for this a few minutes ago.  Please discard/undo my
earlier suggestion and try configuring the new variable instead (see
below).

With this change applied and *after* exporting the document via the ODT
exporter, you may want to:

1. create a figure/table index with Insert->Indexes and Tables->Indexes
   and Tables etc
2. insert a couple of figures tables etc *by hand*
3. update fields with Tools->Update->Update All

and make sure that you don't get any weird behaviour.

If there are non-English speakers who are reading this message and then
you may want to give me the localized equivalent for Table, Figure,
Equation in your language.

,[ C-h v org-export-odt-category-strings RET ]
| org-export-odt-category-strings is a variable defined in `org-odt.el'.
| Its value is (("en" "Table" "Figure" "Equation" "Equation")
|  ("de" "Tabelle" "Abbildung" nil nil))
| 
| Original value was 
| (("en" "Table" "Figure" "Equation" "Equation"))
| 
| 
| Documentation:
| Specify category strings for various captionable entities.
| Captionable entity can be one of a Table, an Embedded Image, a
| LaTeX fragment (generated with dvipng) or a Math Formula.
| 
| For example, when `org-export-default-language' is "en", an
| embedded image will be captioned as "Figure 1: Orgmode Logo".
| If you want the images to be captioned instead as "Illustration
| 1: Orgmode Logo", then modify the entry for "en" as shown
| below.
| 
|   (setq org-export-odt-category-strings
|   '(("en" "Table" "Illustration"
|  "Equation" "Equation")))
| 
| You can customize this variable.
| 
| This variable was introduced, or its default value was changed, in
| version 24.1 of Emacs.
| 
| [back]
`

[O] [Jambunathan K] Re: Figure and table captions in org-odt.el

[Jambunathan K]

[Out of thread]

I have also made the following commits in response to your earlier
request titled "Is it possible to refer to section numbers in links?"[1]

commit d3cd3720d5a0a2993d37a43046c36535cdaf8bce
Author: Jambunathan K 
Date:   Tue Mar 20 19:53:28 2012 +0530

org-odt.el: Resolve headline links as sec nos only if num:t

* lisp/org-odt.el (org-odt-format-org-link): Resolve links to
headlines as section numbers only if section numbering is on.

commit 4120d6fcf741f04673e90133ee8fb98a879c8e1d
Author: Jambunathan K 
Date:   Tue Mar 20 13:32:23 2012 +0530

org-odt.el: Render links to outline headings as section nos

* lisp/org-odt.el (org-odt-format-link): Add support for
generating cross-references to chapter numbers.
(org-odt-format-org-link): Resolve links to outline headings
as section numbers.  This special case resolution kicks in
only if the Org link has no description and the target outline
is not listified i.e., it is at a level within
`org-export-headline-levels'.

The above change is in conformity with the way links to
headlines will be treated in new ODT exporter that will be
built on top of Nicolas' org-element/org-export
infrastructure.

Footnotes: 
[1]  http://lists.gnu.org/archive/html/emacs-orgmode/2012-02/msg01035.html

Re: [O] Multiple :LOGBOOK: blocks "allowed" without unwanted side effects?

[Achim Gratz]

Rainer Stengele  writes:
> I wonder if any of the clocking table functions is looking at the
> drawer names or begin end markers or is simply collecting all CLOCK
> entries, which would say that the "management/hiding" of the CLOCK
> entries by drawer names is no problem.

Nicolas would be a more authoritative source, but AFAIK the drawers are
completely transparent to anything that works with existing markers.
They are only looked up when you create a new entry and specified which
drawer they should end up in.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

[O] org ELPA package 20120216 cannot be downloaded

[Tassilo Horn]

Hi all,

on IRC someone just reported that org 20120216 as it is listed in the
GNU ELPA archive won't download.  When trying to install, all you get is
this error:

  package-handle-response: Error during download request: Not Found

Probably a dead link or something alike...

Bye,
Tassilo

Re: [O] org ELPA package 20120216 cannot be downloaded

[Christopher Schmidt]

Tassilo Horn  writes:

> on IRC someone just reported that org 20120216 as it is listed in the
> GNU ELPA archive won't download.  When trying to install, all you get
> is this error:
>
>   package-handle-response: Error during download request: Not Found
>
> Probably a dead link or something alike...

I think this is a GNU ELPA problem.  The cronjob that mirrors the
content of the ELPA branch to the actual files that can be accessed via
elpa.gnu.org/packages is no run any more.  It looks like the 14th of
February was the last time it ran.

Christopher

Re: [O] [DEV] New git workflow

[Achim Gratz]

Bastien  writes:
> Agreed.  What I want on top of this is a to have a branch where *every*
> commit corresponds to a single release.

Fair enough: a three-branch model with a release branch at the side of
bugfixing and bleeding edge.

> No.  All hotfix branches should merge into master regularily.  When
> hotfix contains enough fixes for a bugfix release, then we merge it to
> maint, and process with release.

This is what I think is confusing: the bugfix branch (be it maint or any
other) should always have the same _unless_ you want to track release
specific bugfixes (which I don't think you do, but you tell me).  If it
changes name at every release, that just begs for a mix-up to happen
when you are preparing for release and someone else tries to do one more
fix.

> My main goal is this: have a branch with one commit = one release.

Why not name it release then and keep maint for fixes?  You could even
install that release branch retro-actively if you want.  BTW, this also
means you need to prepare the release on the hotfix branch, no
fier-upper on the release allowed at all (since you would need to merge
that back).

But as I said before, clone the repo, branch off the 7.7 release or so
and re-trace the following releases via cherry-pick according to that
new development model.  You will quickly learn if what you have to do
feels right and if you commit to that model you will have practised the
moves a few times already.

Another thing that I'd recommend is to not work on the public repo _at
all_ and specifically never push to it, especially not automatically.
The public repo should be "bare" (without a work tree) and any work on
the server should use a clone of that repo, just like anyone else.  If
you prepare the releases on a fresh clone apart from the development
clone, you have a stable base to work from and can nuke with no
consequences if something goes wrong.  Git was designed to make merges
easier, but they are hard and I still botch about every tenth that I try
unless they are really trivial.  Once the release repo is finished, have
it reviewed and then pull from it on the public repo.  The reason is
that it is easy to push from the wrong branch onto the wrong target, but
you really have to try to do that when pulling.  You can be more liberal
with the normal development and bugfixing work on the development repo,
but it would still be a good idea to have commits reviewed and signed
off by another person before they are pulled into public.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

[O] LaTeX export - can't skip a heading level

[Richard Stanton]

Using org-mode 7.8.03, I've found that exporting to LaTeX has a tough time
if you try to skip a header level. For example, to prevent my TODO items
being numbered, one method is to make them a lower-level heading, and then
make that level un-numbered.

However, if I try the following:

* To Do List
*** TODO First item
*** TODO Second item

Then when exported to LaTeX, only the title appears (both TODO items are
excluded).

I tried make the first title one level lower, like this:

** To Do List
*** TODO First item
*** TODO Second item

* Next Section

Now the TODO list exports, though it now treats ** as the section header,
so it hasn't solved that problem, and moreover, the next section is
omitted entirely.

[O] TODO items as part of an itemized list?

[Richard Stanton]

To save space in LaTeX exports and also to stop my TODO items being
numbered, I'd like to have TODO items as part of a list, e.g.,

- TODO Item 1
- TODO Item 2

However, while this prints OK, these entries are ignored by org-mode when
I ask it to create a TODO list. Is there any way to do what I want?

Thanks.

Re: [O] HTML Export Error : org-export-replace-src-segments-and-examples: Args out of range: 0, 0

[Achim Gratz]

Sankalp  writes:
> i.e. at the end I get this error - Args out of range: 0, 0

Well, it tells you that the input to that function was unexpected.  You
could do M-: (setq debug-on-error) and see what the backtrace turns up.

> Strangely, doing an export for the 2nd time, without deleting the
> output html file manages to do it successfully without throwing any
> errors.

Which seems to hint at some undeclared variable that is brought into
scope by the first run.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: [O] org ELPA package 20120216 cannot be downloaded

[Christopher Schmidt]

Christopher Schmidt  writes:

> I think this is a GNU ELPA problem.  The cronjob that mirrors the
> content of the ELPA branch to the actual files that can be accessed
> via elpa.gnu.org/packages is no run any more.  It looks like the 14th
> of February was the last time it ran.

BTW. the script I am referring to[1] is responsible for grabbing org
daily and pushing it to GNU ELPA.

Christopher

[1] 
http://bzr.savannah.gnu.org/lh/emacs/elpa/annotate/head:/admin/package-update.sh#L80

Re: [O] LaTeX export - can't skip a heading level

[Nick Dokos]

Richard Stanton  wrote:

> Using org-mode 7.8.03, I've found that exporting to LaTeX has a tough time
> if you try to skip a header level. For example, to prevent my TODO items
> being numbered, one method is to make them a lower-level heading, and then
> make that level un-numbered.
> 
> However, if I try the following:
> 
> * To Do List
> *** TODO First item
> *** TODO Second item
> 

Does this do what you want?

--8<---cut here---start->8---

#+OPTIONS: num:1

* To Do List
** TODO First item
** TODO Second item
--8<---cut here---end--->8---

Nick

PS. Not sure why the third level headlines are skipped if the second level
headline is absent. This feels like a bug to me.

> Then when exported to LaTeX, only the title appears (both TODO items are
> excluded).
> 
> I tried make the first title one level lower, like this:
> 
> ** To Do List
> *** TODO First item
> *** TODO Second item
> 
> * Next Section
> 
> Now the TODO list exports, though it now treats ** as the section header,
> so it hasn't solved that problem, and moreover, the next section is
> omitted entirely.
> 
> 
> 
> 
> 
> 
> 
> 

Re: [O] LaTeX export - can't skip a heading level

[Richard Stanton]

> From: nicholas.do...@hp.com [mailto:nicholas.do...@hp.com]
> Sent: Tuesday, March 20, 2012 12:55 PM
> To: Richard Stanton
> Cc: emacs-orgmode@gnu.org; nicholas.do...@hp.com
> Subject: Re: [O] LaTeX export - can't skip a heading level
> 
> Richard Stanton  wrote:
> 
> > Using org-mode 7.8.03, I've found that exporting to LaTeX has a tough
> > time if you try to skip a header level. For example, to prevent my
> > TODO items being numbered, one method is to make them a lower-level
> > heading, and then make that level un-numbered.
> >
> > However, if I try the following:
> >
> > * To Do List
> > *** TODO First item
> > *** TODO Second item
> >
> 
> Does this do what you want?
> 
> --8<---cut here---start->8---
> 
> #+OPTIONS: num:1
> 
> * To Do List
> ** TODO First item
> ** TODO Second item
> --8<---cut here---end--->8---

Not quite, I don't think, as it removes numbers from *all* second level headers.

[O] ELPA syncing cronjob stopped running

[Tassilo Horn]

Hi all,

on irc some user reported that the current org-mode version listed in
`M-x package-list-packages' cannot be downloaded anymore.  It seems that
this is caused by some cronjob that stopped running on February, 14th.

> Christopher Schmidt  writes:
>
>> I think this is a GNU ELPA problem.  The cronjob that mirrors the
>> content of the ELPA branch to the actual files that can be accessed
>> via elpa.gnu.org/packages is no run any more.  It looks like the 14th
>> of February was the last time it ran.
>
> BTW. the script I am referring to[1] is responsible for grabbing org
> daily and pushing it to GNU ELPA.
>
> Christopher
>
> [1] 
> http://bzr.savannah.gnu.org/lh/emacs/elpa/annotate/head:/admin/package-update.sh#L80

Bye,
Tassilo

[O] List all habits with consistency graph

[Henning Weiss]

Hi,

I was wondering how to create a list that contains all habits including
their consistency graph. At the end of the week I want an overview over all
of my habit entries and how consistent I have been. Consistency graphs are
a nice for that purpose, but they are scattered all over my weekly (or
monthly!) agenda. This makes it rather hard to get a concise overview.

It would be nice if orgmode could somehow show all habits in a list with
the corresponding consistency graph next to it. It's straight forward to
create a property search that finds and displays all habits, but org-mode
has so far resisted my attempts at inserting consistency graphs into those
search views.

How could this be accomplished?

best regards,
Henning Weiss

Re: [O] LaTeX export - can't skip a heading level

[Nick Dokos]

Nick Dokos  wrote:

> Richard Stanton  wrote:
> 
> > Using org-mode 7.8.03, I've found that exporting to LaTeX has a tough time
> > if you try to skip a header level. For example, to prevent my TODO items
> > being numbered, one method is to make them a lower-level heading, and then
> > make that level un-numbered.
> > 
> > However, if I try the following:
> > 
> > * To Do List
> > *** TODO First item
> > *** TODO Second item
> > 
> 
> > Then when exported to LaTeX, only the title appears (both TODO items are
> > excluded).
> > 
> PS. Not sure why the third level headlines are skipped if the second level
> headline is absent. This feels like a bug to me.
> 

The latex exporter is very rigid about what it will accept: it wants the
levels to be in strict sequence. So this has to be chalked down as a
fairly deeply ingrained limitation of the exporter. I don't see an easy way
to lift it.

Nick

Re: [O] Org-mode version 7.8.05 (release_7.8.05.19.gb32d.dirty) `org-agenda-filter' bug pushing to mobile

[Alexander Vorobiev]

Hi,
I have just downloaded zip for 7.8.06 and the org-mobile.el's
line (org-agenda-filter org-agenda-filter) is still there, had to apply the
patch to make org-mobile-push work.

Thanks
Alex

On Mon, Mar 19, 2012 at 8:37 PM, Bastien  wrote:

> Nick Bell  writes:
>
> > Using the above version, needed to apply the patch
> > http://article.gmane.org/gmane.emacs.orgmode/51812 in order to make
> > org-mobile-push work. My git-fu isn't quite up to working out what should
> > (if anything) have happened to incorporate this fix into the release.
>
> This is fixed now in maint (included in 7.8.06) and master.
>
> Sorry for this.
>
> --
>  Bastien
>
>

Re: [O] List all habits with consistency graph

[Nick Bell]

On 20/03/12 20:21, Henning Weiss wrote:

Hi,

I was wondering how to create a list that contains all habits 
including their consistency graph. At the end of the week I want an 
overview over all of my habit entries and how consistent I have been. 
Consistency graphs are a nice for that purpose, but they are scattered 
all over my weekly (or monthly!) agenda. This makes it rather hard to 
get a concise overview.


It would be nice if orgmode could somehow show all habits in a list 
with the corresponding consistency graph next to it. It's straight 
forward to create a property search that finds and displays all 
habits, but org-mode has so far resisted my attempts at inserting 
consistency graphs into those search views.


This would be very helpful for me too.

Nick

[O] latex labels

[Marvin Doyley]

Hi there,

Do anyone know how to get org mode to list all the latex label in a given
org file. Something analogous that what reftex does, I can list all
citation in bib file, and thought it would be nice to do the same for
labels.

thanks
M

Re: [O] Org-mode version 7.8.05 (release_7.8.05.19.gb32d.dirty) `org-agenda-filter' bug pushing to mobile

[Nick Bell]

Org-mode version 7.8.06 (release_7.8.06.31.gc7a2) from git is correct:

(defun org-mobile-push ()
  "Push the current state of Org affairs to the WebDAV directory.
This will create the index file, copy all agenda files there, and also
create all custom agenda views, for upload to the mobile phone."
  (interactive)
  (let ((a-buffer (get-buffer org-agenda-buffer-name)))
(let ((org-agenda-buffer-name "*SUMO*")
  (org-agenda-tag-filter org-agenda-tag-filter)
  (org-agenda-redo-command org-agenda-redo-command))

Nick

On 20/03/12 21:02, Alexander Vorobiev wrote:

Hi,
I have just downloaded zip for 7.8.06 and the org-mobile.el's
line (org-agenda-filter org-agenda-filter) is still there, had to apply
the patch to make org-mobile-push work.

Thanks
Alex

On Mon, Mar 19, 2012 at 8:37 PM, Bastien mailto:b...@altern.org>> wrote:

Nick Bell mailto:mail%2b...@nickbell.org>>
writes:

 > Using the above version, needed to apply the patch
 > http://article.gmane.org/gmane.emacs.orgmode/51812 in order to make
 > org-mobile-push work. My git-fu isn't quite up to working out
what should
 > (if anything) have happened to incorporate this fix into the release.

This is fixed now in maint (included in 7.8.06) and master.

Sorry for this.

--
  Bastien

Re: [O] [DEV] New git workflow

[Simon Thum]

Hi all,

as discussion started anyway, I'd like to mention that I see some 
problem with maint, that is, it only ever pertains to the latest 
release. It's hard to hotfix and release old versions in the proposed model.


Moreover, maint is bound quite tightly to master. maint seems like a 
somewhat safer master to me - I fail to see a big difference between 
them. One may want to count that as a bonus; I don't. Part of the reason 
is that sometimes releases have commits that simply don't belong into 
master, like specific version increments.


Many projects use the IMO more sane model of release branches (or 
maintenance branches, if you prefer) for major releases. Minor ones are 
tagged on those branches, and back-porting critical fixes is much 
cleaner: Fixes and development go to master, fixes which should be 
back-ported are cherry-picked onto the release branches. When desired, a 
new release is tagged. Releases only come from release branches, of course.


If you like to see an example, the X server uses such a model:

http://cgit.freedesktop.org/xorg/xserver/

I guess a decision should mostly be based on how significant the use 
case "back-port fix" is to org-mode. The "safer master" role of maint 
could of course be retained in a stable branch which points to something 
like master@{1 month ago}.


Cheers,

Simon

On 03/20/2012 01:51 AM, Bastien wrote:

Hi all,

our current git workflow is pretty well summarised by Achim -- we have
two main branches, master and maint, and we (try to) follow these rules:

If it's a bugfix for something broken in a release version, commit to
maint and merge maint back into master.

If implementing a new feature or fixing something not yet released,
commit to master.

On top of that, some local development happens in dedicated branches.

The role of master is clear: it contains latest mature developments,
which are either (1) bugfixes merged from maint, (2) features merged
from dedicated branches or (3) features developed in master directly.

The role of maint is less clear: it is both a "hotfix" branch and a
release branch for bugfix releases.  The reason for this branch was
first that we need to keep a production-like version of Org in sync
with Emacs.

The main problem I see With this workflow is that releases are made
from two different branches: bugfix releases are made from maint and
major releases are made from master.  This doesn't look right to me.

So I suggest to use three branches with these rules:

- master: the main persistent branch.  This is were regular development
   goes.  This branch is merged back to the maint branch when we release
   a new major version.  No release happens directly from this branch.

- maint: the "production" persistent branch.  This branch is dedicated
   to the release process: when hot fixes are hot enough, we merge the
   hotfix branch to the maint branch and release a bugfix release.  When
   the master branch (where hot fixes are also merged to) is mature and
   well tested, we merge master into maint and release a major version.

- hotfix-7.XX.XX: the transient branch for hotfixes.  Severe bugs are
   fixed there first, then merged back to maint when this makes sense.
   The branch is created when we need it and deleted when we don't need
   it anymore.

This workflow looks clearer to me.  Here are the advantages I see:

1) *all releases happen on the same branch* (the maint branch): it is
easier to keep this branch in sync with Emacs and we can also add
git hooks to automate the release process.

2) the master branch *is* the development branch: yes, pretty unusual.
At least as unusual as not having two mailing lists, one for users
and one for devs.  But I want to stick to what makes this list a
great place: regular users are invited to live on the bleeding edge
and to contribute patches on the "development" branch, the one they
will clone first.

So, what's next?

I will merge 7.8.06 into Emacs.

Nothing should be committed to maint anymore before the next release.

Important bug fixes for 7.8.06 all go to a new branch hotfix-7.8.06.

Usual development goes to master, from where we regularily merge the
hotfix branch.

We'll get rid of the hotfix branch when releasing 7.8.07 or 7.9.

...

Finally, two positive things from the mess I put and went through:
I learned more about git, and I experienced once again how patient
and helpful people can be on this list.  Thanks to all again!

Re: [O] LaTeX export - can't skip a heading level

[Achim Gratz]

Nick Dokos  writes:
> The latex exporter is very rigid about what it will accept: it wants the
> levels to be in strict sequence. So this has to be chalked down as a
> fairly deeply ingrained limitation of the exporter. I don't see an easy way
> to lift it.

Especially as this is a limitation of LaTeX, not the exporter.

:-)


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html

Re: [O] [DEV] New git workflow

[Achim Gratz]

Simon Thum  writes:
> as discussion started anyway, I'd like to mention that I see some
> problem with maint, that is, it only ever pertains to the latest
> release. It's hard to hotfix and release old versions in the proposed
> model.

IMHO, that was never the objective.

> Moreover, maint is bound quite tightly to master. maint seems like a
> somewhat safer master to me - I fail to see a big difference between
> them.

That's what it was designed to be, a way for people with (and more so
without) git access to access the latest bugfixes without the vagaries
of evolving new features.

> One may want to count that as a bonus; I don't. Part of the
> reason is that sometimes releases have commits that simply don't
> belong into master, like specific version increments.
>
> Many projects use the IMO more sane model of release branches (or
> maintenance branches, if you prefer) for major releases. Minor ones
> are tagged on those branches, and back-porting critical fixes is much
> cleaner: Fixes and development go to master, fixes which should be
> back-ported are cherry-picked onto the release branches. When desired,
> a new release is tagged. Releases only come from release branches, of
> course.

Sorry, but cherry-picking into multiple release branches would simply
not be a sane development model for a small project like orgmode.

> I guess a decision should mostly be based on how significant the use
> case "back-port fix" is to org-mode. The "safer master" role of maint
> could of course be retained in a stable branch which points to
> something like master@{1 month ago}.

Any point in the past is no safer than today's master.  The stability
that maint should provide to users is with regards to the feature set,
i.e. no gratuitous changes between releases.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: [O] HTML Export Error : org-export-replace-src-segments-and-examples: Args out of range: 0, 0

[Sankalp]

Hi Achim,

On 21 March 2012 01:01, Achim Gratz  wrote:

> Sankalp  writes:
> > i.e. at the end I get this error - Args out of range: 0, 0
>
> Well, it tells you that the input to that function was unexpected.  You
> could do M-: (setq debug-on-error) and see what the backtrace turns up.
>
>
Here's what the backtrace says :

Debugger entered--Lisp error: (args-out-of-range 0 0)
  replace-match(#("\n#+BEGIN_html\nimport re # import the module\n\nmatch = re.search(r'iiit','iiit hyderabad is
in India')\nprint
match.group()\n\nmatch = re.search(r'iiit','iiit is in India.
IIIT offers CS degrees too.')\nprint match.group()\n\nmatch = re.search(r'he','this is the eiffel
tower. The eiffel tower is in France.')\nprint match.group()\n\n\n\n#+END_html\n" 0 14
(original-indentation 3) 14 961 (org-native-text t org-example t
org-protected t original-indentation 3) 961 973 (original-indentation 3)) t
t)
  org-export-replace-src-segments-and-examples()
  org-export-preprocess-string(#("#+TITLE: Regular Expressions in
Python\n#+STARTUP: overview   (others are showall)\n#+STARTUP:
hidestars\n#+OPTIONS: toc:nil\n\n* Introduction\n\n** Mathematical
understanding of regular expressions\n\n\n** regular expressions and
Operations\n - sequencing :: by default\n - grouping  ::  [abc]  one of any
characters in the group\n - alternation :: |\n - repetition :: a* and a+
and a?\n - complementation :: ^\n\n\n\n** From strings to Regular
expressions in Python ::\n   Using the 'r' keyword to indicate regular
expressions\n   instead of strings.\n\n\n** Metacharacters\n\n  - $ ::\n  -
^ :: inside a group, specifies complementation\n  - \\ :: used to escape
from the default meaning to a new meaning.  Eg, \\w, \\[, , etc.\n  - .
::\n\n** Special symbols ::\n\n  - \\d :: matches any decimal\n  - \\s ::
any whitespace character [\\t\\n\\r\\f\\v]\n  - \\w :: any alphanumeric
character\n  - .  :: matches any character except newline\n  - more\n\n\n**
Compiling regexes\n\n - pat = re.compile(r\"ab*\") :: This \"compiles\" the
regular\n  expression =ab*=.  The result is a pattern object.\n\n**
Using regexes\n\n\n - re.match(r, string) :: returns an object
that contains\n  a match at the BEGINNING of the string, else None.\n\n
- re.search(r, string) :: returns an object that contains a\n
match ANYWHERE in the string, else None\n\n - re.findall(r,
string) :: returns a list that\n  contains all the matches of the
pattern in the string.\n\n - re.finditer(r, string) :: returns an
iterator that\n  contains all the matches of the pattern in the
string.\n\n\n** Operations on the matched object\n\n  - group() :: returns
the string matched\n  - start() :: returns the start position of the
match\n  - end() :: returns the end position of the match\n  - span() ::
returns the group of starting and ending positions.\n\n* Examples\n\n  We
cover some simple examples of regular expressions\n\n** Basic
examples\n\n   #+begin_src python :results output :exports both\n
import re # import the module\n\n match = re.search(r'iiit','iiit
hyderabad is in India')\n print match.group()\n\n match =
re.search(r'iiit','iiit is in India. IIIT offers CS degrees too.')\n
print match.group()\n\n match = re.search(r'he','this is the eiffel
tower. The eiffel tower is in France.')\n print match.group()\n\n
#+end_src\n\n   #+results:\n   : iiit\n   : iiit\n   : he\n\n\n** Using
special characters\n\n*** The =^= and =$=\n\n#+begin_src python
:results output :exports both\n  import re\n  match =
re.search(r'^t123','this t123')\n  print match   # match is
None\n\n  match = re.search(r'^t123','t123 the')\n  print
match.group()\n\n  match = re.search(r't123$','this t123')\n  print
match.group()\n\n  match = re.search(r't123$','t123 the')\n  print
match   # match is None\n\n#+end_src\n\n#+results:\n: None\n
: t123\n: t123\n: None\n\n*** The =*= and =+=\n\n#+begin_src
python :results output :exports both\n  import re\n\n  match =
re.search(r'a*','red box in red light')\n  print match.group()#
Null String, not None\n\n  match = re.search(r'a+','red box in red
light')\n  print match# None\n\n  match =
re.search(r'a*','a red box in the red light')\n  print
match.group()\n#+end_src\n\n#+results:\n=\nNone\na\n=:\n:
None\n: a\n\n*** The =?= and =.=\n\n#+begin_src python :results
output :exports both\n  import re\n\n  match = re.search(r'a?','red
box in red light')\n  print match.group() #Null String, not
None\n\n  # pattern is ={'a'}\n  match = re.search(r'a.','red box
in red light')\n  print match # None\n\n  match =
re.search(r'a.','a red box in the red light')\n  print
match.group()\n#+end_src\n\n#+results:\n=\nNone\na \n=:\n:
None\n: a\n\n*** The =\\w, \\d, \\W= etc.\n\n#+begin_src python
:results output :exports both\n  import re\n\n  match =
re.search(r

Re: [O] AUCTeX conflicting with org-mode

[suvayu ali]

Hi Bastien,

On Tue, Mar 20, 2012 at 17:23, Bastien  wrote:
> Hi Suvayu,
>
> suvayu ali  writes:
>
>> I wanted to comment earlier but it slipped my mind, sorry about that.
>>
>> I am not sure if this patch is quite corect. It removes the let bind and
>> instead conditionally uses setq to bind it to t. From the docs I see the
>> variable becomes buffer local when set in any fashion, but does that
>> still mean it is okay to use setq?
>>
>> I can imagine in a complicated publishing project, an org file might
>> need to set the value to something. I suppose this will override any
>> such custom config. Is my analysis correct? It might be worth thinking
>> about before applying the patch.
>>
>> Is a conditional let binding possible, it might be the safer choice in
>> that case.
>
> I applied a patch into hotfix-7.8.06 using the let binding -- let me
> know if this works correctly.

I don't think this works. The problem (thanks to Nick again for the
analysis earlier in the thread[1] :-)) is the let bind happens before
tex.el is loaded. So when it is loaded eventually, the defvar fails
which in turn triggers the backtrace. The setq in the body works but
could possibly mess up someone's custom config as I mentioned in my
earlier post.

I hope you see the no-win situation now (:-p), hence my apprehension
about the fix earlier. That said, I guess you have two choices:

1. Leave the bug unsolved, hoping there will be a cleaner solution
   later. After all, there is a very simple workaround on the user side,
   do (load "tex.el") before using org-latex.
2. The second choice would be to partially fix the bug with the setq,
   but potentially break a future unsuspecting user with a non-standard
   config.

If it were up to me, I would probably prefer option one.

I hope this clears up everything.

Footnotes:

[1] 


-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] LaTeX export - can't skip a heading level

[Nick Dokos]

Achim Gratz  wrote:

> Nick Dokos  writes:
> > The latex exporter is very rigid about what it will accept: it wants the
> > levels to be in strict sequence. So this has to be chalked down as a
> > fairly deeply ingrained limitation of the exporter. I don't see an easy way
> > to lift it.
> 
> Especially as this is a limitation of LaTeX, not the exporter.
> 
> :-)
> 
> 

Not true - the following compiles with no problems:

--8<---cut here---start->8---
...
\begin{document}

\maketitle

\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}

\section{foo}
\label{sec-1}

\subsubsection{baz}
\label{sec-1-1-1}
\subsubsection{hunoz}
\label{sec-1-1-2}

\end{document}
--8<---cut here---end--->8---

Nick

Re: [O] org ELPA package 20120216 cannot be downloaded

[Bastien]

Christopher Schmidt  writes:

>> Probably a dead link or something alike...
>
> I think this is a GNU ELPA problem.  

Yes, probably.

The daily Org packages are here: http://orgmode.org/pkg/daily/

The last one was done on the 20th of March.

-- 
 Bastien

Re: [O] TODO items as part of an itemized list?

[Bastien]

Hi Richard,

Richard Stanton  writes:

> To save space in LaTeX exports and also to stop my TODO items being
> numbered, I'd like to have TODO items as part of a list, e.g.,
>
> - TODO Item 1
> - TODO Item 2
>
> However, while this prints OK, these entries are ignored by org-mode when
> I ask it to create a TODO list. Is there any way to do what I want?

No, because you are mixing to different things: lists and TODO items.

TODO items start with "*".

You can convert 

* TODO item 1
* TODO item 2

to a list by selecting the region they are in, then doing C-u C-c -

You can convert a list to TODO items with C-u C-c *

Best,

-- 
 Bastien

Re: [O] [DEV] New git workflow

[Bastien]

Hi Achim,

Achim Gratz  writes:

> Fair enough: a three-branch model with a release branch at the side of
> bugfixing and bleeding edge.

This is directly inspired from this: 
http://nvie.com/posts/a-successful-git-branching-model/

with some simplifications.

>> No.  All hotfix branches should merge into master regularily.  When
>> hotfix contains enough fixes for a bugfix release, then we merge it to
>> maint, and process with release.
>
> This is what I think is confusing: the bugfix branch (be it maint or any
> other) should always have the same _unless_ you want to track release
> specific bugfixes (which I don't think you do, but you tell me).  

I mostly want to track wrt-last-Emacs-merge specific bugs. 
I used the naming convention hotfix-* as suggested above because
I like the idea of deleting such a branch once we don't need it 
anymore (i.e. once a release has been done.)  Since hotfix-* role
is to contain fixes for severe bugs against the last production
version, their lifespan is not much (expect now, while we are 
testing this workflow, and while the forthcoming Emacs release
puts some heat on getting as much bugfixes committed to the
next 7.8.07 Org version.)

If we keep a persistent maint branch, I guess we will tend to
put all bugfixes there -- which I don't want.  But which could
make sense if those bugfixes are regularily merged back to Emacs
trunk.

>> My main goal is this: have a branch with one commit = one release.
>
> Why not name it release then and keep maint for fixes?  You could even
> install that release branch retro-actively if you want.  BTW, this also
> means you need to prepare the release on the hotfix branch, no
> fier-upper on the release allowed at all (since you would need to merge
> that back).

Indeed.  As for the names, I don't care, I just don't want to change
things that are just conventions.

> But as I said before, clone the repo, branch off the 7.7 release or so
> and re-trace the following releases via cherry-pick according to that
> new development model.  You will quickly learn if what you have to do
> feels right and if you commit to that model you will have practised the
> moves a few times already.

Good idea.  I will try.

> Another thing that I'd recommend is to not work on the public repo _at
> all_ and specifically never push to it, especially not automatically.
> The public repo should be "bare" (without a work tree) and any work on
> the server should use a clone of that repo, just like anyone else.  

Mhh.. something I don't get here: why should we not work on the public
repo?  This is the repo many people are cloning.

> If
> you prepare the releases on a fresh clone apart from the development
> clone, you have a stable base to work from and can nuke with no
> consequences if something goes wrong.  

(We prepare major releases on the development branch, minor ones on the
hotfix-* branch.)

> Git was designed to make merges
> easier, but they are hard and I still botch about every tenth that I try
> unless they are really trivial.  Once the release repo is finished, have
> it reviewed and then pull from it on the public repo.  The reason is
> that it is easy to push from the wrong branch onto the wrong target, but
> you really have to try to do that when pulling.  You can be more liberal
> with the normal development and bugfixing work on the development repo,
> but it would still be a good idea to have commits reviewed and signed
> off by another person before they are pulled into public.

Okay, I now understand the problem of pushing from the wrong repo ;)
Well, this is a trade-off.  If developers are willing to follow these
rules, okay.  But I don't feel like imposing them to everyone --
especially because paying a little more attention might be enough to
avoid the mess I did.

Again, thanks for sharing this.  

Let's continue with the model I suggest and see what is better and 
what should be fixed.

-- 
 Bastien

Re: [O] [DEV] New git workflow

[Bastien]

Bastien  writes:

> version, their lifespan is not much (expect now, while we are 
   ^^
   except
-- 
 Bastien

[O] org-enforce-todo-dependencies setting

[Bernt Hansen]

Hi Carsten,

Are the last three lines of the description for
org-enforce-todo-dependencies correct? 
--+

 |
,[ C-h v org-enforce-todo-dependencies RET ]
 |
| org-enforce-todo-dependencies is a variable defined in `org.el'.  
 |
| Its value is t
 |
|   
 |
| Documentation:
 |
| Non-nil means undone TODO entries will block switching the parent to DONE.
 |
| Also, if a parent has an :ORDERED: property, switching an entry to DONE will  
 |
| be blocked if any prior sibling is not yet done.  
 |
| Finally, if the parent is blocked because of ordered siblings of its own, 
 |
| the child will also be blocked.   
 |
| This variable needs to be set before org.el is loaded, and you need to   <--+ 
 |
| restart Emacs after a change to make the change effective.  The only way 
<--+-- HERE <-+
| to change is while Emacs is running is through the customize interface.  <--+
`

I set this variable with a setq in my .emacs long after loading org-mode
(uncompiled) and have never run into any issues with it.

,[ my .emacs lines 16-18 ]
| (add-to-list 'load-path (expand-file-name "~/git/org-mode/lisp"))
| (add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . 
org-mode))
| (require 'org-install)
`

,[ my .emacs line 1568 ]
| (setq org-enforce-todo-dependencies t)
`

>From the description it doesn't sound like my setup is supposed to work.

According to git you wrote this.

,[ git blame lisp/org.el ]
| 2949012f lisp/org.el (Carsten Dominik2009-02-01 23:49:03 +0100  2273) 
This variable needs to be set before org.el is loaded, and you need to
| 2949012f lisp/org.el (Carsten Dominik2009-02-01 23:49:03 +0100  2274) 
restart Emacs after a change to make the change effective.  The only way
| 2949012f lisp/org.el (Carsten Dominik2009-02-01 23:49:03 +0100  2275) to 
change is while Emacs is running is through the customize interface."
`

Thanks,
Bernt

Re: [O] org-enforce-todo-dependencies setting

[Nick Dokos]

Bernt Hansen  wrote:

> Hi Carsten,
> 
> Are the last three lines of the description for
> org-enforce-todo-dependencies correct? 
> --+
>   
>|
> ,[ C-h v org-enforce-todo-dependencies RET ]  
>|
> | org-enforce-todo-dependencies is a variable defined in `org.el'.
>|
> | Its value is t  
>|
> | 
>|
> | Documentation:  
>|
> | Non-nil means undone TODO entries will block switching the parent to DONE.  
>|
> | Also, if a parent has an :ORDERED: property, switching an entry to DONE 
> will   |
> | be blocked if any prior sibling is not yet done.
>|
> | Finally, if the parent is blocked because of ordered siblings of its own,   
>|
> | the child will also be blocked. 
>|
> | This variable needs to be set before org.el is loaded, and you need to   
> <--+  |
> | restart Emacs after a change to make the change effective.  The only way 
> <--+-- HERE <-+
> | to change is while Emacs is running is through the customize interface.  
> <--+
> `
> 
> I set this variable with a setq in my .emacs long after loading org-mode
> (uncompiled) and have never run into any issues with it.
> 
> ,[ my .emacs lines 16-18 ]
> | (add-to-list 'load-path (expand-file-name "~/git/org-mode/lisp"))
> | (add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . 
> org-mode))
> | (require 'org-install)
> `
> 
> ,[ my .emacs line 1568 ]
> | (setq org-enforce-todo-dependencies t)
> `
> 
> From the description it doesn't sound like my setup is supposed to work.
> 

Well, yes - but Carsten knew[fn:1] there'd be someone (we won't mention
names :-) ) who would do that and took care to do the
add-hook/remove-hook thingie while setting up the mode when you open an
org file: see line 5016ff in org.el. So it sounds a bit more ominous
than it actually is.

OTOH, if your .emacs opens an org file between lines 18 and 1568, all
bets are off.

Nick

Footnotes:

[fn:1] ... or maybe somebody did it and complained about it already: I
didn't search the ML.

Re: [O] org-enforce-todo-dependencies setting

[Nick Dokos]

Nick Dokos  wrote:


> [fn:1] ... or maybe somebody did it and complained about it already: I
> didn't search the ML.
> 

``git blame'' fingers commit c11a0b2d which indicates that there were indeed
complaints.

Nick

Re: [O] org-enforce-todo-dependencies setting

[Bernt Hansen]

Nick Dokos  writes:

> Nick Dokos  wrote:
>
>
>> [fn:1] ... or maybe somebody did it and complained about it already: I
>> didn't search the ML.
>> 
>
> ``git blame'' fingers commit c11a0b2d which indicates that there were indeed
> complaints.
>
> Nick

Yup - Thanks for the info!

Bernt

[O] org-log-note-headings 'state

[John J Foerch]

Hello,

I'm writing an extension for org-mode wherein it would be incredibly
convenient to be able to parse the state changes inside of LOGBOOK
drawers to get the state-names and timestamps.  However, I find that
state changes are currently only parsable in an ad hoc manner, as for
example by org-agenda-log-mode.  The docsting of org-log-note-headings
mentions this:

  "In fact, it is not a good idea to change the `state' entry, because
  agenda log mode depends on the format of these entries."

It is disappointing to me that the state entry of org-log-note-headings
is not safely user-configurable because of this.  Personally, I do like
to configure it to something a little cleaner and easier to read,
("State -> %s  %d").  (I haven't yet used org-agenda-log-mode, so haven't
run into the problems warned of in the docstring.)  If I were to do ad
hoc parsing of state changes in the mode I'm writing, I would have to
give up my local configuration of the state entry of org-log-note-headings.

These thoughts lead me to suggest that maybe org-log-note-headings is no
longer sufficient to its original purpose, because extensions wish to
parse state changes, but that blocks users from configuring the formats.
Perhaps it is time to replace it with something that guarantees ability
to parse.

Thoughts?

-- 
John Foerch

Re: [O] how to include graphics in pdf output

[Christopher W. Ryan]

Nick Dokos wrote:

Christopher W. Ryan  wrote:


I've attached a small org file that reproduces my problem with getting
images to export to pdf. I've also attached the resulting .tex file.

I think my issue may have something to do with my misunderstanding of
inline tasks, since if I put my org code for inclusion of the image
elsewhere in the org file, under its own 2nd level heading (2 stars)
then it exports fine. The narrative text in the attached org file
explains my observations in more detail.




#+OPTIONS:   todo:nil toc:nil tags:nil
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+LATEX_HEADER: \usepackage{graphicx}


* I guess I don't understand enough about Org's hierarchical trees yet

** Study design

Here's what we'll do.

As patients of home care agencies, the subjects will all be considered 
homebound by definition. Subjects with cognitive impairment or psychiatric 
illness sufficiently severe to make them unable to consent to the study will 
not be eligible.
** TODO notice how "end" on next line is expandable
** END
Somehow this text is under, hierarchically-speaking, the END statement of this 
inline task.

So it does not show up in the final pdf

** TODO there is text>>and the image file<<  inside "end"
** END

Neither does this paragraph.

Neither does this image, which must also be under the END statement of the 
inline task

#+CAPTION: Temperature and humidity data logger
#+LABEL:   datalogger
[[./DataLoggerImage.jpg]]

** But if I start a new 2-star heading

and put the image here, it works fine.

#+CAPTION: Temperature and humidity data logger
#+LABEL:   datalogger
[[./DataLoggerImage.jpg]]



What is the value of org-inlinetask-min-level? If it's the default 15,
then you just haven't formatted the inline tasks correctly (not enough
stars)- did you use C-c C-x t to insert them?  I used that to
insert the inline tasks and I got the following org file which exports
correctly afaict:

--8<---cut here---start->8---
#+OPTIONS:   todo:nil toc:nil tags:nil
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+LATEX_HEADER: \usepackage{graphicx}


* I guess I don't understand enough about Org's hierarchical trees yet

** Study design

Here's what we'll do.

As patients of home care agencies, the subjects will all be considered 
homebound by definition. Subjects with cognitive impairment or psychiatric 
illness sufficiently severe to make them unable to consent to the study will 
not be eligible.
*** TODO notice how "end" on next line is expandable
*** END
Somehow this text is under, hierarchically-speaking, the END statement of this 
inline task.

So it does not show up in the final pdf

*** TODO there is text>>and the image file<<  inside "end"
*** END
Neither does this paragraph.

Neither does this image, which must also be under the END statement of the 
inline task

#+CAPTION: foo
#+LABEL:   foo
[[./DataLoggerImage.jpg]]

** But if I start a new 2-star heading

and put the image here, it works fine.

#+CAPTION: bar
#+LABEL:   bar
[[./DataLoggerImage.jpg]]
--8<---cut here---end--->8---

Nick



Well, I'm making some progress.

org-inlinetask-min-level = 15

I had previousl simply typed in an arbitrary number of stars by hand, 
for my inline tasks. If I use C-c C-x t to insert one, then figures and 
text subsequent to it do appear in the final pdf as desired.  If I type 
in 15 stars by hand, emacs recognizes this also as an inline task 
(judging by the syntax highlighting) and figures following it are again 
exported correctly.


However, in both cases, the inline tasks themselves also appear in the 
final pdf. I was trying to avoid that, and I though todo:nil in 
#+OPTIONS would accomplish that objective, but it did not.  Is there a 
way to not export inline tasks?


Here are the modifications to the small reproducible file I started with:

#+OPTIONS:   todo:nil toc:nil tags:nil
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+LATEX_HEADER: \usepackage{graphicx}


* I guess I don't understand enough about Org's hierarchical trees yet

** Study design

Here's what we'll do.

Blah blah blah

*** TODO I'd like this not to appear in pdf
*** END
So now this text here appears in the pdf, as desired. But I'd like the 
inline task above not to appear in the pdf. I though todo:nil would 
prevent it from appearing, but it did not.



*** TODO figure will follow this todo
*** END
This line appears in the pdf too. Unfortunately, so does the inline task 
above it.


And the image shows up; its first appearance.


#+CAPTION: foo
#+LABEL:   foo
[[./DataLoggerImage.jpg]]

** But if I start a new 2-star heading

and put the image here, it works fine.  Second appearance of the image.

#+CAPTION: bar
#+LABEL:   bar
[[./DataLoggerImage.jpg]]


*** TODO entered via C-c C-x t
*** END

**

Re: [O] org-enforce-todo-dependencies setting

[Carsten Dominik]

On 21.3.2012, at 03:00, Nick Dokos wrote:

> Bernt Hansen  wrote:
> 
>> Hi Carsten,
>> 
>> Are the last three lines of the description for
>> org-enforce-todo-dependencies correct? 
>> --+
>>  
>>|
>> ,[ C-h v org-enforce-todo-dependencies RET ] 
>> |
>> | org-enforce-todo-dependencies is a variable defined in `org.el'.   
>> |
>> | Its value is t 
>> |
>> |
>> |
>> | Documentation: 
>> |
>> | Non-nil means undone TODO entries will block switching the parent to DONE. 
>> |
>> | Also, if a parent has an :ORDERED: property, switching an entry to DONE 
>> will   |
>> | be blocked if any prior sibling is not yet done.   
>> |
>> | Finally, if the parent is blocked because of ordered siblings of its own,  
>> |
>> | the child will also be blocked.
>> |
>> | This variable needs to be set before org.el is loaded, and you need to   
>> <--+  |
>> | restart Emacs after a change to make the change effective.  The only way 
>> <--+-- HERE <-+
>> | to change is while Emacs is running is through the customize interface.  
>> <--+
>> `
>> 
>> I set this variable with a setq in my .emacs long after loading org-mode
>> (uncompiled) and have never run into any issues with it.
>> 
>> ,[ my .emacs lines 16-18 ]
>> | (add-to-list 'load-path (expand-file-name "~/git/org-mode/lisp"))
>> | (add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . 
>> org-mode))
>> | (require 'org-install)
>> `
>> 
>> ,[ my .emacs line 1568 ]
>> | (setq org-enforce-todo-dependencies t)
>> `
>> 
>> From the description it doesn't sound like my setup is supposed to work.
>> 
> 
> Well, yes - but Carsten knew[fn:1] there'd be someone (we won't mention
> names :-) ) who would do that and took care to do the
> add-hook/remove-hook thingie while setting up the mode when you open an
> org file: see line 5016ff in org.el. So it sounds a bit more ominous
> than it actually is.
> 
> OTOH, if your .emacs opens an org file between lines 18 and 1568, all
> bets are off.
> 
> Nick
> 
> Footnotes:
> 
> [fn:1] ... or maybe somebody did it and complained about it already: I
> didn't search the ML.

I had forgotten all about this, but indeed, the hook makes sure
things are OK, so the sentence could be removed from the
docstring.

- Carsten

Re: [O] AUCTeX conflicting with org-mode

[Yagnesh Raghava Yakkala]

Hi Bastien and Suvayu,

suvayu ali  writes:
>
[snipped 35 lines]
>
> 1. Leave the bug unsolved, hoping there will be a cleaner solution
>later. After all, there is a very simple workaround on the user side,
>do (load "tex.el") before using org-latex.

how about this patch (to hotfix branch). 

diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 2e11ca4..438e5a4 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -871,6 +871,7 @@ when PUB-DIR is set, use this as the publishing directory."
 		 filename)))
 	 (auto-insert nil); Avoid any auto-insert stuff for the new file
 	 (TeX-master (boundp 'TeX-master))
+	 (dummy (unless TeX-master (makunbound 'TeX-master))) ; make sure we are not introducing TeX-master
 	 (buffer (if to-buffer
 		 (cond
 		  ((eq to-buffer 'string) (get-buffer-create

-- 
YYR