[O] Wishlist: LaTeX export: automatically append backslash to "." unless at end of sentence

[Andras Major]

Hi,

in TeX and LaTeX, the width of the glue (blank space) after a "." can
be one of two different values, depending on the context.  There is
always a longer space between sentences than after a "." that doesn't
mark the end of a sentence (abbreviations, dates, etc.).  Since
TeX/LaTeX usually can't recognize the latter case by itself, one can
help out by writing ".\ " or ".~" explicitly to enforce a short space.
Without these hints, printed output will look typographically wrong.

Org-mode export doesn't allow me to easily include these hints without
affecting readability and export to other formats.  Therefore I ask
that LaTeX export places ". " or ".\ " in the output automatically
depending on the context:

- If, in the source, the "." precedes a double space " " or a newline,
  use ". ".

- In any other case, use ".\ ".

The reason this would work is the Emacs convention of writing ASCII
such that there is at least one more space (at least two) between
sentences.  I believe that the Emacs fill-* functions also make use of
this convention.

Thanks,

  András

[O] Missing Mobile TODO questions

[Iain Houston]

I'd be very grateful for some help setting up Mobile Org.

This is what I have defined right now:

(setq org-mobile-directory "/Volumes/iainhouston/org")

(setq org-agenda-files 
  (list "~/Documents/org/gtd.org" 
;; more to add
)
)

These are my issues:

1. When I push, no Agenda file is created as document says it should
The generated index.org links to agendas.org but no such file has been created 
even though I have an agenda after C-c a a l

3. Linked files are not copied as described in the Mobile Org webpage for 
sync-ing
in gtd.org I have:
[[file:~/Documents/org/maybe.org][Someday / Maybe tasks]]
which is ignored when pushed but is a valid link in emacs.

4. Missing TODO states
In emacs I can cycle through my TODO states:

(setq org-todo-keywords
   '((sequence "TODO" "MAYBE" "WAITING" "NEXT" "|" "DONE" "ABANDONED"))
)

but when sync'd with MobileOrg my TODO items are reported as having a TODO 
state of "none" with only the option to move to "DONEARCHIVE" state or the 

[O] Bug: babel: results switch (output vs. value) has no or wrong effect for sh source block [7.7 (release_7.7.107.g7a82)]

[Andras Major]

Hello, here is an example of apparently erroneous behaviour of the
:results switch.  In this example, we use an sh block, but it also
appears to affect other languages (will need more investigation).

Example Org code:

#+begin_src sh :exports output
  echo "Hello World 1"
#+end_src

#+results:
: Hello World 1

#+begin_src sh :exports value
  echo "Hello World 2"
#+end_src

#+results:
: Hello World 2

Am I missing something here or should the second instance really
output something like an integer exit value from echo?

Cheers,

  András


Emacs  : GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
 of 2010-12-11 on raven, modified by Debian
Package: Org-mode version 7.7 (release_7.7.107.g7a82)

current state:
==
(setq
 org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
 org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
 org-babel-load-languages '((asymptote . t) (ditaa . t) (dot . t)
(gnuplot . t) (haskell . t) (latex . t)
(octave . t) (R . t) (ruby . t) (scheme . t) (sh . 
t))
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-babel-tangle-lang-exts '(("ruby" . "rb") ("latex" . "tex")
("haskell" . "hs") ("asymptote" . "asy")
  ("emacs-lisp" . "el"))
 org-export-blocks-postblock-hook '(org-exp-res/src-name-cleanup)
 org-export-latex-format-toc-function 'org-export-latex-format-toc-default
 org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
  org-babel-hide-result-toggle-maybe)
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
 org-confirm-shell-link-function 'yes-or-no-p
 org-export-first-hook '(org-beamer-initialize-open-trackers)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-cycle-hook '(org-cycle-hide-archived-subtrees
org-cycle-hide-drawers org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
 org-export-preprocess-before-normalizing-links-hook
'(org-remove-file-link-modifiers)
 org-mode-hook '(#[nil "\300\301\302\303\304$\207"
   [org-add-hook change-major-mode-hook org-show-block-all 
append local] 5]
 #[nil "\300\301\302\303\304$\207"
   [org-add-hook change-major-mode-hook 
org-babel-show-result-all
append local] 5]
 org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
org-babel-execute-safely-maybe)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-export-interblocks '((lob org-babel-exp-lob-one-liners) (src
org-babel-exp-inline-src-blocks))
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 org-occur-hook '(org-first-headline-recenter)
 org-from-is-user-regexp nil
 org-export-preprocess-before-selecting-backend-code-hook
'(org-beamer-select-beamer-code)
 org-confirm-babel-evaluate nil
 org-export-latex-final-hook '(org-beamer-amend-header
org-beamer-fix-toc org-beamer-auto-fragile-frames
   org-beamer-place-default-actions-for-lists)
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-export-blocks '((src org-babel-exp-src-block nil) (comment
org-export-blocks-format-comment t)
 (ditaa org-export-blocks-format-ditaa nil) (dot
org-export-blocks-format-dot nil))
 )

Re: [O] bug: org-mouse broken

[Samuel Wales]

On headlines without todo kw, tries to follow link.  Should cycle.

On 2011-08-18, Samuel Wales  wrote:
> mouse-1 on stars says "no link" sometimes instead of cycling.
>
> Maybe it is a regexp issue.
>
> git bisect:
>
> 628ebf04f74afa8694945386c507bde06c3aac9e is the first bad commit
> commit 628ebf04f74afa8694945386c507bde06c3aac9e
> Author: Nicolas Goaziou 
> Date:   Mon Jul 25 17:50:28 2011 +0200
>
> Enforce white space after todo keywords
>
> * lisp/org.el (org-set-regexps-and-options): enforce white space after
>   todo keyword, as word boundary isn't sufficient (i.e. in matches
> * TODO/this)
>
> :04 04 9786e7018273d86a894aecabac265e46429c233c
> ef1ffd65a9c8efa918dedfe5c157f0f1ef835923 Mlisp
>
> I can't provide more at present, but thuoght this might help.
>
> Samuel
>
> --
> The Kafka Pandemic: http://thekafkapandemic.blogspot.com
> I support the Whittemore-Peterson Institute (WPI)
> ===
> Bigotry against people with serious diseases is still bigotry.
>


-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
I support the Whittemore-Peterson Institute (WPI)
===
Bigotry against people with serious diseases is still bigotry.

[O] bug: org-mouse broken

[Samuel Wales]

mouse-1 on stars says "no link" sometimes instead of cycling.

Maybe it is a regexp issue.

git bisect:

628ebf04f74afa8694945386c507bde06c3aac9e is the first bad commit
commit 628ebf04f74afa8694945386c507bde06c3aac9e
Author: Nicolas Goaziou 
Date:   Mon Jul 25 17:50:28 2011 +0200

Enforce white space after todo keywords

* lisp/org.el (org-set-regexps-and-options): enforce white space after
  todo keyword, as word boundary isn't sufficient (i.e. in matches
* TODO/this)

:04 04 9786e7018273d86a894aecabac265e46429c233c
ef1ffd65a9c8efa918dedfe5c157f0f1ef835923 M  lisp

I can't provide more at present, but thuoght this might help.

Samuel

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
I support the Whittemore-Peterson Institute (WPI)
===
Bigotry against people with serious diseases is still bigotry.

Re: [O] [odt] htmlfontify + Support for src blockfontification

[suvayu ali]

On Thu, Aug 18, 2011 at 10:55 PM, Jambunathan K  wrote:
>>  Any user can add download the modified htmlfontify.el if he ever
>> wants to achieve fonitification of source blocks in the odt file.
>
> If anyone is interested in fontification support they can drop a private
> mail to me. I will be happy to share the modified htmlfontify.el.
>

Worg might be a nice place. :)

> Jambunathan K.



-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] backend specific preprocess hook

[suvayu ali]

Hi Bastien,

On Thu, Aug 18, 2011 at 7:17 PM, Bastien  wrote:
>> [1] IIUC I have to customise the `org-export-preprocess-hook'?
>
> Yes, and test against `org-export-current-backend' to see whether you
> are exporting to HTML or LaTeX.

I have this working now. Works great. I should have reported back with
my solution:


(defun my-org-export-preprocess-hook ()
  "My backend specific export preprocess hook."
  (save-excursion
(if (eq org-export-current-backend 'latex)
(let* ((tag "ignoreheading")) ; Thanks to Nick for this
  (org-map-entries (lambda ()
 (delete-region (point-at-bol) (point-at-eol)))
   (concat ":" tag ":"
(if (eq org-export-current-backend 'html)
(let* ((match "Qn"))
  (org-map-entries (lambda ()
 (org-set-property "HTML_CONTAINER_CLASS"
   "question"))
   match)

(add-hook 'org-export-preprocess-hook 'my-org-export-preprocess-hook)


The html customisation is incomplete for the moment (for the lack of
time :-p). My goal is to have custom styles for headlines tagged with
"Qn" (unanswered questions) and "QnA" (questions with complete
answers).

Actually I was also hoping to colour code my latex export based on a
similar philosophy using \todo[inline] and PROPERTIES. But I haven't
had the time to investigate the possibilities yet. I will put it on
Worg if I do manage to figure it out. :)

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] missing todo's in agenda after emacs/org upgrade

[suvayu ali]

Hi Peter,

On Thu, Aug 18, 2011 at 7:41 PM,   wrote:
> So I believe the TODO items are formatted `according to spec’ :-).
> E.g., “** TODO Fix the daily agenda view”.

I don't think the present version of org will show an entry in the
agenda unless you have an active timestamp. To give you an example:


* TODO Plumber to fix leak
  <2011-08-04 Thu>

* TODO RooStats tutorial
  SCHEDULED: <2011-01-25 Tue 09:00>

* TODO Analysis deadline
  DEADLINE: <2011-08-19 Fri 15:00>

* TODO Read Dune
  The above 3 entries show up in the agenda, but this one doesn't.


Actually to show up in the agenda, the TODO keyword is not necessary. It
depends solely on the timestamp and you get reminders based on whether
its a regular timestamp, SCHEDULED timestamp or a DEADLINE.

I hope this helps. If you still have issues, please follow what Seb
suggested and post a minimal example which demonstrates the behaviour
you describe.

GL

-- 
Suvayu

Open source is the future. It sets us free.

[O] Highlight TODO keywords when using dash as bulletpoint

[Marcelo de Moraes Serpa]

Hi list,

I'd like to know if it's possible to highlight the TODO keywords when using
dash " - " as the bulletpoint for items. Example:

- TODO An item
  - BRAINSTORM another item

These are not matched as TODO keywords by org. Is there a way to setup org
to do that?

Thanks in advance,

- Marcelo.

Re: [O] Closing brace with LaTeX export

[Dr. Adrian Wrigley]

Ista Zahn wrote:

Hi,
Probably the best thing to do is update to the latest version of
org-mode, in which this works even with line breaks.


Thanks!  Works brilliantly now!
(thanks to Thomas S. Dye too)

I was using Debian Squeeze, which has the 6.33 by default.
--
Adrian

[O] [error] Capture template `m': number-or-marker-p

[Sebastien Vauban]

Hello,

With the update of 20 mins ago or so, that is [2011-08-18 Thu 23:00] (CET),
I've got the following error when trying to use a capture template I use many
times every day.

--8<---cut here---start->8---
Debugger entered--Lisp error: (error "Capture template `m': number-or-marker-p")
  signal(error ("Capture template `m': number-or-marker-p"))
  error("Capture template `%s': %s" "m" number-or-marker-p)
  (condition-case error (org-capture-place-template) ((error quit) (if ... ...) 
(set-window-configuration ...) (error "Capture template `%s': %s" ... ...)))
  (if (equal goto 0) (org-capture-insert-template-here) (condition-case error 
(org-capture-place-template) (... ... ... ...)) (if (and ... ...) 
(condition-case nil ... ...)) (if (org-capture-get :immediate-finish) 
(org-capture-finalize nil)))
  (cond ((equal entry "C") (customize-variable ...)) ((equal entry "q") (error 
"Abort")) (t (org-capture-set-plist entry) (org-capture-get-template) 
(org-capture-put :original-buffer orig-buf :original-file ... 
:original-file-nondirectory ... :annotation annotation :initial initial) 
(org-capture-put :default-time ...) (org-capture-set-target-location) 
(condition-case error ... ...) (setq org-capture-clock-keep ...) (if ... ... 
... ... ...)))
  (let* ((orig-buf ...) (annotation ...) (initial ...) (entry ...)) (when 
(stringp initial) (remove-text-properties 0 ... ... initial)) (when (stringp 
annotation) (remove-text-properties 0 ... ... annotation)) (cond (... ...) (... 
...) (t ... ... ... ... ... ... ... ...)))
  (cond ((equal goto ...) (org-capture-goto-target)) ((equal goto ...) 
(org-capture-goto-last-stored)) (t (let* ... ... ... ...)))
  org-capture(nil)
  call-interactively(org-capture nil nil)
--8<---cut here---end--->8---

FYI, the capture template in question:

#+begin_src emacs-lisp
  (setq org-capture-templates
`(("m" "Mail" entry
   (file+headline ,org-default-notes-file "Tasks")
   "* TODO %:subject%? (from %:fromname) :mail:
   SCHEDULED: %t
   %:date-timestamp-inactive

#+begin_verse
%i
#+end_verse

>From %a"
   :empty-lines 1 :immediate-finish)))
#+end_src

Best regards,
  Seb

PS- BTW, I still don't understand how to get real data instead of those
useless ellipses in the above stack trace.

I've the following in my .emacs file, but it clearly seems without any
effect!??

#+begin_src emacs-lisp
  ;; maximum depth of lists to print in the result of the evaluation 
commands
  ;; before abbreviating them: no limit
  (setq eval-expression-print-level nil)

  ;; maximum length of lists to print in the result of the evaluation 
commands
  ;; before abbreviating them: no limit
  (setq eval-expression-print-length nil)
#+end_src

-- 
Sebastien Vauban

Re: [O] missing todo's in agenda after emacs/org upgrade

[Sebastien Vauban]

Hi Peter and Puneeth,

Puneeth Chaganti wrote:
> On Thu, Aug 18, 2011 at 11:11 PM,   wrote:
>> Hi Suvayu,
>>
>> On 18 Aug 2011, at 18:44, suvayu ali wrote:
>>
>>> It might be helpful to know how your TODO entries are formatted. Maybe
>>> its not the setup, but how the agenda files are formatted that was
>>> causing the issue?
>>>
>>> In any case, good to hear it is resolved now.
>>
>> That’s the problem, the issue is *not* resolved… the todo items show up in
>> the global todo list, but still not in the daily agenda view.
>
> As far as I understand, this has been changed. Agenda view doesn't
> show the TODO list anymore, by default.  Look at the following commit
> for details.

Are we talking of SCHEDULED TODO's or not?

Peter, can you provide a minimal but complete example of what are your source
files, and your current vs expected agenda view?

Just one or two items should be sufficient to express your point, and let
people really understand your problem. I mean, I'm not totally sure to
understand the real problem you experience.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] missing todo's in agenda after emacs/org upgrade

[Puneeth Chaganti]

On Thu, Aug 18, 2011 at 11:11 PM,   wrote:
> Hi Suvayu,
>
> On 18 Aug 2011, at 18:44, suvayu ali wrote:
>
>> It might be helpful to know how your TODO entries are formatted. Maybe
>> its not the setup, but how the agenda files are formatted that was
>> causing the issue?
>>
>> In any case, good to hear it is resolved now.
>
> That’s the problem, the issue is *not* resolved… the todo items show up in 
> the global todo list, but still not in the daily agenda view.

As far as I understand, this has been changed. Agenda view doesn't
show the TODO list anymore, by default.  Look at the following commit
for details.

--
commit 770c2ddfba5c173d1b33e7b247b49a8188994f76
Author: Bernt Hansen 
Date:   Tue Apr 5 01:05:43 2011 +

Remove obsolete functionality to add todo list in front of agenda

* lisp/org-agenda.el: Remove obsolete code for adding todo list in front
of the agenda

Todo lists should be built with the TODO list or a block agenda instead.

This code was triggered for C-u R in block agendas which is used to
limit the clock report to the current tags filter applied to the
agenda.


HTH,
Puneeth

Re: [O] how to include effort in agenda prefix?

[Sebastien Vauban]

Hi,

Michael C Gilbert wrote:
> On Aug 17, 2011, at 9:17 PM, Max Mikhanosha wrote:
>
>> Use %e format for effort. If it gives you an error you need newer
>> org-mode, as the patch to fix %e format only got applied recently.
>
> I do try to keep current, but apparently I missed that! I see it in the
> docstring, but I don't see its usage explained (in the docstring or in the
> manual). Am I overlooking it?

I confirm the explanation is missing from the doc.

> Thank you, regardless — exactly what I needed.

This is to be used with caution: I had put it in my config file, used by other
Org users, and they experienced immediately an "out-of-args" error, inhibiting
them forever to access the agenda from that point in time.

Cause: they use the stable 7.7, hence do not have that feature accessible.

Though, is there a way to make a unknown format specifier have less
problematic impact on users?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] [odt] htmlfontify + Support for src blockfontification

[Jambunathan K]

>  Any user can add download the modified htmlfontify.el if he ever
> wants to achieve fonitification of source blocks in the odt file.

If anyone is interested in fontification support they can drop a private
mail to me. I will be happy to share the modified htmlfontify.el.

Jambunathan K.

-- 

Re: [O] Bug: Extra space inserted in repeated tasks' date line

[Sebastien Vauban]

Hi Bastien,

Bastien wrote:
> "Sebastien Vauban"  writes:
>
>> ** This one won't be moved along with the heading
>>   SCHEDULED: <2011-08-18 Thu>
>>
>> Because of this text here...
>
> This should be fixed now.  "Meta" lines (SCHEDULED string, etc, 
> along with the first properties drawer) will be indented correctly,
> even when text from the subtree start at the beginning of the line.
>
> Please confirm this works okay for you, and thanks for reporting 
> this!

This works in many cases, but suffers some problems. Anyway, you're really not
far from giving this a definitive solution[1].

Here a compilation of cases which don't work, or work with an error being
generated in the echo area.

--8<---cut here---start->8---
* New section

The first one works, but generates an error ("setq: Wrong type argument:
number-or-marker-p, nil").

** The SCHED will be moved
   SCHEDULED: <2011-08-18 Thu>

** This one now move as well along with the heading
   SCHEDULED: <2011-08-18 Thu>

Even with this text here... but error is also generated.

Same for the following: works, with error.

** RDV client
   DEADLINE: <2011-09-06 Tue 08:30-09:15>

** Feestje Iris
   <2011-08-14 Sun 18:30>

Demoting this one does not move the active timestamp, but moves the SCHEDULED
line of the next entry.

** TODO Bi-weekly review
   SCHEDULED: <2011-08-12 Fri ++14d>
   :PROPERTIES:
   :RESET_CHECK_BOXES: t:
   :LAST_REPEAT: [2009-07-28 Tue 21:19]
   :END:

Here, the properties aren't moved. The rest well.
--8<---cut here---end--->8---

Thank you so much for patching this. It will save me tens of minutes per
month, and an RSI because of adding them manually? ;-)

Best regards,
  Seb

Footnotes:

[1] I've been sure for months that this worked before (like some half year
ago), but never tried on such a vintage version. Anyway, Carsten told me I
was wrong...

-- 
Sebastien Vauban

Re: [O] org-icons package

[Dan Davison]

Hi Renzo,

org-icons needs to be moved into contrib/, hooked in via a lightweight patch
against org.el, instead of being implemented as a monolithic change to
org.el. I made a start on that in this branch:

https://github.com/dandavison/org-devel/tree/org-icons

but I'm not sure that I got very far. Note that that is a branch in a clone
of the org repo, as opposed to the org-icons repos which are standalone
repos and do not contain org.

I thought org-icons was interesting because it offers the possibility of
allowing users to make arbitrary superficial changes to org aesthetics. For
example, the #+begin_src...#+end_src boilerplate is rather heavy for some
peoples' tastes. At one point I had it replacing that with a little (ruby,
snake) for (ruby, python) code... But I think it also allows the possibility
of overlaying with text. I'd be happy to give you push access to that repo,
but, you may as well just fork it as I have no plans to work on it.

I don't know how to contact Nicolas. I believe that he is on record as
saying he did not plan to develop org-icons further.

Good luck,

Dan

On Thu, Aug 18, 2011 at 1:13 PM, Renzo Been  wrote:

> Hi Dan, Nicolas and list,
>
> In my previous mail I wrote about using (and upgrading it for use with the
> latest version of org-mode) Nicolas Girard's org-icons package, see:
> http://news.gmane.org/find-root.php?group=gmane.emacs.orgmode&article=44834
>
> I've tried to contact Nicolas Girard (via e-mail and a google search). But
> I
> have not heard back from him as yet.
>
> When I checked the github for org-icons again I discovered that there was a
> second branch by Dan Davison.
> https://github.com/ngirard/org-icons/tree/dan
>
> Dan,
>
> Do you know how I can get in contact with Nicolas? Or do you have access to
> the github for org-icons, so that it's code can be updated to work with the
> latest version of org-mode? Did you and Nicolas ever think about including
> org-icons into org-mode?
>
> As for me, I'm happily using org-icons with org-mode 7.7, I've attached a
> new
> and updated patch file that works on the latest org.el
>
> Copy the patch "org-icons.patch" to the directory where you keep your
> "org.el"
> cd to that directory
> And then apply the patch like this:
> patch -b org.el org-icons.patch
>
> Of-course, if neither of you has the time to work on org-icons... I could
> make
> a fork of the git repo, and make the changes myself. However, I do not have
> much elisp knowledge...
>
> Ciao,
> Renzo
>
> On 25 July 2011 12:12, Renzo Been  wrote:
> > Bastien  altern.org> writes:
>
> >> Hi Philipp,
>
> >> Philipp Haselwarter  gmx.de> writes:
>
> >> > Is there any particular reason for it to be hardcoded? Apart from the
> >> > fact that /well it just is this way right now/ I mean.
>
> >> Nothing carved in stone, but here are the two reasons I see:
>
> >> - we don't want users to use arbitrary regexp to match headlines as they
> >>   are very likely to shoot themselves in the foot (Harven's example of
> >>   using "-" instead of "*" is a good example of that.)
>
> >> - Given this, I am not able to imagine a good way of limiting the number
> >>   of allowed characters.
>
> >> > That'd be useful information for anyone interested in changing it.
>
> >> I'd interested in any solution to the problems above.
>
> >> > Then
> >> > you can still just tell them to write a patch if they care that much
> >> > ('cause even in org-mode-land patches don't write themselves just yet)
>
> >> :)
>
> >> > [I just had the most awesome idea for a feature request].
>
> >> Please share!
>
> >> > If it's "just" about inheriting from a variable in some 300 places it
> >> > could at least be discussed.
>
> >> Yep -- if you have the energy to go through the code and see where it is
> >> hardcoded while it should not, please do.
>
> >> Thanks,
>
> > Hi,
>
> > I was just thinking... If you want to change the "look" of the
> > org-headlines. Does one really need to change the code?
>
> > I have been using Nicolas Girard's org-icons package for quite a while.
> And
> > that makes org-buffers look pretty nice. You can even customise the
> icons, to
> > make it look the way you want.
>
> > However, some things about the org-icons package... It seems to be a
> little
> > outdated.  Are there many org-moders out there still using it?  Were
> there
> > ever any plans to include it in the org-distribution? Right now it needs
> to be
> > installed by hand, because the patch to org.el is outdated...  Also, I
> need to
> > load it two times in my .emacs before the icons work...
>
> > Ciao,
> > Renzo
>
> > The org-icons can be found here:
> > Download from Nicolas Girard's github
> > http://github.com/ngirard/org-icons
> > On the Worg site I could only find screenshots, no other information...
> > http://orgmode.org/worg/org-screenshots.html
> > The list-message announcement for org-icons
> >
> http://news.gmane.org/find-root.php?message_id=%3c87zl2962um.fsf%40stats.ox.ac.uk%3e
> > And some list-messag

Re: [O] Attachments and refiling

[Darlan Cavalcante Moreira]

Hello Bastien,
I'm glad to help (even if such a small contribution).

The downside of this hack is that it does not work when you export the
buffer. If you use the file: link type then the link will works when you
export the org buffer, but you have to type the whole path of the attached
file. Therefore, there is this trade-off for now.

There is probably a way to make the attach link type also work when
exporting the org buffer, but since I don't need this right now I didn't
search how to do it.

--
Darlan

At Thu, 18 Aug 2011 19:33:37 +0200,
Bastien  wrote:
> 
> Hi Darlan,
> 
> Darlan Cavalcante Moreira  writes:
> 
> > I requested this some time ago [1]. While there is not a built-in attach
> > link type, org provides you with ways to easily create this functionality.
> >
> > In the setup part in my org-files I put
> > #+LINK: attach elisp:(org-open-file (org-attach-expand "%s"))
> >
> > Now I can use the "attach" link type, but org will ask me if I want to
> > allow executing the elisp code. To avoid this you can even set
> > org-confirm-elisp-link-function to nil (I don't like this because it allows
> > any elisp code in links) or you can set org-confirm-elisp-link-not-regexp
> > appropriately.
> >
> > In my case I use
> > : (setq org-confirm-elisp-link-not-regexp "org-open-file")
> >
> > This works very well.
> 
> This is a nice and useful hack -- I added it to Worg/org-hacks.org.
> 
> Thanks!
> 
> -- 
>  Bastien

Re: [O] [odt] htmlfontify + Support for src blockfontification

[Achim Gratz]

> [1] This is more of a backup strategy than anything else. You can delete
> the patches from the patchwork server if you want to.

Your fork on repo.or.cz just needs another branch and you're good to
go... no need to commit this to master and easily within reach.


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

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [O] [odt] htmlfontify + Support for src blockfontification

[Jambunathan K]

>> Till such time as this patch is integrated in to official Emacs, I
>> would like to check-in a copy of htmlfontify.el into the contrib
>> dir. Will there any objection to this?
>
> Yes.  We must avoid duplicate code as much as possible, especially
> when the code lives in Elisp libraries that have the same name.

I still need a way to save the changes. All I was asking for is some
temporary storage space.

I will be quickly following up this mail with a series of patches [1]to
htmlfontify.el and htmlfontify.el in it's final form. Any user can add
download the modified htmlfontify.el if he ever wants to achieve
fonitification of source blocks in the odt file.  

Jambunathan K.

Footnotes: 

[1] This is more of a backup strategy than anything else. You can delete
the patches from the patchwork server if you want to.

Re: [O] Closing brace with LaTeX export

[Thomas S. Dye]

Aloha Adrian Wrigley,

Version 6.33 is out of date.  It would likely help to upgrade your
Org-mode installation if possible.

All the best,
Tom

"Dr. Adrian Wrigley"  writes:

> Hi people!
>
> I've just started using Org mode (6.33x).  A fabulous tool.  But I have a 
> problem
> exporting TeX such as this:
>
> SAMPLE
> I want to emphasise \emph{these three words} only.
> --END-
>
> when this is exported, the closing brace is erroneously escaped with a 
> backslash "\".
> It works fine without the spaces in the \emph section.
>
> The closest discussion on the topic is here:
> https://lists.gnu.org/archive/html/emacs-orgmode/2009-04/msg00427.html
> but unlike Scot, I find even keeping the text on one line doesn't work.
>
> I would like to pass multi-line arguments, with spaces in braces.
> I don't think it works to put use a #+BEGIN_LaTeX block for
> every argument, since that seems to confuse things and is very verbose.
>
> What's the best way of doing this?
>
> Thanks for your time!
> --
> Dr. Adrian Wrigley.
>
>

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

Re: [O] Closing brace with LaTeX export

[Ista Zahn]

Hi,
Probably the best thing to do is update to the latest version of
org-mode, in which this works even with line breaks.

best,
Ista

On Wed, Aug 17, 2011 at 6:40 PM, Dr. Adrian Wrigley
 wrote:
> Hi people!
>
> I've just started using Org mode (6.33x).  A fabulous tool.  But I have a
> problem
> exporting TeX such as this:
>
> SAMPLE
> I want to emphasise \emph{these three words} only.
> --END-
>
> when this is exported, the closing brace is erroneously escaped with a
> backslash "\".
> It works fine without the spaces in the \emph section.
>
> The closest discussion on the topic is here:
> https://lists.gnu.org/archive/html/emacs-orgmode/2009-04/msg00427.html
> but unlike Scot, I find even keeping the text on one line doesn't work.
>
> I would like to pass multi-line arguments, with spaces in braces.
> I don't think it works to put use a #+BEGIN_LaTeX block for
> every argument, since that seems to confuse things and is very verbose.
>
> What's the best way of doing this?
>
> Thanks for your time!
> --
> Dr. Adrian Wrigley.
>
>



-- 
Ista Zahn
Graduate student
University of Rochester
Department of Clinical and Social Psychology
http://yourpsyche.org

Re: [O] Keeping an eye on byte-compilation warnings

[Achim Gratz]

Bastien  writes:
> Thanks for the heads up.  I'll be more careful about this.

In org-fixup-indentation:
org.el:7368:32:Warning: reference to free variable `org-property-end-re'

In org-set-property:
org.el:14316:34:Warning: reference to free variable `fn'


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

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

[O] Closing brace with LaTeX export

[Dr. Adrian Wrigley]

Hi people!

I've just started using Org mode (6.33x).  A fabulous tool.  But I have a 
problem
exporting TeX such as this:

SAMPLE
I want to emphasise \emph{these three words} only.
--END-

when this is exported, the closing brace is erroneously escaped with a backslash 
"\".
It works fine without the spaces in the \emph section.

The closest discussion on the topic is here:
https://lists.gnu.org/archive/html/emacs-orgmode/2009-04/msg00427.html
but unlike Scot, I find even keeping the text on one line doesn't work.

I would like to pass multi-line arguments, with spaces in braces.
I don't think it works to put use a #+BEGIN_LaTeX block for
every argument, since that seems to confuse things and is very verbose.

What's the best way of doing this?

Thanks for your time!
--
Dr. Adrian Wrigley.

Re: [O] xemacs error when calling org-install

[Bastien]

Hi Michael,

good to know that you are still watching after Org's compatibility 
with XEmacs :)

Michael Sperber  writes:

> I'm definitely using XEmacs with org-mode, but I usually lag behind a
> little bit.  The problem you're citing seems to be gone, but there are
> still a number of nits XEmacs runs into when trying to run the current
> org-mode.  I'm testing my current set of patches, which I'll submit as
> soon as things work satisfactorily.  Let me know if you want them in
> advance.

No hurry.  Please send the changes when they are complete.

Thanks again,

-- 
 Bastien

Re: [O] how to include effort in agenda prefix?

[Michael C Gilbert]

On Aug 17, 2011, at 9:17 PM, Max Mikhanosha wrote:

> Use %e format for effort. If it gives you an error you need newer
> org-mode, as the patch to fix %e format only got applied recently.

I do try to keep current, but apparently I missed that! I see it in the 
docstring, but I don't see its usage explained (in the docstring or in the 
manual). Am I overlooking it?

Thank you, regardless — exactly what I needed.

— Michael

Re: [O] missing todo's in agenda after emacs/org upgrade

[peter . frings]

Hi Suvayu,

On 18 Aug 2011, at 18:44, suvayu ali wrote:

> It might be helpful to know how your TODO entries are formatted. Maybe
> its not the setup, but how the agenda files are formatted that was
> causing the issue?
> 
> In any case, good to hear it is resolved now.

That’s the problem, the issue is *not* resolved… the todo items show up in the 
global todo list, but still not in the daily agenda view.

So I believe the TODO items are formatted `according to spec’ :-).
E.g., “** TODO Fix the daily agenda view”.

I tried the really minimal set-up, as documented on worg [1], and as it is it 
is not showing TODO items in the agenda, either. But when I switch on 'Org 
Agenda Include All Todo’, it does! With the same agenda files (thus I really 
assume they’re properly formatted). So, one step closer… but no cigar.

I’m now comparing the org settings between the two set-ups (as included in the 
org bug report facility), but I don’t notice anything obvious… it’s 
frustrating! But tomorrow is another day, and maybe with a fresh mind… who 
knows?


Thanks!
Peter.

[1] http://orgmode.org/worg/org-faq.html

Re: [O] org-agenda.el acquired a dependency on org-clock.el

[Achim Gratz]

Nick Dokos  writes:
> (require 'org-clock)
>
> in my init file to resolve the dependency, but that feels wrong.

It probably is... the three functions should get an autoload cookie, I
suppose.  Their declaration then deals with the compilation and the
autoload in org-install keeps things happy at runtime.


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

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: [O] Attachments and refiling

[Bastien]

Hi Darlan,

Darlan Cavalcante Moreira  writes:

> I requested this some time ago [1]. While there is not a built-in attach
> link type, org provides you with ways to easily create this functionality.
>
> In the setup part in my org-files I put
> #+LINK: attach elisp:(org-open-file (org-attach-expand "%s"))
>
> Now I can use the "attach" link type, but org will ask me if I want to
> allow executing the elisp code. To avoid this you can even set
> org-confirm-elisp-link-function to nil (I don't like this because it allows
> any elisp code in links) or you can set org-confirm-elisp-link-not-regexp
> appropriately.
>
> In my case I use
> : (setq org-confirm-elisp-link-not-regexp "org-open-file")
>
> This works very well.

This is a nice and useful hack -- I added it to Worg/org-hacks.org.

Thanks!

-- 
 Bastien

Re: [O] backend specific preprocess hook

[Bastien]

Hi Suvayu,

suvayu ali  writes:

> I wanted to do some preprocessing based on headline tags (set some
> properties), before export[1]. But I want to do this only for specific
> backends (html/latex). How can I achieve this?

Yes.

> [1] IIUC I have to customise the `org-export-preprocess-hook'?

Yes, and test against `org-export-current-backend' to see whether you
are exporting to HTML or LaTeX.

HTH,

-- 
 Bastien

Re: [O] Blog-like sitemap for org-publish

[Bastien]

Hi Jon,

Jon Anders Skorpen  writes:

> I have made a function which creates a blog-like sitemap. It works as
> an alternative sitemap function to org-publish. 

This looks very interesting -- do you have a webpage we can look at to
see the result?

Thanks!

-- 
 Bastien

Re: [O] [dev] org-indent-mode patch

[Bastien]

Nicolas Goaziou  writes:

> Bastien  writes:
>
>> Nicolas, feel free to merge this change so that more users can test
>> it.
>
> Done.

Great work, thanks!!

-- 
 Bastien

Re: [O] missing todo's in agenda after emacs/org upgrade

[suvayu ali]

Hello Peter,

On Thu, Aug 18, 2011 at 6:36 PM,   wrote:
> I have removed all customizations, started with an empty
> org-agenda-files list, opened my main planning file and added it to
> the agenda list. That’s about the most basic setup I can get. I do
> have the logged work now, that is already something, but still no TODO
> items on the current day (in day view). Oh, BTW, the Agenda TODO list
> shows all todo items… go figure!
>

It might be helpful to know how your TODO entries are formatted. Maybe
its not the setup, but how the agenda files are formatted that was
causing the issue?

In any case, good to hear it is resolved now.

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] [PATCH] org.el: Preserve indentation of manually indented lines in example blocks.

[Bastien]

Hi Valentin,

Valentin Wüstholz  writes:

> I was thinking of the the 80 character line limit for both code and
> commit messages, which doesn't seem to be in there. It might also make
> sense to link to some style guide for Emacs Lisp (e.g.,
> http://www.gnu.org/software/emacs/elisp/html_node/Coding-Conventions.html),
> that developers should adhere to. If you agree, I could commit those
> additions to worg.

I added a section pointing to this link in org-contribute.org.

It will be online as soon as Worg gets published fine again.

Thanks,

-- 
 Bastien

Re: [O] missing todo's in agenda after emacs/org upgrade

[peter . frings]

Hi Suvayu,

> This is quite an extensive setup. What do you get with only the
> following options:
[remainder at end]

I have removed all customizations, started with an empty org-agenda-files list, 
opened my main planning file and added it to the agenda list. That’s about the 
most basic setup I can get. I do have the logged work now, that is already 
something, but still no TODO items on the current day (in day view). Oh, BTW, 
the Agenda TODO list shows all todo items… go figure!

I switched on 'Org Agenda Include All Todo’, although the description says I 
should better use a block agenda. However, the ‘out of the box’ agenda should 
show the TODO items, no?


I restored my previous set-up and voila, all was there. Grrr. Note that I 
mistakenly reported org-mode’s version of previous setup (with Carbon Emacs) as 
6.6; it’s actually 7.4.


I’ll compare the two set-ups to see if there’s anything obvious (I did that 
already, but having a second look never hurts).

Thanks,
Peter.


[Remainder…]
> 
> (setq org-agenda-files
>  '("~/planning/planning.org" "~/planning/todo.org"
>   "~/planning/notes.org" "~/planning/time-sheet.org")
>  org-agenda-include-diary t
>  org-todo-keywords
>  '((sequence "TODO(t)" "BUSY(b)" "WAITING(w)" "|"
>  "DONE(d)" "CANCELLED(c)" "POSTPONED(p)")))
> 
> I think your best bet is to try to isolate which part of your setup is
> interfering. I would start with the most basic setup and systematically
> add more until I hit the problem.
> 
> GL
> 
> -- 
> Suvayu
> 
> Open source is the future. It sets us free.

Re: [O] git repository over http?

[Bastien]

Hi Jonathan,

Jonathan Leech-Pepin  writes:

> The server does seem to support HTTP for pulling, however it is very
> slow. 

Yes, I noticed this too.

> http:// does work for cloning and pulling from the main Repo, however
> there's nothing to indicate that anything is happening until the task
> is complete.

Yes.

Jason, is the slowliness something worth trying to fix?   
Can we get some indication that the repo is currently being
cloned?

Thanks!

-- 
 Bastien

Re: [O] Tutorial notes on ESS and org-babel-R

[Bastien]

Hi Stephen,

Stephen Eglen  writes:

> I gave a 3 hour tutorial on Emacs Speaks Statistics on Monday; this
> included mostly Emacs and ESS, but also introduced org-mode for R
> users.  If anyone is interested, the slides and material are available
> at: http://www.damtp.cam.ac.uk/user/sje30/ess11

Great -- I added a link to Worg/org-contribs/babel/uses.org

Thanks!

-- 
 Bastien

Re: [O] Bug: Extra space inserted in repeated tasks' date line

[Bastien]

Hi Sébastien,

"Sebastien Vauban"  writes:

> ** This one won't be moved along with the heading
>   SCHEDULED: <2011-08-18 Thu>
>
> Because of this text here...

This should be fixed now.  "Meta" lines (SCHEDULED string, etc, 
along with the first properties drawer) will be indented correctly,
even when text from the subtree start at the beginning of the line.

Please confirm this works okay for you, and thanks for reporting 
this!

Best,

-- 
 Bastien

Re: [O] Org Mode export: xelatex

[Puneeth Chaganti]

On Thu, Aug 18, 2011 at 9:09 PM, Rainer Thiel  wrote:
> I am aware I am not the only one who wants to export text written in
> org-mode in pfd through XeLaTeX.  In fact, I am aware of Kieran
> Healy's blog and of
> ,
> but can't seem to find a solution that wotks for me.  I use Emacs 23
> on a Windows Vista machine.
>
> I do manage to persuade org-mode to use XeLaTeX instead of pdfLaTeX,
> but org-mode insists upon including the fontenc and inputenc packages
> even though in org-export-latex-default-packages-alist both packages
> are set to "nil".  So compilation of the tex-file produced by org-mode
> fails.  I can heal this by manually removing both packages from the
> tex-file, but this, of course, detracts much from the convenience I am
> used to in using org-mode.
>
> Any hints how to solve this problem?

Did you look at this FAQ entry[1]? I think this is what you are looking for.

[1] - http://orgmode.org/worg/org-faq.html#using-xelatex-for-pdf-export

--
Puneeth

[O] Org Mode export: xelatex

[Rainer Thiel]

I am aware I am not the only one who wants to export text written in
org-mode in pfd through XeLaTeX.  In fact, I am aware of Kieran
Healy's blog and of
,
but can't seem to find a solution that wotks for me.  I use Emacs 23
on a Windows Vista machine.

I do manage to persuade org-mode to use XeLaTeX instead of pdfLaTeX,
but org-mode insists upon including the fontenc and inputenc packages
even though in org-export-latex-default-packages-alist both packages
are set to "nil".  So compilation of the tex-file produced by org-mode
fails.  I can heal this by manually removing both packages from the
tex-file, but this, of course, detracts much from the convenience I am
used to in using org-mode.

Any hints how to solve this problem?

Many thanks in advance and best regards,

Rainer
-- 
Prof. Dr. Rainer Thiel
Institut für Altertumswissenschaften
07737 Jena, Germany (EU)
r.th...@uni-jena.de

Re: [O] git repository over http?

[Jonathan Leech-Pepin]

Hello Bastien,

The server does seem to support HTTP for pulling, however it is very slow. I
have to use http from work because the firewall blocks the git:// protocol.
Times on my prompt are DST (-0400).

[10:22:25] ~/test$ git clone http://orgmode.org/org-mode.git
Cloning into org-mode...
[10:35:43] ~/test$ cd org-mode/
[10:36:46] ~/test/org-mode$ git log -1
commit 74cca9f57ee3896dad85d3b354d1d9db286e799b
Author: Nicolas Goaziou 
Date: Thu Aug 18 15:44:46 2011 +0200

org-indent: silence byte-compiler
[10:36:57] ~/test/org-mode$ cat .git/config
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
ignorecase = true
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = http://orgmode.org/org-mode.git
[branch "master"]
remote = origin
merge = refs/heads/master

http:// does work for cloning and pulling from the main Repo, however
there's nothing to indicate that anything is happening until the task is
complete.

Regards,

Jonathan

On Wed, Aug 17, 2011 at 3:52 AM, Bastien  wrote:

> Hi Peter,
>
> peter.fri...@agfa.com writes:
>
> > I can’t seem to clone the git repository over http (from
> > http://orgmode.org/org-mode.git). Is the server not supporting http, or
> is
> > it just me?
>
> The server isn't supporting the http protocol -- you can use
> http://repo.or.cz/w/org-mode.git instead, which lags behind by
> just ~1 hour.
>
> HTH,
>
> --
>  Bastien
>
>

Re: [O] missing todo's in agenda after emacs/org upgrade

[suvayu ali]

Hi Peter,

This is quite an extensive setup. What do you get with only the
following options:

(setq org-agenda-files
  '("~/planning/planning.org" "~/planning/todo.org"
"~/planning/notes.org" "~/planning/time-sheet.org")
  org-agenda-include-diary t
  org-todo-keywords
  '((sequence "TODO(t)" "BUSY(b)" "WAITING(w)" "|"
  "DONE(d)" "CANCELLED(c)" "POSTPONED(p)")))

I think your best bet is to try to isolate which part of your setup is
interfering. I would start with the most basic setup and systematically
add more until I hit the problem.

GL

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] [dev] org-indent-mode patch

[Nicolas Goaziou]

Hello,

Bastien  writes:

> Nicolas, feel free to merge this change so that more users can test
> it.

Done.

Regards,


-- 
Nicolas Goaziou

[O] missing todo's in agenda after emacs/org upgrade

[Peter Frings]

Good afternoon all,

I recently switched from the wonderful Carbon-emacs to the `no-frills'
Emacs for OSX, and decided to use the emacs `starter-kit for social
sciences' (http://kjhealy.github.com/emacs-starter-kit/) with it.

During the upgrade, I also upgraded org-mode from 6.6. to 7.7.

Now, the agenda no longers lists my todo items... the agenda files are
the same as the previous setup, the todo keywords are the same, ... I've
examined all plausible customizations, but I can't seem to find the
problem.

The agenda shows the (re)scheduled todo items all right, the Agenda Files 
menu shows the correct files, 

Another thing that’s missing are the logged items in the time grid. The 
repeating 
tasks show up, but the clocked tasks don’t.

This is probably something really stupid that I’m overlooking, but i can’t find 
it. 
Is there someone out there that can point me in the right direction?

Thanks!
Peter.



Emacs  : GNU Emacs 23.3.1 (x86_64-apple-darwin, NS apple-appkit-1038.35)
 of 2011-03-10 on black.porkrind.org
Package: Org-mode version 7.7

current state:
==
(setq
 org-export-latex-after-initial-vars-hook '(my-auto-tex-parameters 
my-auto-tex-cmd
org-beamer-after-initial-vars)
 org-link-frame-setup '((vm . vm-visit-folder-other-frame) (gnus . 
gnus-other-frame)
(file . find-file-other-frame))
 org-export-latex-listings 'minted
 org-agenda-clockreport-parameter-plist '(:link t :maxlevel 3)
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-agenda-custom-commands '(("p" "Postponed tasks" todo
   #("POSTPONED" 0 9 (face org-warning)) nil)
  )
 org-shiftdown-final-hook '(windmove-down)
 org-agenda-files '("~/planning/planning.org" "~/planning/todo.org" 
"~/planning/notes.org"
"~/planning/time-sheet.org")
 org-agenda-include-diary t
 org-src-window-setup 'current-window
 org-src-fontify-natively t
 org-babel-load-languages '((emacs-lisp . t) (sh . t) (R . t) (perl . t) (ruby 
. t)
(python . t) (js . t) (haskell . t) (clojure . t) 
(ditaa . t))
 org-hide-leading-stars t
 org-completion-use-ido t
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-shiftup-final-hook '(windmove-up)
 org-export-preprocess-after-blockquote-hook 
'(org-special-blocks-make-special-cookies)
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-babel-tangle-lang-exts '(("latex" . "tex") ("clojure" . "clj") ("haskell" 
. "hs")
  ("python" . "py") ("ruby" . "rb") ("perl" . "pl")
  ("emacs-lisp" . "el"))
 org-clock-history-length 10
 org-archive-location "~/planning/archive.org::From %s"
 org-log-state-notes-insert-after-drawers t
 org-export-html-after-blockquotes-hook 
'(org-special-blocks-convert-html-special-cookies)
 org-export-blocks-postblock-hook '(org-exp-res/src-name-cleanup)
 org-log-note-clock-out t
 org-export-html-style ""
 org-export-latex-format-toc-function 'org-export-latex-format-toc-default
 org-stuck-projects '("+LEVEL=2/-DONE" ("TODO" "NEXT" "NEXTACTION" "BUSY") nil)
 org-export-latex-after-blockquotes-hook 
'(org-special-blocks-convert-latex-special-cookies)
 org-agenda-time-grid '((daily weekly today) #("" 0 16 
(org-heading t))
(900 1000 1100 1230 1400 1500 1600 1730))
 org-src-lang-modes '(("r" . ess-mode) ("ocaml" . tuareg) ("elisp" . emacs-lisp)
  ("ditaa" . artist) ("asymptote" . asy) ("dot" . 
fundamental)
  ("sqlite" . sql) ("calc" . fundamental) ("C" . c))
 org-log-done-with-time nil
 org-tab-first-hook '(yas/org-very-safe-expand org-hide-block-toggle-maybe
  org-src-native-tab-command-maybe 
org-babel-hide-result-toggle-maybe)
 org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
 org-confirm-shell-link-function 'yes-or-no-p
 org-mouse-1-follows-link t
 org-export-first-hook '(org-beamer-initialize-open-trackers)
 org-agenda-include-all-todo t
 org-todo-keywords '((sequence "TODO(t)" "BUSY(b)" "WAITING(w)" "|" "DONE(d)" 
"CANCELLED(c)"
  "POSTPONED(p)")
 )
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-export-latex-packages-alist '(("" "graphicx" t) ("" "longtable" nil) ("" 
"float"))
 org-default-notes-file "~/planning/notes.org"
 org-directory "~/planning/"
 org-blank-before-new-entry '((heading . t) (plain-list-item))
 org-babel-pre-tangle-hook '(save-buffer)
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-show-empty-lines 
org-optimize-window-after-visibility-change)
 org-publish-project-alist '(("org" :base-directory "~/.emacs.d/" 
:publishing-directory
  "~/Documents/websites/kjhhome/esk/" :auto-sitemap 
t

Re: [O] [dev] org-indent-mode patch

[Bastien]

Hi Bernt,

Bernt Hansen  writes:

> I think incorporating it in master so it gets more exposure for
> testing is a good idea.

Thanks for the feedback.

Nicolas, feel free to merge this change so that more users can test it.

Thanks,

-- 
 Bastien

Re: [O] [odt] User-visible improvements

[suvayu ali]

Hi Jambu and Bastien,

On Thu, Aug 18, 2011 at 9:31 AM, Bastien  wrote:
> Hi Jambunathan,
>
> these are great improvements -- I'm surprised people didn't thank
> you more for this!  So, thanks.
>

Does this feature mean we can export to other common word processor
formats like .doc using the odt exporter and command line utilities
for the final conversion? Although this is not of direct interest to
me (I stay away from anything not Linux :-p), it might be interesting
to my Mac/Windows friends. :)

I also see Jambu mentions odp to pdf. I wasn't aware the odt exporter
could export to odp. This would be something I would love to test
more. Is there any special configuration I need to do? I tried looking
for variables, but nothing jumped out as an obvious customisation in a
cursory glance.

And of course a huge thanks to Jambu. :)

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] Bug: Extra space inserted in repeated tasks' date line

[Sebastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> On Aug 18, 2011, at 11:04 AM, Sebastien Vauban wrote:
>> Carsten Dominik wrote:
>>> On Aug 18, 2011, at 10:22 AM, Sebastien Vauban wrote:
 Similar to this, I've noticed that sometimes the SCHEDULED line (or
 DEADLINE, or ...) is moved synchronously with the heading when
 promoting/demoting, sometimes not.
 
 I now found in which cases it does and when it does not: it depends on
 the presence of text in the entry.
>>> 
>>> It depends on the presence of *unindented* text in the entry,
>>> and purposefully so.
>>> 
 So, for example:
 
 --8<---cut here---start->8---
 * The SCHED will be moved
  SCHEDULED: <2011-08-18 Thu>
 
 * This one won't be moved along with the heading
  SCHEDULED: <2011-08-18 Thu>
 
 Because of this text here...
 --8<---cut here---end--->8---

A question: in the above headlines, as I see them in your reply, the 2 spaces
in front of SCHEDULED keyword are replaced by 1, which makes it difficult to
follow the conversation, as the example is not anymore showing what it was
supposed to.

My question is (to you or others): am I the one having the problem when
displaying your reply, or is it more on your side when answering to a post?
Don't lose time with this, but I'd like to (try to) patch this, if it's lying
on my side.

>> [...] The indentation of both SCHEDULED lines is not changed at all.
>> 
>> I would like that their indentation would be changed with the heading, even 
>> if
>> I write all my body text starting in column 0.
>> 
>> So, this is not currently handled, IIUC?
>> 
>> The SCHEDULED lines don't have a different status than the "body text" for
>> indentation purpose ("follow-headline" or "stay-where-you-are")?
>
> They currently don't - but I see that this might makes sense to do 
> differently.

OK. Thanks for your answer.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] [dev] org-indent-mode patch

[Bernt Hansen]

Carsten Dominik  writes:

> On Aug 18, 2011, at 12:19 PM, Nicolas Goaziou wrote:
>
>> Hello,
>> 
>> Carsten Dominik  writes:
>> 
>>> what has happened to this patch?  Did you stop it due to my questions?
>>> That was not my intention - so if you are convinced that it works well,
>>> it might be a good solution.
>>> 
>>> On Jul 21, 2011, at 5:14 PM, Nicolas Goaziou wrote:
>>> 
 In order to circumvent the slow process at initialization, I've
 implemented an asynchronous initialization. Thus, one can open the
 buffer and start to write in it before initialization is complete. Once
 it is done, everything else is synchronous again.
 
 I think it is a good compromise. It needs testing though. Thus, if
 anyone is interested, I'll gladly hear his feedback.
 
 The branch is located at :
 
git://github.com/ngz/org-mode-lists.git indent-patch-no-timer
>> 
>> It's still there. As I use neither Org indent mode nor Visual line mode,
>> feedback is important. Have you tried it since asynchronous
>> initialization implementation?  Does it solve the problems you raised?
>> 
>> Bernt Hansen has been testing it for a few weeks now. As far as I know,
>> he hasn't encountered any problem so far.
>
> Well, if Bernt has been testing is w/o problems, it probably works.
> I propose you push it into master, to make everyone use it - this
> will be a good way to find out if there are niches
> where it causes problems.

I've been using it for awhile and haven't noticed any issues with it.  I
use org-indent mode but I don't use visual line mode.  I've switched
back and forth between this branch and master a few times during my
testing.

I think incorporating it in master so it gets more exposure for testing
is a good idea.

-Bernt

[O] Git merge tool for Org files

[Carsten Dominik]

Hi,

I was wondering if anyone here has the skills and interest to write
a git merge driver for Org mode files, in the way

   
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=lib/git-merge-changelog.c

does this for GNU style ChangeLog files?

One of the obstacle for using Org-mode for collaborative programs is that
many operations add or remove text from the beginning or end of a file,
or which add or remove a subnode from an outline tree.
These are operations that confuse the git merger, in particular
if two people have added something to a file, or removed/added
sequential sibling nodes.

I believe that this could be solved with a dedicated merge driver
that understands the integrity of an outline (sub)tree, and that
knows that the sequence of two new subtrees added by different people
does not matter.

The idea for this is actually (I believe) from Brian Gough who asked me
about it at FOSDEM.  I have now also run into this problem and would
really find it great if such a merge driver could be written.
Unfortunately, I do not have the skill for this.

- Carsten

Re: [O] [dev] org-indent-mode patch

[Carsten Dominik]

On Aug 18, 2011, at 12:19 PM, Nicolas Goaziou wrote:

> Hello,
> 
> Carsten Dominik  writes:
> 
>> what has happened to this patch?  Did you stop it due to my questions?
>> That was not my intention - so if you are convinced that it works well,
>> it might be a good solution.
>> 
>> On Jul 21, 2011, at 5:14 PM, Nicolas Goaziou wrote:
>> 
>>> In order to circumvent the slow process at initialization, I've
>>> implemented an asynchronous initialization. Thus, one can open the
>>> buffer and start to write in it before initialization is complete. Once
>>> it is done, everything else is synchronous again.
>>> 
>>> I think it is a good compromise. It needs testing though. Thus, if
>>> anyone is interested, I'll gladly hear his feedback.
>>> 
>>> The branch is located at :
>>> 
>>>git://github.com/ngz/org-mode-lists.git indent-patch-no-timer
> 
> It's still there. As I use neither Org indent mode nor Visual line mode,
> feedback is important. Have you tried it since asynchronous
> initialization implementation?  Does it solve the problems you raised?
> 
> Bernt Hansen has been testing it for a few weeks now. As far as I know,
> he hasn't encountered any problem so far.

Well, if Bernt has been testing is w/o problems, it probably works.
I propose you push it into master, to make everyone use it - this
will be a good way to find out if there are niches
where it causes problems.

- Carsten

Re: [O] [dev] org-indent-mode patch

[Nicolas Goaziou]

Hello,

Carsten Dominik  writes:

> what has happened to this patch?  Did you stop it due to my questions?
> That was not my intention - so if you are convinced that it works well,
> it might be a good solution.
>
> On Jul 21, 2011, at 5:14 PM, Nicolas Goaziou wrote:
>
>> In order to circumvent the slow process at initialization, I've
>> implemented an asynchronous initialization. Thus, one can open the
>> buffer and start to write in it before initialization is complete. Once
>> it is done, everything else is synchronous again.
>> 
>> I think it is a good compromise. It needs testing though. Thus, if
>> anyone is interested, I'll gladly hear his feedback.
>> 
>> The branch is located at :
>> 
>> git://github.com/ngz/org-mode-lists.git indent-patch-no-timer

It's still there. As I use neither Org indent mode nor Visual line mode,
feedback is important. Have you tried it since asynchronous
initialization implementation?  Does it solve the problems you raised?

Bernt Hansen has been testing it for a few weeks now. As far as I know,
he hasn't encountered any problem so far.

Regards,


-- 
Nicolas Goaziou

Re: [O] Bug: Extra space inserted in repeated tasks' date line

[Carsten Dominik]

On Aug 18, 2011, at 11:04 AM, Sebastien Vauban wrote:

> Hi Carsten,
> 
> Carsten Dominik wrote:
>> On Aug 18, 2011, at 10:22 AM, Sebastien Vauban wrote:
>>> Bastien wrote:
 Markus Berlin  writes:
> some time ago I noticed this small bug (small but it keeps annoying me!):
> an extra space is introduced just before "SCHEDULED"
>>> 
>>> Similar to this, I've noticed that sometimes the SCHEDULED line (or
>>> DEADLINE, or ...) is moved synchronously with the heading when
>>> promoting/demoting, sometimes not.
>>> 
>>> I now found in which cases it does and when it does not: it depends on the
>>> presence of text in the entry.
>> 
>> It depends on the presence of *unindented* text in the entry,
>> and purposefully so.
>> 
>>> So, for example:
>>> 
>>> --8<---cut here---start->8---
>>> * The SCHED will be moved
>>>  SCHEDULED: <2011-08-18 Thu>
>>> 
>>> * This one won't be moved along with the heading
>>>  SCHEDULED: <2011-08-18 Thu>
>>> 
>>> Because of this text here...
>>> --8<---cut here---end--->8---
>>> 
>>> becomes, when demoted:
>>> 
>>> --8<---cut here---start->8---
>>> * New section
>>> 
>>> ** The SCHED will be moved
>>>   SCHEDULED: <2011-08-18 Thu>
>>> 
>>> ** This one won't be moved along with the heading
>>>  SCHEDULED: <2011-08-18 Thu>
>>> 
>>> Because of this text here...
>>> --8<---cut here---end--->8---
>> 
>> See the variable `org-adapt-indentation'.
> 
> This was left untouched by me, that is set to t (default), with the above
> behavior.
> 
> If I change it to nil, I'm even farer from the behavior I would like to get.
> In this new case:
> 
> --8<---cut here---start->8---
> * New section
> 
> ** The SCHED will be moved
>  SCHEDULED: <2011-08-18 Thu>
> 
> ** This one won't be moved along with the heading
>  SCHEDULED: <2011-08-18 Thu>
> 
> Because of this text here...
> --8<---cut here---end--->8---
> 
> The indentation of both SCHEDULED lines is not changed at all.
> 
> I would like that their indentation would be changed with the heading, even if
> I write all my body text starting in column 0.
> 
> So, this is not currently handled, IIUC?
> 
> The SCHEDULED lines don't have a different status than the "body text" for
> indentation purpose ("follow-headline" or "stay-where-you-are")?


They currently don't - but I see that this might makes sense to do differently.

- Carsten

> 
> Best regards,
>  Seb
> 
> -- 
> Sebastien Vauban
> 
> 

- Carsten

[O] Tutorial notes on ESS and org-babel-R

[Stephen Eglen]

I gave a 3 hour tutorial on Emacs Speaks Statistics on Monday; this
included mostly Emacs and ESS, but also introduced org-mode for R
users.  If anyone is interested, the slides and material are available
at: http://www.damtp.cam.ac.uk/user/sje30/ess11

Thanks to the org-mode team for your work!

Stephen

Re: [O] Bug: Extra space inserted in repeated tasks' date line

[Sebastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> On Aug 18, 2011, at 10:22 AM, Sebastien Vauban wrote:
>> Bastien wrote:
>>> Markus Berlin  writes:
 some time ago I noticed this small bug (small but it keeps annoying me!):
 an extra space is introduced just before "SCHEDULED"
>> 
>> Similar to this, I've noticed that sometimes the SCHEDULED line (or
>> DEADLINE, or ...) is moved synchronously with the heading when
>> promoting/demoting, sometimes not.
>> 
>> I now found in which cases it does and when it does not: it depends on the
>> presence of text in the entry.
>
> It depends on the presence of *unindented* text in the entry,
> and purposefully so.
>
>> So, for example:
>>
>> --8<---cut here---start->8---
>> * The SCHED will be moved
>>   SCHEDULED: <2011-08-18 Thu>
>>
>> * This one won't be moved along with the heading
>>   SCHEDULED: <2011-08-18 Thu>
>>
>> Because of this text here...
>> --8<---cut here---end--->8---
>>
>> becomes, when demoted:
>>
>> --8<---cut here---start->8---
>> * New section
>>
>> ** The SCHED will be moved
>>SCHEDULED: <2011-08-18 Thu>
>>
>> ** This one won't be moved along with the heading
>>   SCHEDULED: <2011-08-18 Thu>
>>
>> Because of this text here...
>> --8<---cut here---end--->8---
>
> See the variable `org-adapt-indentation'.

This was left untouched by me, that is set to t (default), with the above
behavior.

If I change it to nil, I'm even farer from the behavior I would like to get.
In this new case:

--8<---cut here---start->8---
* New section

** The SCHED will be moved
  SCHEDULED: <2011-08-18 Thu>

** This one won't be moved along with the heading
  SCHEDULED: <2011-08-18 Thu>

Because of this text here...
--8<---cut here---end--->8---

The indentation of both SCHEDULED lines is not changed at all.

I would like that their indentation would be changed with the heading, even if
I write all my body text starting in column 0.

So, this is not currently handled, IIUC?

The SCHEDULED lines don't have a different status than the "body text" for
indentation purpose ("follow-headline" or "stay-where-you-are")?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] [dev] org-indent-mode patch

[Carsten Dominik]

Hi Nicolas,

what has happened to this patch?  Did you stop it due to my questions?
That was not my intention - so if you are convinced that it works well,
it might be a good solution.

- Carsten

On Jul 21, 2011, at 5:14 PM, Nicolas Goaziou wrote:

> Hello,
> 
> Carsten Dominik  writes:
> 
>> On 13.3.2011, at 17:21, Nicolas wrote:
>> 
>>> I'd like to submit the following org-indent-mode patch for testing.
>>> 
>>> 
>>> It implements two things:
>>> 
>>> 1. It indents correctly text when using visual-line-mode;
>>> 2. It removes the idle timer previous implementation was using, which
>>>  means it won't refresh indentation more often than necessary.
>>> 
>>> Unfortunately, there is a price to pay:
>>> 
>>> 1. Initialization will be much longer for large Org files, but I've
>>>  added a message to the user saying so.
>>> 2. It is a bit slower, as the algorithm has more things to check.
>>> 
>>> 
>>> Last point is obviously my main concern. Although not noticeable on my
>>> not-so-recent laptop, I don't know how it behaves on old machines.
>>> 
> 
>> Initial testing seems to show that this works well, very nice.
>> 
>> The delay at the beginning is long, and it might be annoying
>> when org pulls in a buffer just to look something up,
>> without org-inhibit-startup scoped into the file loading.
>> 
>> Maybe one could arrange for the initialization to happen just
>> before the buffer is first *displayed* (I do not know if that
>> is possible).
>> 
>> Just one nitpicking:  The idle timer may force updating when
>> not necessary - but using after-change-functions will update after
>> each character inserted.  So in fact your code might be updating
>> more often at least while typing - maybe not while looking at
>> the buffer and jumping around.  I am not a fast typist, but maybe
>> fast typists will notice significant delays, in particular
>> while writing inside a very long section?
> 
> In order to circumvent the slow process at initialization, I've
> implemented an asynchronous initialization. Thus, one can open the
> buffer and start to write in it before initialization is complete. Once
> it is done, everything else is synchronous again.
> 
> I think it is a good compromise. It needs testing though. Thus, if
> anyone is interested, I'll gladly hear his feedback.
> 
> The branch is located at :
> 
> git://github.com/ngz/org-mode-lists.git indent-patch-no-timer
> 
> 
> Regards,
> 
> -- 
> Nicolas Goaziou

- Carsten

Re: [O] Variable publishing-directory? (resent with patch as attachment)

[Kai Tetzlaff]

Bastien  writes:

Hi Bastien,

> The patch looks good but I'd like to understand it better.
> Can you send an example configuration working with your patch?

In org-publish-project-alist, i have HTML publishing projects which
should be published to different target directories depending on e.g.
where emacs is running (which i determine in my init files using the MAC
address of the default GW, the name the machine, ...).

Here is an example: At home, i publish to a local directory
(:publishing-directory "~/tmp/publish-test") but at work i would like to
publish directly to a webserver (:publishing-directory
"/plinkx:doxydoc:~/public_html/publish-test" - this is on w32, using
tramps PuTTY/plink). To avoid having to change the definition of the
publishing project when i change locations i would like to construct the
actual value of :publishing-directory by calling a function:

 ("publishing-dir-test"
 :base-directory "~/Documents/Work/RS"
 :recursive t
 :base-extension "org"
 :exclude-tags ("intern")
 :publishing-directory '(expand-file-name "publish-test" 
kt:org-default-publishing-dir)
 :publishing-function org-publish-org-to-html)

Depending on the location i'm in, 'kt:org-default-publishing-dir' would
be set to either "~/tmp" or "/plinkx:doxydoc:~/public_html". Without the
patch, the example above does not work as the value of
:publishing-directory does not get evaluated.

> Also, please try to send git patch using these conventions:
> http://orgmode.org/worg/org-contribute.html#sec-5
>
> Thanks a lot!

Thanks for the hint. I've attached a revised version of the patch which
includes a changelog/commit msg - i hope that works for you.

Publish: allow dynamic construction of the publish destination.

* org-publish.el (org-publish-file): Added 'eval'ing the value of the
 :publishing-directory property before using it as destination of the
 publishing project. This allows to construct the publish destination
 directory dynamically at run-time using the return value of a
 function.

TINYCHANGE
---
 lisp/org-publish.el |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/lisp/org-publish.el b/lisp/org-publish.el
index e2213c5..518c1bf 100644
--- a/lisp/org-publish.el
+++ b/lisp/org-publish.el
@@ -684,7 +684,7 @@ See `org-publish-projects'."
 	 (pub-dir
 	  (file-name-as-directory
 	   (file-truename
-	(or (plist-get project-plist :publishing-directory)
+	(or (eval (plist-get project-plist :publishing-directory))
 		(error "Project %s does not have :publishing-directory defined"
 		   (car project))
 	 tmp-pub-dir)
-- 
1.7.5.4

Re: [O] Bug: Extra space inserted in repeated tasks' date line

[Carsten Dominik]

On Aug 18, 2011, at 10:22 AM, Sebastien Vauban wrote:

> Hi Bastien and Markus,
> 
> Bastien wrote:
>> Markus Berlin  writes:
>> 
>>> some time ago I noticed this small bug (small but it keeps annoying me!):
>>> 
>>> If the following are set:
>>> 
>>>  (setq org-log-done 'time)
>>>  (setq org-log-repeat nil)
>>> 
>>> then if you press C-c C-t on a repeated tasks, like this one:
>>> 
>>> * TODO do nothing
>>>  SCHEDULED: <2011-08-12 Fr .+2d>
>>> 
>>> an extra space is introduced just before "SCHEDULED", i.e. you get:
>>> 
>>> * TODO do nothing
>>>   SCHEDULED: <2011-08-17 Mi .+2d>
>>>  ^
>>> 
>>> instead of what you want:
>>> 
>>> * TODO do nothing
>>>  SCHEDULED: <2011-08-17 Mi .+2d>
>> 
>> This is fixed in the current git repo -- please test and confirm.
> 
> Similar to this, I've noticed that sometimes the SCHEDULED line (or DEADLINE,
> or ...) is moved synchronously with the heading when promoting/demoting,
> sometimes not.
> 
> I now found in which cases it does and when it does not: it depends on the
> presence of text in the entry.


It depends on the presence of *unindented* text in the entry,
and purposefully so.  See the variable `org-adapt-indentation'.

HTH

- Carsten

> 
> So, for example:
> 
> --8<---cut here---start->8---
> * The SCHED will be moved
>  SCHEDULED: <2011-08-18 Thu>
> 
> * This one won't be moved along with the heading
>  SCHEDULED: <2011-08-18 Thu>
> 
> Because of this text here...
> --8<---cut here---end--->8---
> 
> becomes, when demoted:
> 
> --8<---cut here---start->8---
> * New section
> 
> ** The SCHED will be moved
>   SCHEDULED: <2011-08-18 Thu>
> 
> ** This one won't be moved along with the heading
>  SCHEDULED: <2011-08-18 Thu>
> 
> Because of this text here...
> --8<---cut here---end--->8---
> 
> Best regards,
>  Seb
> 
> -- 
> Sebastien Vauban
> 
> 

- Carsten

Re: [O] Bug: Extra space inserted in repeated tasks' date line

[Sebastien Vauban]

Hi Bastien and Markus,

Bastien wrote:
> Markus Berlin  writes:
>
>> some time ago I noticed this small bug (small but it keeps annoying me!):
>>
>> If the following are set:
>>
>>   (setq org-log-done 'time)
>>   (setq org-log-repeat nil)
>>
>> then if you press C-c C-t on a repeated tasks, like this one:
>>
>> * TODO do nothing
>>   SCHEDULED: <2011-08-12 Fr .+2d>
>>
>> an extra space is introduced just before "SCHEDULED", i.e. you get:
>>
>> * TODO do nothing
>>SCHEDULED: <2011-08-17 Mi .+2d>
>>   ^
>>
>> instead of what you want:
>>
>> * TODO do nothing
>>   SCHEDULED: <2011-08-17 Mi .+2d>
>
> This is fixed in the current git repo -- please test and confirm.

Similar to this, I've noticed that sometimes the SCHEDULED line (or DEADLINE,
or ...) is moved synchronously with the heading when promoting/demoting,
sometimes not.

I now found in which cases it does and when it does not: it depends on the
presence of text in the entry.

So, for example:

--8<---cut here---start->8---
* The SCHED will be moved
  SCHEDULED: <2011-08-18 Thu>

* This one won't be moved along with the heading
  SCHEDULED: <2011-08-18 Thu>

Because of this text here...
--8<---cut here---end--->8---

becomes, when demoted:

--8<---cut here---start->8---
* New section

** The SCHED will be moved
   SCHEDULED: <2011-08-18 Thu>

** This one won't be moved along with the heading
  SCHEDULED: <2011-08-18 Thu>

Because of this text here...
--8<---cut here---end--->8---

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] Variable publishing-directory?

[Kai Tetzlaff]

Bastien  writes:

Hi Bastien,

> The patch looks good but I'd like to understand it better.
> Can you send an example configuration working with your patch?

In org-publish-project-alist, i have HTML publishing projects which
should be published to different target directories depending on e.g.
where emacs is running (which i determine in my init files using the MAC
address of the default GW, the name the machine, ...).

Here is an example: At home, i publish to a local directory
(:publishing-directory "~/tmp/publish-test") but at work i would like to
publish directly to a webserver (:publishing-directory
"/plinkx:doxydoc:~/public_html/publish-test" - this is on w32, using
tramps PuTTY/plink). To avoid having to change the definition of the
publishing project when i change locations i would like to construct the
actual value of :publishing-directory by calling a function:

 ("publishing-dir-test"
 :base-directory "~/Documents/Work/RS"
 :recursive t
 :base-extension "org"
 :exclude-tags ("intern")
 :publishing-directory '(expand-file-name "publish-test" 
kt:org-default-publishing-dir)
 :publishing-function org-publish-org-to-html)

Depending on the location i'm in, 'kt:org-default-publishing-dir' would
be set to either "~/tmp" or "/plinkx:doxydoc:~/public_html". Without the
patch, the example above does not work as the value of
:publishing-directory does not get evaluated.

> Also, please try to send git patch using these conventions:
> http://orgmode.org/worg/org-contribute.html#sec-5
>
> Thanks a lot!

Thanks for the hint. I've attached a revised version of the patch which
includes a changelog/commit msg - i hope that works for you.

Publish: allow dynamic construction of the publish destination.

* org-publish.el (org-publish-file): Added 'eval'ing the value of the
 :publishing-directory property before using it as destination of the
 publishing project. This allows to construct the publish destination
 directory dynamically at run-time using the return value of a
 function.

TINYCHANGE
---
 lisp/org-publish.el |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/lisp/org-publish.el b/lisp/org-publish.el
index e2213c5..518c1bf 100644
--- a/lisp/org-publish.el
+++ b/lisp/org-publish.el
@@ -684,7 +684,7 @@ See `org-publish-projects'."
 	 (pub-dir
 	  (file-name-as-directory
 	   (file-truename
-	(or (plist-get project-plist :publishing-directory)
+	(or (eval (plist-get project-plist :publishing-directory))
 		(error "Project %s does not have :publishing-directory defined"
 		   (car project))
 	 tmp-pub-dir)
-- 
1.7.5.4

Re: [O] org-mode fontification error [6 times]

[Leo]

On 2011-08-18 15:22 +0800, Bastien wrote:
>> Just a heads-up. I saw this in my *message* buffer. I don't know how
>> it happened.
>
> Is this with emacs -Q?
>
> I am unable to reproduce this with emacs-23.3.1 and emacs-24.0.50.1.

It is in my normal running emacs session. I haven't found a reproduction
recipe. But I have been using the same org-mode setup for years.

Leo

Re: [O] Bug: Extra space inserted in repeated tasks' date line

[Bastien]

Hi Markus,

Markus Berlin  writes:

> some time ago I noticed this small bug (small but it keeps annoying me!):
>
> If the following are set:
>
>   (setq org-log-done 'time)
>   (setq org-log-repeat nil)
>
> then if you press C-c C-t on a repeated tasks, like this one:
>
> * TODO do nothing
>   SCHEDULED: <2011-08-12 Fr .+2d>
>
> an extra space is introduced just before "SCHEDULED", i.e. you get:
>
> * TODO do nothing
>SCHEDULED: <2011-08-17 Mi .+2d>
>   ^
>
> instead of what you want:
>
> * TODO do nothing
>   SCHEDULED: <2011-08-17 Mi .+2d>

This is fixed in the current git repo -- please test and confirm.

Thanks,

-- 
 Bastien

Re: [O] [odt] User-visible improvements

[Bastien]

Hi Jambunathan,

these are great improvements -- I'm surprised people didn't thank 
you more for this!  So, thanks.

Jambunathan K  writes:

> 1. A choice of command-line converters for org-lparse dependent backends
>like org-odt and org-xhtml.
>
>M-x customize-variable RET org-lparse-convert-processes RET
>
>- Currently two converters are supported. 
>  1. BasicODConverter - Home-brewed converter. This is available as
> an OpenOffice extension in contrib/odt/BasicODConverter dir of
> org git repo.
>
>  2. unoconv - Unable to install this locally on my machine. So use
> of this as a converter is largely untested. But should work
> without any glitches.
>
>  3. If there are other popular converters that are in use, I would
> like to add them to this list.
>
> 2. M-x customize-variable RET org-lparse-convert-process RET
>- Choose one of the based on your preferences and availability

I am not sure I understand why we need `org-lparse-convert-process' and
`org-lparse-convert-processes' -- isn't it possible to just have the
first one, while listing the choices within this option?  

> 3. Make C-c C-e O export directly to your preferred output format
>(doc?). Use 
>
>M-x customize-variable RET org-export-odt-preferred-output-format RET
>
>(But review items 1 and 2 before doing this)

I use unoconv.  

Can you give me an example configuration if I want C-c C-e O to output
files directly in, say, .doc (MS Word) format?

Thanks again, looking forward to test this more heavily!

-- 
 Bastien

Re: [O] org-mode fontification error [6 times]

[Bastien]

Hi Leo,

Leo  writes:

> Just a heads-up. I saw this in my *message* buffer. I don't know how
> it happened.

Is this with emacs -Q?

I am unable to reproduce this with emacs-23.3.1 and emacs-24.0.50.1.

Thanks,

-- 
 Bastien

Re: [O] Bug: Column view does not function properly in Agenda buffers [7.7]

[Bastien]

Hi Christian,

Christian Schmidt  writes:

> I can confirm, that this bug is fixed! This is just brilliant! Thank
> you very much!

Thanks for confirming.

> The first minor concern:
> 
> There is a leading star '*' in front of the ITEM.
> Could you remove this star '*', too?

Fixed.

> The second minor concern:
> =
> In a column-view, that is invoked inside Agenda buffer, there are
> lines, that seperate the todos for each day in the agenda. In version
> 7.5 those lines contained the corresponding date to give orientation.

Is this with a standard agenda view?  Which one?
If that's from an `org-agenda-custom-commands' can you share it?

> I don't want to appear greedy and I am already content with your
> bugfix so far. But maybe you've got the time to look after my two
> minor concerns mentioned above.

I'll try to fix the problem when I fully understand it :)

Best,

-- 
 Bastien

Re: [O] Commit 58f1dbcc Remove version header

[Bastien]

Hi Achim,

Achim Gratz  writes:

> there are a few diffs in that commit that the Changelog doesn't
> describe, especially one addition in org-clock.el that you may or may
> not have wanted to commit.

I didn't want the change in org-clock.el indeed.

Fixed, thanks!

-- 
 Bastien

Re: [O] Org-Mode Homepage error

[Bastien]

Achim Gratz  writes:

> Here's the new patch.

Applied, thanks!

-- 
 Bastien