[O] Linking back to archive

[Marcelo de Moraes Serpa]

Hi list,

I have a gtd.org with my projects and next actions as org items. When I'm
done with them, I archive, and they go to gtd.org_archive.

Sometimes, I create a new org file for a project, to keep notes and other
reference material. Let's say I have this in my gtd.org:

* Project :project:
   file://~/org/reference/project.org
** TODO Foo
** TODO Bar


When the Project is done in gtd.org, and I archive it, I'd like to add a
link back to the Project org item in gtd.org_archive from project.org. I
tried opening gtd.org_archive and then pressing C-l on the "* Project"
headline, then opening project.org and C-c C-l, and while it does paste the
org link, that looks like: file:~/org/gtd/gtd.org_archive::*Project, if I
click it nothing happens.

What could be wrong?

Thanks,

- Marcelo.

Re: [O] Icalendar Export Broken in Git Version

[Charles Philip Chan]

Nick Dokos  writes:

Hi Nick:

Thanks, Bastien already fixed it.

> There are only two recent commits against org-icalendar. The second
> one mentions org-print-icalendar-entries, so I bet that's the culprit
> :-)

I figured that it was that commit too when I grepped the git log. :-)

> For future reference, if you can reproduce the problem with
> *uncompiled* org-mode, the backtrace is going to be much more readable
> (no byte code hieroglyphics). Just something to keep in mind.

Thanks, I didn't know that.

Charles

-- 
"If you want to travel around the world and be invited to speak at a lot
of different places, just write a Unix operating system."
(By Linus Torvalds)


pgpWkIFdtMEqf.pgp
Description: PGP signature

Re: [O] Icalendar Export Broken in Git Version

[Nick Dokos]

Charles Philip Chan  wrote:

> Hello:
> 
> I tried to export an icalendar file with the current git version of
> org-mode and it failed. I debugged it by loading org-install on a clean
> Emacs with no init files and this is what I got:
> 
> ,
> | Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
> |   ...
> |   org-print-icalendar-entries(nil)
> |   ...
> |   org-export-icalendar(nil "/home/hoor/Desktop/Projects/plans/test.org")
> |   org-export-icalendar-this-file()
> |   call-interactively(org-export-icalendar-this-file record nil)
> |   command-execute(org-export-icalendar-this-file record)
> |   execute-extended-command(nil "org-export-icalendar-this-file")
> |   call-interactively(execute-extended-command nil nil)
> `
> 
> If I replace org-icalendar with the version that comes with my Emacs
> 24.1.50.1 everything works.
> 

There are only two recent commits against org-icalendar. The second one
mentions org-print-icalendar-entries, so I bet that's the culprit :-)

,
| commit 2cd498e16ddb8d321c2ab6e4fac18733b500
| Author: Bastien Guerry 
| Date:   Sun Aug 5 18:59:51 2012 +0200
| 
| Fix two compiler warnings.
| 
| commit 216768531f2661c4b1890eef6454f58e6cb8a241
| Author: Bastien Guerry 
| Date:   Sun Aug 5 11:30:23 2012 +0200
| 
| org-icalendar.el: Let APPT_WARNTIME take precedence over 
̀org-icalendar-alarm-time'.
| 
| * org-icalendar.el (org-print-icalendar-entries): Let
| APPT_WARNTIME take precedence over ̀org-icalendar-alarm-time'.
`

For future reference, if you can reproduce the problem with *uncompiled* 
org-mode,
the backtrace is going to be much more readable (no byte code hieroglyphics). 
Just
something to keep in mind.

Nick

Re: [O] [ANN] Editable HTML export of Org-mode files

[Eric Abrahamsen]

On Tue, Aug 14 2012, Eric Schulte wrote:

> Hi,
>
> I've recently put together a web server which runs in Emacs and exports
> local Org-mode files to HTML in such a way that they may be edited from
> within a web browser with the edits saved to local files on disk.  The
> code is available from github.
>
>  repository  https://github.com/eschulte/org-ehtml
>   README --- http://eschulte.github.com/org-ehtml
>
> This is a very thin Emacs Lisp and JavaScript wrapper around Nic
> Ferrier's elnode Emacs web server [1], and Nicolas Goaziou's structured
> Org-mode file representation and export engine.  It requires Emacs 24
> and the development versions of both Org-mode and elnode.
>
> The code is fairly new so there are likely some kinks to be worked out
> (backup your files before editing them with this web-server), but the
> implementation is very simple and should be easy to modify.  See the
> README for information on how to make use of elnode's authentication
> system, or how to have web edits automatically committed to a local
> version control system.

I gave this a very brief whirl, with the dev versions of emacs, org,
elnode, and org-ehtml, and running the test server on simple.org as
described in the README. Every time I edited a block and clicked "save",
it just deleted the whole block. I got these errors in
~/.elnodelogs/elnode-error:

20120814213846: elnode--sentinel 'open from 127.0.0.1.' for process  
*elnode-webserver-proc*<1> <127.0.0.1:59834> with buffer nil
20120814213846: Elnode status: *elnode-webserver-proc*<1> <127.0.0.1:59834> 
open from 127.0.0.1
20120814213847: elnode--sentinel 'open from 127.0.0.1.' for process  
*elnode-webserver-proc*<1> <127.0.0.1:59836> with buffer nil
20120814213847: Elnode status: *elnode-webserver-proc*<1> <127.0.0.1:59836> 
open from 127.0.0.1
20120814213847: filter: calling handler on *elnode-webserver-proc*<1> 
<127.0.0.1:59834>
20120814213848: starting HTTP response on *elnode-webserver-proc*<1> 
<127.0.0.1:59834>
20120814213848: Elnode-child-process init *elnode-webserver-proc*<1> 
<127.0.0.1:59834>
20120814213848: filter: handler returned on *elnode-webserver-proc*<1> 
<127.0.0.1:59834>
20120814213848: Elnode-child-process-filter http state: open data length: 4096 
on *elnode-webserver-proc*<1> <127.0.0.1:59834>
20120814213848: Elnode-child-process-filter http state: open data length: 4096 
on *elnode-webserver-proc*<1> <127.0.0.1:59834>
20120814213848: Elnode-child-process-filter http state: open data length: 1286 
on *elnode-webserver-proc*<1> <127.0.0.1:59834>
20120814213848: Elnode-child-process-sentinel Status @ finished: open -> exit 
on *elnode-webserver-proc*<1> <127.0.0.1:59834>
20120814213848: elnode--http-end ending socket *elnode-webserver-proc*<1> 
<127.0.0.1:59834>
20120814213848: elnode--sentinel 'deleted.' for process  
*elnode-webserver-proc*<1> <127.0.0.1:59834> with buffer  *elnode-request-59834*
20120814213849: Elnode status: *elnode-webserver-proc*<1> <127.0.0.1:59834> 
deleted
20120814213854: filter: calling handler on *elnode-webserver-proc*<1> 
<127.0.0.1:59836>
20120814213854: starting HTTP response on *elnode-webserver-proc*<1> 
<127.0.0.1:59836>
20120814213854: elnode--process-send-eof on *elnode-webserver-proc*<1> 
<127.0.0.1:59836>
20120814213854: elnode--http-end ending socket *elnode-webserver-proc*<1> 
<127.0.0.1:59836>
20120814213855: elnode--sentinel 'deleted.' for process  
*elnode-webserver-proc*<1> <127.0.0.1:59836> with buffer  *elnode-request-59836*
20120814213855: Elnode status: *elnode-webserver-proc*<1> <127.0.0.1:59836> 
deleted
20120814213855: filter: handler returned on *elnode-webserver-proc*<1> 
<127.0.0.1:59836>
20120814213940: elnode--sentinel 'open from 127.0.0.1.' for process  
*elnode-webserver-proc*<1> <127.0.0.1:59848> with buffer nil
20120814213940: Elnode status: *elnode-webserver-proc*<1> <127.0.0.1:59848> 
open from 127.0.0.1
20120814213940: filter: calling handler on *elnode-webserver-proc*<1> 
<127.0.0.1:59848>
20120814213940: starting HTTP response on *elnode-webserver-proc*<1> 
<127.0.0.1:59848>
20120814213940: elnode--process-send-eof on *elnode-webserver-proc*<1> 
<127.0.0.1:59848>
20120814213940: elnode--http-end ending socket *elnode-webserver-proc*<1> 
<127.0.0.1:59848>
20120814213940: elnode--sentinel 'deleted.' for process  
*elnode-webserver-proc*<1> <127.0.0.1:59848> with buffer  *elnode-request-59848*
20120814213940: Elnode status: *elnode-webserver-proc*<1> <127.0.0.1:59848> 
deleted
20120814213941: filter: handler returned on *elnode-webserver-proc*<1> 
<127.0.0.1:59848>
20120814213954: elnode--sentinel 'open from 127.0.0.1.' for process  
*elnode-webserver-proc*<1> <127.0.0.1:59851> with buffer nil
20120814213954: Elnode status: *elnode-webserver-proc*<1> <127.0.0.1:59851> 
open from 127.0.0.1
20120814213955: filter: calling handler on *elnode-webserver-proc*<1> 
<127.0.0.1:59851>
20120814213955: starting HTTP response on *elnode-webserver-proc*<1> 
<127.0.

Re: [O] auto-push to mobile (but only when editing org buffer)

[Ken Mankoff]

How can I wrap that to only run when the active buffer is in Org 
Mode?


(run-at-time "00:10" 10 (lambda () (if (eq major-mode 'org-mode) 
(org-mobile-push


That works well. After reading run-at-time documentation, the 
"00:10" isn't ideal. I now use the following, which syncs files 
every 60 seconds starting 1 minute after launching emacs:


(run-at-time "1 min" 60 (lambda () (if (eq major-mode 
'org-mode)(org-mobile-push

Thanks,

  -k.

Re: [O] Capture template --- :empty-lines 1 results in error

[Bastien]

Hi Alan,

"Alan E. Davis"  writes:

> This may be a bug?
>
> I have this template in my list of templates, to open the file with
> my templates, so I could edit it:
>
>    ("i" "Edit ~/org/capture-templates.2.el" plain (file "~/org/
> capture-templates.2.el") "" :empty-lines 1 :unnarrowed t)
>
> I started to get an error when running this template, and a few
> others.  

Can you tell what error?

(setq debug-on-error t)

> This started somewhat recently, but I don't know exactly
> when. 
>
>     When I removed the ":empty-lines 1" part, the template worked
> fine.  
>
>     ("i" "Edit ~/org/capture-templates.2.el" plain (file "~/org/
> capture-templates.2.el") " "  :unnarrowed t)
>
> I am pretty sure that this is not only from the "empty-lines 1
> part.   Another template with this option does work ok, but has
> ":prepend t".

Hard to reproduce... perhaps you can try to bisect and find the 
culprit commit?  Or just rewind a bit and tell what version works
for sure, and what version doesn't?

Thanks in advance,

-- 
 Bastien

Re: [O] Elint

[Bastien]

Hi Achim,

Achim Gratz  writes:

> If anybody has an idea on how to deal with these two problems, please
> chime in.

I guess more people may have ideas about this on emacs-devel@.
Elint is quite old -- it surely needs some love.

-- 
 Bastien

Re: [O] Icalendar Export Broken in Git Version

[Bastien]

Hi Charles,

Charles Philip Chan  writes:

> I tried to export an icalendar file with the current git version of
> org-mode and it failed. I debugged it by loading org-install on a clean
> Emacs with no init files and this is what I got:

Fixed, thanks for reporting this.

-- 
 Bastien

Re: [O] auto-push to mobile (but only when editing org buffer)

[Bastien]

Hi Ken,

Ken Mankoff  writes:

> How can I wrap that to
> only run when the active buffer is in Org Mode?

(run-at-time "00:10" 10 (lambda () (if (eq major-mode 'org-mode) 
(org-mobile-push

HTH,

-- 
 Bastien

[O] auto-push to mobile (but only when editing org buffer)

[Ken Mankoff]

I'm trying to set up auto-pushing via org-mobile-push to make org-mode
work more seamlessly with the iPhone. I have the following in my
.emacs:

(run-at-time "00:10" 10 'org-mobile-push)

which is running org-mobile-push every 10 seconds. This is for
testing. I'll reduce it to every 5 minutes once I'm done testing. But
it runs even when I'm just editing ~/.emacs. How can I wrap that to
only run when the active buffer is in Org Mode?

Thanks,

   -k.

[O] Icalendar Export Broken in Git Version

[Charles Philip Chan]

Hello:

I tried to export an icalendar file with the current git version of
org-mode and it failed. I debugged it by loading org-install on a clean
Emacs with no init files and this is what I got:

,
| Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
|   byte-code("\306 \210\203\307 \310\216 *\204\311 
\210\312u\210\313\314\315\"\210\316\224\317\316!\320 
\321\315\322\323\217@\324\325\315\326\"!A\324\325\315\327\"\206FB\205F\330 
\321B#C\324\325\315\331\332#!DE\203_\333 \202f\334 \206f\335 F\336 
G\325\315\337\"\211H\205z\340H!H\341I\315\211JK\342L!\203\237\316\225b\210\317\343!M\344\345M\"?\202\322e\nNZ]\n{O\344\346\"\203\273\315\347\350\321\315$\202\274M\344PO\"J\344QO\"K\351
 
RS\204\346J\204\346K\204\346\313\314\321\"\210T\203\372\352\315\353\354\f\"\"\203\372\313\314\321\"\210J\203
R\203\f\355U>?\202
\356U>?\203
\313\314\321\"\210K\2038R\203+\355V>?\2020\356V>?\2038\313\314\321\"\210J\203A\357\202KK\203J\360\202K\361W\344X@\"\204_\344Y@\"\203h\347\341\321\211@$@\344\362\"\203\203\363\364\317\365\"\366\"A\367\317\343\"RZ\202\206\341ZA\206\215@A\315\370\371\217[H\316V\204\243\\\316V\203\310[@\203\310[A@\203\310\365[8\203\310\372\373AH\206\302\\#I\202\313\341I)\344]A\"\203\357\347\374\225\203\343\317\374A\"\202\350\317\343A\"\321\211A$AJ\203\372\375APAK\203\376APA\344\377\"\203

Re: [O] Org Build System (aka Makefile)

[Bastien]

Hi Achim,

I reverted the commits introducing the _COMPILE_ variable and the elint
targets in the makefile.

I'm with Eric on thinking that even the casual developer should not have
to tweak his local.mk to run the equivalent of `make compile-single', as
it is directly useful to get some warnings.  Even further: if a user
reports a bug and we want to give him directions to get more information
on his environment, asking him to run `make compile-single' is simple.

As for elint, your last email shows this is still largely experimental 
and I doubt many developers use it to get useful warnings.  Maybe `make
elint' would be useful at some point, but for now developers can simply
do M-x elint-current-buffer RET if they want.

I also reduced the number of targets displayed by `make targets': only
the ones that may be directly useful to the user or the developers are
shown.  You were right on this -- I first needed all doc to be able to 
follow your development myself...

I hope you'll understand the choices above.

Best,

-- 
 Bastien

Re: [O] Org Build System (aka Makefile)

[Bastien]

Achim Gratz  writes:

> http://orgmode.org/worg/dev/org-build-system.html
>
> I'll add that link to `make help´.

Good idea, thanks!

-- 
 Bastien

Re: [O] Org Build System (aka Makefile)

[Bastien]

Achim Gratz  writes:

>> cleandirs, cleancontrib, cleantesting, cleanutils, cleanelc
>
> Internal use and compatibility, I could remove the documentation if
> Bastien changes his mind about all the target needing documentation.

I'll stick to this: it is good to document all existing targets.

The question is whether a target should be displayed by `make helpall'
rather than just ̀make help'.  

The current make help is sober enough for me.

>> targets
>
> Mandated by GNU Makefile standards which I try to adhere to.

Sure, let's keep it.

-- 
 Bastien

Re: [O] [babel, ess] How can I make S-RET to be multi-session friendly?

[Bastien]

Hi Mikhail,

Mikhail Titov  writes:

> I would say that after applying changes to my-ess-eval and to
> org-babel-edit-prep:R as suggested by Andrew, it looks like everything
> is working right for me.

I'v been bold and I pushed the change Andrew suggested.

Thanks for reporting this and for testing around -- and thanks
to Andrew for the exploration and the fix! 

-- 
 Bastien

Re: [O] A tidy file maketh a tidy mind?

[Bastien]

Eric Schulte  writes:

> The code could look something like the following
>
> ;; -*- emacs-lisp -*-
> (let ((buf (org-element-parse-buffer))) ;; convert current buffer to ELisp
>   (dolist (rule cleanup-rules) ;; run cleanup transformations on the 
> buffer
> (setq buf (funcall rule buf)))
>   (delete-region (point-min) (point-max)) ;; replace the buffer contents
>   (insert (org-element-interpret-data buf))) ;; with the cleaned results
>
> The only catch would be deciding what to add to the cleanup-rules.

One useful clean up operation, also illustrated in 'Mash's example,
is to put time-stamps (i.e. SCHEDULED: lines etc.) where they belong,
right after the headline.

Is there any taker for such a function?

It would be a nice addition to org-hacks.org!

-- 
 Bastien

Re: [O] [babel, ess] How can I make S-RET to be multi-session friendly?

[Mikhail Titov]

Eric Schulte  writes:

> Thanks for sending this along, unfortunately ob-R.el is currently
> without a core maintainer

Quite a sad situation, many good modules lack maintainers :(

>, so I'm not sure who on list would have the expertise to review your
>submission.  Although hopefully those experiencing the problem can at
>least check if it works for them.

I'm not an expert but I gave it a shot.

>> It seems that for me, the inferior ess process is not being properly
>> associated with the src edit buffer.  It is being set correctly by
>> org-babel-R-associate-session, and then being set a second time
>> incorrectly by org-babel-edit-prep:R.  Commenting out line 5 in
>> org-babel-edit-prep:R seems to fix this issue, although I'm honestly
>> not sure if or what it breaks.  Everything seems ok for me, but ymmv.
>>
>> Heres the change:
>> #+begin_src emacs-lisp
>>   (defun org-babel-edit-prep:R (info)
>> (let ((session (cdr (assoc :session (nth 2 info)
>>   (when (and session (string-match "^\\*\\(.+?\\)\\*$" session))
>> (save-match-data (org-babel-R-initiate-session session nil))
>> ;;(setq ess-local-process-name (match-string 1 session)
>> )))
>> #+end_src
>>
>
> Perhaps replacing the commented "setq ess-local-process-name" line with
> ess-switch-process could solve this problem?  Could the process name be
> found programatically, perhaps using the regexp solution above.
>
>>
>> Is there any one having such issues, or who can weigh in on what
>> exactly is happening here?
>>
>> Without making the above change, it is possible to manually attach an
>> ess process to the current src buffer by using the command:
>>
>> C-c C-s (ess-switch-process)
>>
>> You'll have to specify the process name, rather than the buffer name,
>> and the session must have already been started.

I would say that after applying changes to my-ess-eval and to
org-babel-edit-prep:R as suggested by Andrew, it looks like everything
is working right for me. Once I hit C-c ' I see properly named buffer
appear with new process. Then if I hit S-RET it asks me what session to
use and since I have ido mode, it already highlights proper session
name, so I just hit RET. Perhaps it worth recommending to use ido?

Note that I do not have to enter process name.

If I quite R, while editing code in a separate buffer, and hit S-RET it
is executed in the wrong one without any question being asked :(

I'm running somewhat recent bzr version of Emacs with default Org in it.

-- 
Mikhail

Re: [O] Activate/deactivate export of inlinetasks with #+OPTIONS

[Bastien]

Hi Rasmus,

Rasmus  writes:

> (defcustom org-export-with-inlinetasks t
>   "Non-nil means include INLINETASKS keywords in export.
> When nil, remove all these keywords from the export."
>   :group 'org-export-general
>   :type 'boolean)

+1 for having this for the new exporter.

Thanks for the idea and the code!

-- 
 Bastien

Re: [O] [ANN] Editable HTML export of Org-mode files

[Bastien]

Hi Eric,

Eric Schulte  writes:

> With respect to security, elnode has a simple authentication system
> which seems to work well in my local trials.  It has no forms for
> setting passwords online, so users would have to generate a hash of
> their password locally, and then send the hash to someone who would
> manually add it to the elnode authentication database on orgmode.org.
>
> During authentication the hashed password is sent in plain text, so we
> would need to run the elnode server behind an https proxy server.  I
> don't think this would be difficult to implement and is a good idea for
> any system with authentication.

Thanks for those details.

> With respect to integration with the existing Worg, this system should
> work well in concert with the git backend.  Git could still be used for
> offline edits as it is currently.  The org-ehtml server could be
> configured to commit all web edits to git.  A conflict checker would be
> needed, which could be added to the `org-ehtml-before-save-hook'.

I think a page should be locked when a user is editing it through
org-ehtml.el.  This would prevent conflicts from concurrent editing
from the web.

As for conflicts between the .org to be written (from org-ehtml) and 
the .org that might have been pushed trough git, what would be the
behavior?  Discard this edit?  Use org-merge-driver to help resolve
the conflict?  Let the user download the .org he has been editing, 
so that his changes are not lost?

This is still quite unclear to me.  

In any case, we should first try this on a prototype for a while and 
see if this is robust enough.

-- 
 Bastien

[O] Capture template --- :empty-lines 1 results in error

[Alan E. Davis]

This may be a bug?

I have this template in my list of templates, to open the file with my
templates, so I could edit it:

   ("i" "Edit ~/org/capture-templates.2.el" plain (file
"~/org/capture-templates.2.el") "" :empty-lines 1 :unnarrowed t)

I started to get an error when running this template, and a few others.
This started somewhat recently, but I don't know exactly when.

When I removed the ":empty-lines 1" part, the template worked fine.

("i" "Edit ~/org/capture-templates.2.el" plain (file
"~/org/capture-templates.2.el") " "  :unnarrowed t)

I am pretty sure that this is not only from the "empty-lines 1 part.
Another template with this option does work ok, but has ":prepend t".

Alan Davis

Re: [O] [GSoC] Org-sync v0.2

[Bastien]

Hi Achim,

Achim Gratz  writes:

>> I thought os is short for org-sync, just like ob is for org-babel?
>
> Yes, but only the source files are shortened to ob-*.el, the function
> and variable names still spell out org-babel (with very few exceptions).
> I think that would be a good example to follow, especially as an "os-"
> prefix might easily clash with other namespaces.

Agreed.  I will discuss this with Aurélien.

-- 
 Bastien

Re: [O] [OT] ELNODE is soon to be released as version 1.0

[Bastien]

Hi Christopher,

please discuss this on a place related to elnode, this is OT here.

Thanks for your understanding!

-- 
 Bastien

Re: [O] [OT] ELNODE is soon to be released as version 1.0

[Christopher Allan Webber]

>> Is elnode a Free Software - AGPL?

If elnode is under GPLv3 or later, it's still free software.

>
> I was looking for a license but it seems to have it under COPYING.
> Anyways, should it be AGPL?

I'm a big fan of the AGPL... my own personal project uses it... but I
might be somewhat cautious about releasing a web framework under that
library.  There's a huge scope of things you may be unintentionally be
forcing people to share (such as passwords, etc) especially since
configuration is done in lisp.  I think complying with the distribution
requirements of the AGPL may be hard for a lot of elnode projects in
ways that are not intended without carefully crafted exceptions.  I
think AGPL makes a lot of sense for web applications, but I'd be
cautious about using it for libraries as such.

But that's just my two cents and I know not all AGPL supporters would
agree with me on this.

[O] Elint

[Achim Gratz]

Here's what my investigations into the elint make target(s) have dug up
so far…

I've increased max-specpdl-size and max-lisp-eval-depth by more than a
factor of ten.  Emacs will now eat a good deal of memory, and a few
errors have been dodged this way, but whenever elint encounters
cal-menu, Emacs falls into a rabbit hole (and will even segfault if the
limits are increased too far) and I don't trust anything that happens
after that.

Also, elint seems to habitually refuse to expand cl macros, although I'm
not yet sure if that is a principle limitation of elint or if the tricky
load structure that the cl package is using is throwing it off.  If the
latter, I might be able to preload all the cl stuff into elint and avoid
those errors.

If anybody has an idea on how to deal with these two problems, please
chime 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

Re: [O] Activate/deactivate export of inlinetasks with #+OPTIONS

[Suvayu Ali]

On Tue, Aug 14, 2012 at 01:19:47PM +0100, Rasmus wrote:
> 
> Hi list,
> 
> When writing documents, I think in terms of LaTeX.  There, a common
> option in `draft'.  In orgmode inlinetasks is a draft-thingy to me.  I
> want to easily remove inlinetasks before exporting a final (that merely
> means `pretty') version.
> 
> To reach an Org-ish solution I wrote the following trivial advice+extra,
> which allows #+OPTIONS: inline:t or #+OPTIONS: inline:nil.  It works
> only with the new exporter (which is amazing!!!).
> 

[...]

> 
> If this is of high enough standards it could perhaps be added to the
> worg. . .
> 

Worg is exactly for these kind of things!  Feel free to add it to an
appropriate page.  I would suggest Worg/org-hacks.org::Exporting org
files .

> –Rasmus

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] [OT] ELNODE is soon to be released as version 1.0

[Bastien]

Jambunathan K  writes:

> I was looking for a license but it seems to have it under COPYING.
> Anyways, should it be AGPL?
>
> Will Nic be coaxed to put it under GNU ELPA?

I'm copying Nic.

Let's take further discussion (if any) outside of the org-mode list.

-- 
 Bastien

Re: [O] Capturing to a list in a dynamic 2nd level heading

[Simon Brown]

Hi cj

At Mon, 13 Aug 2012 13:50:09 -0400,
Christopher J. White wrote:
> I have a capture template that does almost exactly that, I just use a 
> user entered subheading -- should be easy enough to tweak for your task.

Yes indeed, thank you very much!

Simon

> Capture template:
> 
>("d" "Discussion Item" item
>   (file+function
>"~/org/Todo.org"
>(lambda ()
>  (let* ((ctxt (read-string "Discussion context: "))
> (ctxt-pt
>   (condition-case msg
>   (org-find-olp (list "Discussion Items" ctxt) t)
> (error nil
>(if ctxt-pt
>(progn
>  (goto-char ctxt-pt)
>  (org-end-of-subtree)
>  (insert-string "\n"))
>  (goto-char (org-find-olp (list "Discussion Items") t))
>  (org-end-of-subtree)
>  (insert-string (format "\n** %s\n" ctxt)))

Re: [O] [GSoC] Org-sync v0.2

[Achim Gratz]

Suvayu Ali writes:
> On Sun, Aug 12, 2012 at 10:09:31PM +0900, Waldemar Quevedo wrote:
>> 
>> Not a big deal but I see that you have to set os-github-auth and call M-x
>> os-import, os etc..
>> to use org-sync. Since the library is named org-sync, wouldn't it be better 
>> to 
>> base on the library name for these settings? e.g. `org-sync-github-auth`,
>> `org-sync-import`...
>> 
>
> I thought os is short for org-sync, just like ob is for org-babel?

Yes, but only the source files are shortened to ob-*.el, the function
and variable names still spell out org-babel (with very few exceptions).
I think that would be a good example to follow, especially as an "os-"
prefix might easily clash with other namespaces.


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

Re: [O] Exporting inline code sections

[Ken Williams]

> -Original Message-
> From: nicholas.do...@hp.com [mailto:nicholas.do...@hp.com]
> Sent: Tuesday, August 14, 2012 10:20 AM
>
> You might want to try edebug instead of the standard debugger,

MUCH better, thanks!

 -Ken


CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended 
recipient(s) and may contain confidential and privileged information. Any 
unauthorized review, use, disclosure or distribution of any kind is strictly 
prohibited. If you are not the intended recipient, please contact the sender 
via reply e-mail and destroy all copies of the original message. Thank you.

Re: [O] Exporting inline code sections

[Nick Dokos]

Ken Williams  wrote:

> > C-h v org-src-preserve-indentation RET
> 
> Okay, I was stepping through org-edit-src-exit with the emacs debugger, get=
> ting my bearings - but now for the life of me I can't get the debugger to t=
> rigger when entering that function anymore.  I do `M-x debug-on-entry org-e=
> dit-src-exit`, then put my point in a table.el table and hit `C-c '`, then =
> hit `C-c '` again to exit the editing buffer, and no debugging happens.  Ca=
> n someone think of why that might be?
> 

You might want to try edebug instead of the standard debugger, but the
following steps might help in any case (with appropriate translations).

I have had such problems and I try the following steps (in increasing
order of desperation):

o quitting out of any existing debug sessions and/or error backtraces
  and try again.

o M-x top-level and try again.

o reload the file (uncompiled) and redo the M-x edebug-defun - btw,
  there are convenient shorthands: C-M-x to reevaluate the defun and turn
  off edebug and C-u C-M-x to enable edebug on the defun. Then try again.

o restart emacs and try again.

o reboot the machine and try again :-)

Nick

Re: [O] [OT] ELNODE is soon to be released as version 1.0

[Jambunathan K]

Jambunathan K  writes:

> Is elnode a Free Software - AGPL?

I was looking for a license but it seems to have it under COPYING.
Anyways, should it be AGPL?

Will Nic be coaxed to put it under GNU ELPA?

https://github.com/nicferrier/elnode/blob/57bb600b596a143ecd36ab994a287a7b71889ffb/COPYING

Re: [O] [OT] ELNODE is soon to be released as version 1.0

[Jambunathan K]

Is elnode a Free Software - AGPL?

-- 

Re: [O] Exporting inline code sections

[Ken Williams]

> -Original Message-
> From: nicholas.do...@hp.com [mailto:nicholas.do...@hp.com]
> Sent: Monday, August 13, 2012 6:34 PM
>
> Ken Williams  wrote:
>
> > The other thing I just noticed was that every time I edit a table.el
> > table with C-c ', two more spaces get inserted to the left of the
> > table when it's reinserted into the org buffer.  I tried to find where
> > in the code that's happening (probably in org-edit-src-exit?) but I
>
> Yes.
>
> > couldn't quite see it.
>
> C-h v org-src-preserve-indentation RET

Okay, I was stepping through org-edit-src-exit with the emacs debugger, getting 
my bearings - but now for the life of me I can't get the debugger to trigger 
when entering that function anymore.  I do `M-x debug-on-entry 
org-edit-src-exit`, then put my point in a table.el table and hit `C-c '`, then 
hit `C-c '` again to exit the editing buffer, and no debugging happens.  Can 
someone think of why that might be?

Otherwise I have to try to simulate emacs in my head to see what this code is 
doing, and that's not going to be pretty. =)

 -Ken

CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended 
recipient(s) and may contain confidential and privileged information. Any 
unauthorized review, use, disclosure or distribution of any kind is strictly 
prohibited. If you are not the intended recipient, please contact the sender 
via reply e-mail and destroy all copies of the original message. Thank you.

Re: [O] [ANN] Editable HTML export of Org-mode files

[Eric Schulte]

Bastien  writes:

> Rasmus  writes:
>
>> That's very cool!  Good job!  This could be useful.  Would this be
>> something that could eventually be used in the Worg?
>
> If there are some good ideas, and if Jason (as the security guy for 
> the server) is okay, why not?

With respect to security, elnode has a simple authentication system
which seems to work well in my local trials.  It has no forms for
setting passwords online, so users would have to generate a hash of
their password locally, and then send the hash to someone who would
manually add it to the elnode authentication database on orgmode.org.

During authentication the hashed password is sent in plain text, so we
would need to run the elnode server behind an https proxy server.  I
don't think this would be difficult to implement and is a good idea for
any system with authentication.

With respect to integration with the existing Worg, this system should
work well in concert with the git backend.  Git could still be used for
offline edits as it is currently.  The org-ehtml server could be
configured to commit all web edits to git.  A conflict checker would be
needed, which could be added to the `org-ehtml-before-save-hook'.

Cheers,

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

Re: [O] A tidy file maketh a tidy mind?

['Mash (Thomas Herbert)]

On 2012-08-14 07:10-0600, Eric Schulte wrote:
> 'Mash  writes:
>
> > Morning,
> >
> > I just want to know if there is there exists a 'tidy' module/command
> > that can be run on a file to tidy it?
> >
> > I often find myself going back and adding extra line breaks and
> > padding, and wondering if there exists something that can do this for
> > me?
> >
>
> While this doesn't exist currently, it should be fairly easy to
> implement a set of rules which operate over the parsed file
> representation generated by org-element.  This may be used to convert an
> Org-mode buffer into an elisp list, manipulate the list, and then insert
> the results as text back into a new buffer.
>
> The code could look something like the following
>
> ;; -*- emacs-lisp -*-
> (let ((buf (org-element-parse-buffer))) ;; convert current buffer to ELisp
>   (dolist (rule cleanup-rules) ;; run cleanup transformations on the 
> buffer
> (setq buf (funcall rule buf)))
>   (delete-region (point-min) (point-max)) ;; replace the buffer contents
>   (insert (org-element-interpret-data buf))) ;; with the cleaned results
>
> The only catch would be deciding what to add to the cleanup-rules.
>
> Also, since Org-mode is plain text, I bet a couple of lines of sed or
> perl could get you most of the way to a clean buffer.

Thanks, I need to spend some time to look at rules. But my most
common clean-up is really just adding some spacing/padding for
example. Would be handy to implement in a save-hook along with org-sort.

--- cluttered ---
* Lorem ipsum dolor sit amet


** TODO consectetuer adipiscing elit
   Sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna
   aliquam erat volutpat.
   SCHEDULED: <2012-08-09 Thu 20:30>
** TODO  quis nostrud exerci tation ullamcorper
   SCHEDULED: <2012-08-08 Wed 10:30>
   Nam liber tempor cum soluta nobis eleifend option congue nihil
   imperdiet doming id quod mazim placerat facer possim assum.
** TODO Ut wisi enim ad minim veniam...

--- tidier ---
* Lorem ipsum dolor sit amet
** TODO  quis nostrud exerci tation ullamcorper
   SCHEDULED: <2012-08-08 Wed 10:30>
   Nam liber tempor cum soluta nobis eleifend option congue nihil
   imperdiet doming id quod mazim placerat facer possim assum.

** TODO consectetuer adipiscing elit
   SCHEDULED: <2012-08-09 Thu 20:30>
   Sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna
   aliquam erat volutpat.

** TODO Ut wisi enim ad minim veniam...

Re: [O] Exporting inline code sections

[Ken Williams]

> -Original Message-
> From: Bastien Guerry [mailto:bastiengue...@googlemail.com]
> Sent: Monday, August 13, 2012 4:56 PM
> Ken Williams  writes:
>
> > FWIW, I just downloaded 7.8.11 and confirmed that the problem still
> > exists there.
>
> Now fixed in git, thanks.
>

Just tested it, works great, thanks.

 -Ken

CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended 
recipient(s) and may contain confidential and privileged information. Any 
unauthorized review, use, disclosure or distribution of any kind is strictly 
prohibited. If you are not the intended recipient, please contact the sender 
via reply e-mail and destroy all copies of the original message. Thank you.

Re: [O] [babel, ess] How can I make S-RET to be multi-session friendly?

[Eric Schulte]

Andrew Young  writes:

> Hello All,
>

Hi Andrew,

>
> Well, despite being relatively new to elisp, I've decided to take a
> crack at one of your problems. I'm not too sure what is causing the
> strange behaviour of the session property, but I have some thoughts on
> getting that one function working.
>

Thanks for sending this along, unfortunately ob-R.el is currently
without a core maintainer, so I'm not sure who on list would have the
expertise to review your submission.  Although hopefully those
experiencing the problem can at least check if it works for them.

>
> Bear with me :-)
>
> It seems that for me, the inferior ess process is not being properly
> associated with the src edit buffer.  It is being set correctly by
> org-babel-R-associate-session, and then being set a second time
> incorrectly by org-babel-edit-prep:R.  Commenting out line 5 in
> org-babel-edit-prep:R seems to fix this issue, although I'm honestly
> not sure if or what it breaks.  Everything seems ok for me, but ymmv.
>
> Heres the change:
> #+begin_src emacs-lisp
>   (defun org-babel-edit-prep:R (info)
> (let ((session (cdr (assoc :session (nth 2 info)
>   (when (and session (string-match "^\\*\\(.+?\\)\\*$" session))
> (save-match-data (org-babel-R-initiate-session session nil))
> ;;(setq ess-local-process-name (match-string 1 session)
> )))
> #+end_src
>

Perhaps replacing the commented "setq ess-local-process-name" line with
ess-switch-process could solve this problem?  Could the process name be
found programatically, perhaps using the regexp solution above.

>
> Is there any one having such issues, or who can weigh in on what
> exactly is happening here?
>
> Without making the above change, it is possible to manually attach an
> ess process to the current src buffer by using the command:
>
> C-c C-s (ess-switch-process)
>
> You'll have to specify the process name, rather than the buffer name,
> and the session must have already been started. From here all ESS
> functions should work. For example, calling:
>
> C-c C-z (ess-switch-to-end-of-ESS)
>
> will open the session buffer.
>
> I've implemented a variation of the function you mentioned, which uses
> the inferior process discussed above.  It should do something at least
> remotely like the function you were asking for, and will work with
> babel sessions, as long as the ess process is associated
> properly. I've made one change worth mentioning: the function now
> prompts for a buffer name to set up on if no ess process is associated,
> instead of only and always using *R*.
>
> Try it out, and let me know what you think.  Of course feel free to
> tweak & share!  This is my real first dive into lisp, so if anyone has
> anything to share please do.
>
> #+begin_src emacs-lisp
>   (defun my-ess-eval ()
> (interactive)
> (update-ess-process-name-list)
> (if (not (ess-make-buffer-current))
> ;; Obtain the target ess session
> (let ((session
>(read-string "Use session: "
> (let ((proc (get-process 
> ess-current-process-name)))
>   (if (processp proc)
>   (buffer-name (process-buffer proc)))
>   ;; Obtain buffer matching session
>   (if (not (get-buffer session))
>   ;; If there is no buffer, create a new one
>   (save-excursion
> (inferior-ess)
> (rename-buffer session)))
>   (setq ess-local-process-name
> (process-name (get-buffer-process session)
> (ess-make-buffer-current)
> (if (and transient-mark-mode mark-active)
> (call-interactively 'ess-eval-region)
>   (call-interactively 'ess-eval-line-and-step)))
>
> (add-hook 'ess-mode-hook
>   '(lambda ()
>  (local-set-key [(shift return)] 'my-ess-eval)))
>
> (add-hook 'inferior-ess-mode-hook
>   '(lambda ()
>  (local-set-key [C-up] 'comint-previous-input)
>  (local-set-key [C-down] 'comint-next-input)))
>
> (add-hook 'Rnw-mode-hook
>   '(lambda ()
>  (local-set-key [(shift return)] 'my-ess-eval)))
>
>   (require 'ess-site)
>
> #+end_src
>

This looks good to me, perhaps it should be added to the Worg page on
using R with Org-mode?

http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html

Thanks,

>
> Sincerely,
> Andrew Young
>

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

Re: [O] A tidy file maketh a tidy mind?

[Eric Schulte]

'Mash  writes:

> Morning,
>
> I just want to know if there is there exists a 'tidy' module/command
> that can be run on a file to tidy it?
>
> I often find myself going back and adding extra line breaks and
> padding, and wondering if there exists something that can do this for
> me?
>

While this doesn't exist currently, it should be fairly easy to
implement a set of rules which operate over the parsed file
representation generated by org-element.  This may be used to convert an
Org-mode buffer into an elisp list, manipulate the list, and then insert
the results as text back into a new buffer.

The code could look something like the following

;; -*- emacs-lisp -*-
(let ((buf (org-element-parse-buffer))) ;; convert current buffer to ELisp
  (dolist (rule cleanup-rules) ;; run cleanup transformations on the buffer
(setq buf (funcall rule buf)))
  (delete-region (point-min) (point-max)) ;; replace the buffer contents
  (insert (org-element-interpret-data buf))) ;; with the cleaned results

The only catch would be deciding what to add to the cleanup-rules.

Also, since Org-mode is plain text, I bet a couple of lines of sed or
perl could get you most of the way to a clean buffer.

Best,

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

Re: [O] Org Build System (aka Makefile)

[Eric Schulte]

Achim Gratz  writes:
>
> You found the time and energy to edit Makefile and targets.mk, so
> presumably you might be able to edit local.mk as well as I suggested
> numerous times.  So please go ahead and actually do it and then after
> you've used elint for a while tell me how useful you find it from your
> experience and if there are other things that need attending aside from
> that depth limit.

Will do. Thanks,

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

Re: [O] Activate/deactivate export of inlinetasks with #+OPTIONS

[Rasmus]

Rasmus  writes:

> To reach an Org-ish solution I wrote the following trivial
> advice+extra,
> which allows #+OPTIONS: inline:t or #+OPTIONS: inline:nil.  It works
> only with the new exporter (which is amazing!!!).

This solution is better as it's backend-agnostic: 

#+BEGIN_SRC emacs-lisp
  (add-to-list 'org-export-options-alist
   '(:with-inlinetasks nil "inline" org-export-with-inlinetasks))

  (defcustom org-export-with-inlinetasks t
"Non-nil means include INLINETASKS keywords in export.
  When nil, remove all these keywords from the export."
:group 'org-export-general
:type 'boolean)

  (defun org-e-inlinetask-p (inlinetask back-end info)
"Return an inlinetask string if :with-inlinetasks is t"
(if (plist-get info :with-inlinetasks)
inlinetask
""))

  (add-to-list 'org-export-filter-inlinetask-functions 'org-e-inlinetask-p)

  ;; (defadvice org-e-latex-inlinetask (after org-e-export-inlinetask-p)
  ;;   "Return an inlinetask string if :with-inlinetasks is t otherwise
  ;;   return nothing"
  ;;   (if (not (plist-get info :with-inlinetasks))
  ;;   (setq ad-return-value "")))

  ;; (ad-activate 'org-e-latex-inlinetask)

#+END_SRC

-- 
I almost cut my hair, it was happened just the other day

[O] Activate/deactivate export of inlinetasks with #+OPTIONS

[Rasmus]

Hi list,

When writing documents, I think in terms of LaTeX.  There, a common
option in `draft'.  In orgmode inlinetasks is a draft-thingy to me.  I
want to easily remove inlinetasks before exporting a final (that merely
means `pretty') version.

To reach an Org-ish solution I wrote the following trivial advice+extra,
which allows #+OPTIONS: inline:t or #+OPTIONS: inline:nil.  It works
only with the new exporter (which is amazing!!!).

I'm hoping someone else could make use of it (although it is truly
trivial, but not being a programmer I appreciate finding `easy'
solutions on the internets).

#+BEGIN_SRC emacs-lisp
(add-to-list 'org-export-options-alist
 '(:with-inlinetasks nil "inline" org-export-with-inlinetasks))

(defcustom org-export-with-inlinetasks t
  "Non-nil means include INLINETASKS keywords in export.
When nil, remove all these keywords from the export."
  :group 'org-export-general
  :type 'boolean)

(defadvice org-e-latex-inlinetask (after org-e-export-inlinetask-p)
  "Return an inlinetask string if :with-inlinetasks is t otherwise
  return nothing"
  (if (not (plist-get info :with-inlinetasks))
  (setq ad-return-value "")))

(ad-activate 'org-e-latex-inlinetask)
#+END_SRC

If this is of high enough standards it could perhaps be added to the
worg. . .

–Rasmus

-- 
In theory, practice and theory are the same. In practice they are not

Re: [O] Possible bug with org-add-node in org 7.8.11

[Thomas Wallrafen]

Hi Bastien,

On Tue, Aug 14, 2012 at 01:10:11PM +0200, Bastien wrote:
> Hi Thomas,
> 
> Thomas Wallrafen  writes:
> 
> > I recently discovered a possible bug in org-mode (recent git checkout,
> > 7.8.11-482-g570e30-git) and GNU Emacs 24.1.50.1 from emacs.naquadah.org
> > on Debian Squeeze when using org-add-note (bound to C-c C-z by default).
> 
> Fixed, thanks.

thank you very much for fixing it so fast!

Bye,

Thomas

Re: [O] Possible bug with org-add-node in org 7.8.11

[Bastien]

Hi Thomas,

Thomas Wallrafen  writes:

> I recently discovered a possible bug in org-mode (recent git checkout,
> 7.8.11-482-g570e30-git) and GNU Emacs 24.1.50.1 from emacs.naquadah.org
> on Debian Squeeze when using org-add-note (bound to C-c C-z by default).

Fixed, thanks.

-- 
 Bastien

[O] Possible bug with org-add-node in org 7.8.11

[Thomas Wallrafen]

Hello all,

I recently discovered a possible bug in org-mode (recent git checkout,
7.8.11-482-g570e30-git) and GNU Emacs 24.1.50.1 from emacs.naquadah.org
on Debian Squeeze when using org-add-note (bound to C-c C-z by default).

Given a simple file test.org with the content

* test

And running org-add-note whith the content
#+begin_example
test
#+end_example

will result in the following buffer content:
* test
- Note taken on [2012-08-14 Tue 12:57] \\
  test note
#+end_example

missing the #+begin_example.

Is anyone able to reproduce this?

Bye,

Thomas

Re: [O] org-link minor mode

[Christopher J. White]

This is pretty cool, Sean.  One issue I'm having is that it does not 
properly handle "breaking" the link:


"[[link][description]]" is displayed as "link", with the cursor after 
link.  In org-mode, if I hit backspace, it deletes the trailing ']' and 
changes the display to "[[link][description]".  But using this minor 
mode, it keeps still just shows "link".  If I turn minor mode off again, 
it's clear that the trailing bracket was deleted.


I took a look at the org source regarding links, but I couldn't quite 
figure out how org does this.  It just calls org-delete-backward-char, 
which doesn't appear to have any magic for links.


Thanks
...cj


On 8/12/12 4:25 PM, Sean O'Halpin wrote:

Hi,

I've been hacking this weekend to try to create a minor mode that
enables org-mode bracket links in modes other than org-mode.

I believe this has been mooted before
(e.g. 
http://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00573.html).


The following codes works for me but I'm sure it could be improved.

I'm an elisp noob so I'd very much appreciate feedback on the approach
I'm taking.  For example, I'm not sure how to prevent turning on
org-link-minor-mode from an org-mode buffer - advice would be welcome.

Regards,
Sean

#+begin_src emacs-lisp

(require 'org)

(define-minor-mode org-link-minor-mode
   "Toggle display of org-mode style bracket links in non-org-mode 
buffers."

   :lighter " org-link"
   (let ((org-link-minor-mode-keywords (list
'(org-activate-bracket-links (0 'org-link t)
 (save-excursion
   (save-match-data
 (goto-char (point-min))
 (if org-link-minor-mode
 (progn
   (font-lock-add-keywords nil org-link-minor-mode-keywords t)
   (set (make-local-variable 'org-descriptive-links)
org-descriptive-links)
   (if org-descriptive-links (add-to-invisibility-spec 
'(org-link)))

   (font-lock-fontify-buffer)
   )
   (progn
 (font-lock-remove-keywords nil org-link-minor-mode-keywords)
 (org-remove-from-invisibility-spec '(org-link))
 (while (re-search-forward org-bracket-link-regexp nil t)
   ;; Remove all org-link properties
   (remove-text-properties (match-beginning 0) (match-end
0) (text-properties-at (match-beginning 0)))
   )
 )
   )

(provide 'org-link-minor-mode)

#+end_src

Re: [O] [ANN] Editable HTML export of Org-mode files

[Bastien]

Rasmus  writes:

> That's very cool!  Good job!  This could be useful.  Would this be
> something that could eventually be used in the Worg?

If there are some good ideas, and if Jason (as the security guy for 
the server) is okay, why not?

-- 
 Bastien

Re: [O] are super-hidden technical blocks required?

[Bastien]

Hi Torsten,

thanks for the mock-ups -- very useful to get a quick overview.

I'm still reluctant to implement what you propose, because the 
two issues (cycling and hiding) are still too intertwined for me.

Here is how I would like the problems:

1. The fact that property drawers with only "technical" properties
   are shown when cycling.

2. The fact that property drawers with only "technical" properties
   are shown altogether.

3. The fact that "technical" properties are shown when unfolding 
   a drawer.

4. The fact that "technical" properties are shown altogether.


We started from (4), moved to (3), then stumbled on (1) and (2).

It seems to me that (4) is fundamental -- other issues depend on it.

It also occurred to me you only want this kind of feature when you 
are actually editing your org file -- not when it is processed by a 
third-part tool or by the Agenda.  Chances are that you don't want
the properties to be always invisible... and editing HIDE_PROPS just
to hide/unhide some properties is not handy.

So I implemented this simple solution, now available in the git repo:

  M-: (setq org-custom-properties '("ID")) RET
  M-x org-toggle-custom-properties-visibility RET

will hide all :ID: properties in the buffer.  The same command again
will show them.  If `org-catch-invisible-edits' is non-nil, trying to 
edit an invisible property will throw a question/error.

I hope this suits most people needs in this thread.

Thanks again for triggering this dicussion!

-- 
 Bastien

Re: [O] [ANN] Editable HTML export of Org-mode files

[Rasmus]

Eric Schulte  writes:

> I've recently put together a web server which runs in Emacs and exports
> local Org-mode files to HTML in such a way that they may be edited from
> within a web browser with the edits saved to local files on disk.  The
> code is available from github.

That's very cool!  Good job!  This could be useful.  Would this be
something that could eventually be used in the Worg?

–Rasmus

-- 
Hooray!

Re: [O] stable links to gnus messages?

[Alan Schmitt]

Bastien  writes:

> Hi Alan,
>
> Alan Schmitt  writes:
>
>> I'm starting to play with org-store-link, and I've noticed that if I
>> create a link to a gnus message, this link will be broken if I move the
>> message to another mailbox. Is it possible to have a stable link that
>> would survive such a move?
>
> You might want to use gnus-registry and the nnregistry backend.

Thanks, that worked great. The only part I'm still trying to figure out
is to find in which group the mail is in (nnregistry is finding it, and
displaying it, but the modeline mentions the old group and not the one
where the message has been moved to). I guess this is also why
displaying the thread does not work.

For the record, here is the settings I've used:

#+begin_src elisp
;; Registry, to allow the finding of messages
;; From 
http://www.gnu.org/software/emacs/manual/html_node/gnus/The-Gnus-Registry.html#The-Gnus-Registry

(setq
 gnus-registry-split-strategy 'majority
 gnus-registry-ignored-groups '(("Junk" t)
("TrainSpam" t)
("notmuch" t)
("Trash" t)
("Chats" t)
("Contacts" t)
("Emailed Contacts" t)
("Notes" t))
 gnus-registry-max-entries nil
 ;; this is the default
 gnus-registry-track-extra '(sender subject))

(gnus-registry-initialize)

(setq gnus-refer-article-method
  '(current
(nnregistry)))
#+end_src

Re: [O] [GSoC] Org-sync v0.2

[Bastien]

Suvayu Ali  writes:

> I thought os is short for org-sync, just like ob is for org-babel?

Indeed, that's the idea.

-- 
 Bastien

Re: [O] Using org-mode as day planner

[Bastien]

Hi John,

I added the option `org-datetree-add-timestamp'.

You can (setq org-datetree-add-timestamp 'inactive)

then use C-c / on date trees to look for entries with
inactive time stamps.

HTH,

-- 
 Bastien

Re: [O] org-link minor mode

[Bastien]

"Sean O'Halpin"  writes:

> I've been hacking this weekend to try to create a minor mode that
> enables org-mode bracket links in modes other than org-mode.
>
> I believe this has been mooted before
> (e.g. http://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00573.html).

Yes.  This might especially be useful in modes where people use
orgstruct as well -- and could well end up being part of orgstruct,
if that's not too invasive.

> The following codes works for me but I'm sure it could be improved.
>
> I'm an elisp noob so I'd very much appreciate feedback on the approach
> I'm taking.  For example, I'm not sure how to prevent turning on
> org-link-minor-mode from an org-mode buffer - advice would be welcome.

Simply use

(unless (derived-mode-p 'org-mode)

on the top of your function?

Also, you might want to check `org-fontify-like-in-org-mode': for any
regexp (including links) that you find in your buffer, you can fontify
it like in org-mode.

HTH,

-- 
 Bastien

Re: [O] A tidy file maketh a tidy mind?

[Bastien]

Hi Mash,

'Mash  writes:

> I just want to know if there is there exists a 'tidy' module/command  that
> can be run on a file to tidy it?

People differ in the way they think their org files are "clean".

Maybe you can start a list of tidyfication routines you use reguarily,
then if we all agree on the core routines that many people use, we can
have a useful function for this -- certainly in org-hacks.org first.

Thanks,

-- 
 Bastien

Re: [O] [ANN] Editable HTML export of Org-mode files

[Bastien]

Eric Schulte  writes:

> The code is fairly new so there are likely some kinks to be worked out
> (backup your files before editing them with this web-server), but the
> implementation is very simple and should be easy to modify.  See the
> README for information on how to make use of elnode's authentication
> system, or how to have web edits automatically committed to a local
> version control system.
>
> Comments and patches are welcome.

One single comment: that's *great* stuff.

Thanks!

-- 
 Bastien

Re: [O] [PATCH 07/10] org-taskjuggler: make project umbrella task optional

[Bastien]

Hi Christian,

Christian Egli  writes:

> OK this clears it up. So basically all the patches are fine from my pov.
> Thanks again.

Thanks for confirming.

I'll commit the patches when the FSF papers arrive.

Best,

-- 
 Bastien

Re: [O] stable links to gnus messages?

[Bastien]

Hi Alan,

Alan Schmitt  writes:

> I'm starting to play with org-store-link, and I've noticed that if I
> create a link to a gnus message, this link will be broken if I move the
> message to another mailbox. Is it possible to have a stable link that
> would survive such a move?

You might want to use gnus-registry and the nnregistry backend.

-- 
 Bastien

[O] stable links to gnus messages?

[Alan Schmitt]

Hello,

I'm starting to play with org-store-link, and I've noticed that if I
create a link to a gnus message, this link will be broken if I move the
message to another mailbox. Is it possible to have a stable link that
would survive such a move?

Thanks,

Alan