Re: [O] org-caldav feedback
Torsten Wagner torsten.wag...@gmail.com writes: CC. Since Sogo does not allow a print view. Does someone know how to create a printable weekly calendar which contains org-agenda entries? I barley remember there was a possibility to create a PDF but can't find it anymore There are the cal-tex-* functions which produce tex from diary files. See the info entry on Writing Calendar Files. Also there is a Makefile which uses the cal-tex-* functions to generate hipster style printouts in contrib/scripts/org2hpda. This might serve as an inspiration. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Wish: switch active time-stamps to inactive when CANCELED
Nick Dokos nicholas.do...@hp.com writes: But unfortunately, I know that little of ELISP, that I am not able to implement it by myself :-( Time to learn some then - and there is no better way than scratching your own itch :-) Two days later, no reply so far. I'll give it a shot. Karl, if you are still fiddling to make it work, ignore this posting and keep trying. :) [...] accomplish this with org-after-todo-state-change-hook: Write a function that checks if org-state is CANCELED [...] looks for active timestamps and calls org-toggle-timestamp-type on them. Everything there, so... --8---cut here---start-8--- (defun my-org-active-to-inactive-ts () Toggle type on active timestamp in current heading if state was changed to 'CNCL'. This function is supposed to be called by 'org-after-todo-state-change-hook. This function expects only one active timestamp to be in the headline. (when (string= org-state CNCL) ; 1. (save-excursion ; 2. (save-restriction (widen) (outline-back-to-heading t) ; 3. (narrow-to-region (point) (or (outline-next-heading) (point-max))) (when (re-search-backward (org-re-timestamp 'active) nil t) ; 4. (org-toggle-timestamp-type)) (add-hook 'org-after-todo-state-change-hook 'my-org-active-to-inactive-ts) --8---cut here---end---8--- 1.: Only when org-state is CNCL, do the rest. 2.: We are jumping around and narrowing, so let's save the way things are, first. 3.: Move point to the beginning of the current headline, make sure we only touch it by narrowing to it. If there is no next headline, point-max will do. 4.: regex search for (only) one active timestamp. When there is one, point will end up there and we toggle it. When there is none, search returns nil, nothing happens. Memnon
[O] OT: Learning ELISP (was: Wish: switch active time-stamps to inactive when CANCELED)
* Memnon Anon gegendosenflei...@googlemail.com wrote: Two days later, no reply so far. I'll give it a shot. Karl, if you are still fiddling to make it work, ignore this posting and keep trying. :) Well, the hook in combination with the ARCHIVE tag did resolve my current issue quite nicely. However, I follow ELISP lessons with great pleasure independent of my current issues :-) But thanks to my time budget, it's low priority for now. :-( I did accomplish some advancement in the last weeks. I could fix some if/when issues in my configuration and I do get the feeling that meanwhile, I am able to judge the quality or the side-effects of ELISP snippets I copy/copied from other people. Even this limited knowledge gives me way more power over my Emacs than before. The core of ELISP is not that huge at all. So far, I tend to think that one key aspect of programming in ELISP is knowing, what functions are out there, waiting to be used to accomplish a task. And learning/finding all these handy functions is not trivial to me. Especially in such a huge project like Org-mode. Even more off-topic: I cleaned out some very old things and summarized my Emacs config in (currently) two files.[1] And I am thinking of moving it to Emacs initialization with babel[2] but so far, I am not sure, if there are that many advantages over the current situation. 1. https://github.com/novoid/dot-emacs 2. http://orgmode.org/worg/org-contrib/babel/intro.html#literate-programming -- Karl Voit
Re: [O] colorg: Some news!
Daimrod daim...@gmail.com writes: François Pinard pin...@iro.umontreal.ca writes: ColOrg is a project about real-time collaborative editing of Org files. That's a really cool project! Thanks. Do you plan to keep the server in Python? Or do you think it would be possible to make this in Emacs Lisp only with Elnode[1] for the server-side? Once we get a working solution, the protocol remains the contact point. The server could be replaced using other languages, and new clients may be written for other editors (given they are extensible enough). My goal is quickly getting something usable, so I selected the means that looked fastest to me, and that's how Python got in the picture. Is there any incentive for rewriting the server in Emacs Lisp? For one, even if rather bearable, Emacs Lisp is not my preferred programming language. Moreover, I consider a bit wrong having to rely on an editor for tasks wholly unrelated to editing. Other people are free to have differing opinions, and do that rewrite, however. If I really had more time and less pressure, I would likely have selected Node (JavaScript) to write the server instead of Python. The choice of JSON within the ColOrg communication protocol is a way, for me, to leave that door opened. One not so hidden dream is to bring Org mode a bit closer to Web browsers, if there are ways to do so. François
Re: [O] Problem exporting code
I believe I've figured it out. I must have an old version of 'htmlize' installed somewhere, I 'edebug' traced through the code and fell through to this part: (when lang (if (featurep 'xemacs) (require 'htmlize) (require 'htmlize nil t)) (when (not (fboundp 'htmlize-region-for-paste)) ;; we do not have htmlize.el, or an old version of it (setq lang nil) (message htmlize.el 1.34 or later is needed for source code formatting))) I couldn't manage to set up my load-path to load htmlize 'properly' (is htmlize not able to be loaded via 'load-path' and 'require'?), but after downloading htmlize 1.43 and adding the following to my .emacs, I seem to be in business again: (load-file ~/share/emacs/site-lisp/htmlize/htmlize.el) Thanks everyone. On Mon, Jan 21, 2013 at 1:39 AM, Eric S Fraga e.fr...@ucl.ac.uk wrote: Ken Williams kena...@gmail.com writes: Thanks John. Here's a small org file: Data point: this works just fine for me with both old and new exporters. And I don't even have R installed on this particular system (hadn't realised until now ;-). -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org release_7.9.3d-826-gbe0d87
Re: [O] colorg: Some news!
François Pinard pin...@iro.umontreal.ca writes: Once we get a working solution, the protocol remains the contact point. The server could be replaced using other languages, and new clients may be written for other editors (given they are extensible enough). My goal is quickly getting something usable, so I selected the means that looked fastest to me, and that's how Python got in the picture. Is there any incentive for rewriting the server in Emacs Lisp? For one, even if rather bearable, Emacs Lisp is not my preferred programming language. Moreover, I consider a bit wrong having to rely on an editor for tasks wholly unrelated to editing. Other people are free to have differing opinions, and do that rewrite, however. It's not unlreated to editing, it's for collaborative editing! :) Anyway, I understand and respect your point of view. Moreover, it's nice of you to report on the mailing list, it helps to keep on eye. If I really had more time and less pressure, I would likely have selected Node (JavaScript) to write the server instead of Python. The choice of JSON within the ColOrg communication protocol is a way, for me, to leave that door opened. One not so hidden dream is to bring Org mode a bit closer to Web browsers, if there are ways to do so. -- Daimrod/Greg pgpEc4gg27uJw.pgp Description: PGP signature
Re: [O] org-caldav feedback
Hey David, could you please help me and steer me in the right direction to find the cuprit which makes the caldav calendar lagging an hour compared to the timestamps in org-mode. I use Linux, not sure that might be releated or not. Thanks Torsten On 17 January 2013 20:05, David Engster d...@randomsample.de wrote: Torsten Wagner writes: we just tried org-caldav and it seems to work very nice. We use Sogo http://www.sogo.nu/ and hence David might like to ad Sogo on the list of possible caldav servers. Thanks, that's good news. I'm actually pretty surprised that it works right out of the box. Any plans to sync tasks too? Could you elaborate? What exactly to you mean by 'task'? Everything with an active timestamp should get synced. -David
Re: [O] Prefix arguments, checklists, and lists
Nicolas Goaziou n.goaz...@gmail.com writes: I plan to rewrite C-c C-c using Elements, so the behaviour will slightly change. It will be better to discuss about checkboxes when this change is done. I've got no problem waiting, but it would be a good idea to figure out a consistent non-contradictory key-binding in advance, so you can switch to that when you make the other changes. R Horn rjh...@alum.mit.edu
Re: [O] Problem exporting code
On Mon, Jan 21, 2013 at 9:58 AM, Ken Williams kena...@gmail.com wrote: I believe I've figured it out. I must have an old version of 'htmlize' installed somewhere, I 'edebug' traced through the code and fell through to this part: (when lang (if (featurep 'xemacs) (require 'htmlize) (require 'htmlize nil t)) (when (not (fboundp 'htmlize-region-for-paste)) ;; we do not have htmlize.el, or an old version of it (setq lang nil) (message htmlize.el 1.34 or later is needed for source code formatting))) I couldn't manage to set up my load-path to load htmlize 'properly' (is htmlize not able to be loaded via 'load-path' and 'require'?), but after downloading htmlize 1.43 and adding the following to my .emacs, I seem to be in business again: Awesome that you got it going. Do you still have =(require 'org-install)= in your .emacs? ETA: just checked and you do. I checked as I had an issue with emacs not using the git version of org because I stupidly had =(require 'org-install)= before my load paths! The only thing that stuck out to me was this: =(add-to-list 'load-path ~/share/emacs/site-lisp/org load-path)= Is that the proper syntax? Mine (and just checked the org manual) features this: =(add-to-list 'load-path ~/path/to/orgdir/lisp)=. I know nil about elisp (see what I did there?), but does that extra load-path at the end of the argument do anything? Good luck, John (load-file ~/share/emacs/site-lisp/htmlize/htmlize.el) Thanks everyone. On Mon, Jan 21, 2013 at 1:39 AM, Eric S Fraga e.fr...@ucl.ac.uk wrote: Ken Williams kena...@gmail.com writes: Thanks John. Here's a small org file: Data point: this works just fine for me with both old and new exporters. And I don't even have R installed on this particular system (hadn't realised until now ;-). -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org release_7.9.3d-826-gbe0d87
[O] [PATCH] Bug fix: delete indirect buffer's window only when it exists.
Bug fix: delete indirect buffer's window only when it exists. * org-agenda.el (org-agenda-quit): Delete indirect buffer's window only when it exists. When indirect buffer's window doesn't exist, the original logic will delete the current window. TINYCHANGE diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index f48ff6f..530e79a 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -6989,7 +6989,9 @@ When `org-agenda-sticky' is non-nil, only bury the agenda. (interactive) (if (and (eq org-indirect-buffer-display 'other-window) org-last-indirect-buffer) - (delete-window (get-buffer-window org-last-indirect-buffer))) + (when-let (org-last-indirect-window + (get-buffer-window org-last-indirect-buffer)) + (delete-window org-last-indirect-window))) (if org-agenda-columns-active (org-columns-quit) (if org-agenda-sticky
Re: [O] Problem exporting code
On Mon, Jan 21, 2013 at 10:48 AM, John Hendy jw.he...@gmail.com wrote: Awesome that you got it going. Do you still have =(require 'org-install)= in your .emacs? ETA: just checked and you do. I checked as I had an issue with emacs not using the git version of org because I stupidly had =(require 'org-install)= before my load paths! I do have =(require 'org)= in my .emacs. I never really know whether I'm supposed to do 'org or 'org-install, but this seems to get the ball rolling! The only thing that stuck out to me was this: =(add-to-list 'load-path ~/share/emacs/site-lisp/org load-path)= D'oh! I changed that from a ham-fisted (setq ...) to an (add-to-list ...) call, and I forgot to take out the final argument. Thanks for spotting it. -Ken
Re: [O] [PATCH] Bug fix: delete indirect buffer's window only when it exists.
Muchenxuan Tong writes: Bug fix: delete indirect buffer's window only when it exists. * org-agenda.el (org-agenda-quit): Delete indirect buffer's window only when it exists. Introduces a new bug: when-let is not defined in GNU Emacs. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
[O] #+PROPERTY documentation
Hi, It would be nice if the documentation mentioned the need to reparse the org buffer with `C-c C-c' when a property is set with #+PROPERTY. (info (org) Property syntax) And, IMO, it should also be mentioned here: (info (org) Buffer-wide header arguments). A simple footnote like the one present here: (info (org) Tag inheritance) should be sufficient. (1) As with all these in-buffer settings, pressing `C-c C-c' activates any changes in the line. -- Daimrod/Greg pgplZQR3DFgvj.pgp Description: PGP signature
Re: [O] org-caldav feedback
Torsten Wagner writes: Hey David, could you please help me and steer me in the right direction to find the cuprit which makes the caldav calendar lagging an hour compared to the timestamps in org-mode. It's difficult. I will need to add some (optional) excessive debugging output for seeing what's happening. Or maybe you could provide an account on some server running SUGo so that I can debug this myself. I guess the easy way out would be to add a variable which allows shifting the time by X hours before sending it to the server. But I'd rather avoid that kludge. -David
Re: [O] org-caldav feedback
Torsten Wagner writes: I also noticed the files org-caldav-2094e16.el and org-caldav-backup.org. However, they are stored in my .emacs.d folder. Would it make sens to have an option to save them relatively to the org-file? E.g. relative to the path set in org-caldav-files? That would help to keep infos together and might be even a security concern (e.g., you might forget to move or delete backup infos in .emacs.d)!? Just adapt the variables org-caldav-backup-file and org-caldav-save-directory. SOGo calendars allow to set events and tasks (not sure whether tasks are part of the caldav specs). From what I can say they differ only in the fact that a task has a certain deadline and can be marked done. Thus, this would be equivalent to a TODO DEADLINE entry in org-mode I'm not very familiar with the VTODO stuff. It doesn't make much of a difference as far as CalDAV is concerned, but the import/export will surely be tricky. For now, I'll concentrate on making the existing features more stable. -David
Re: [O] org-caldav feedback
Torsten Wagner writes: You might can try http://sogo-demo.inverse.ca/SOGo/dav/sogo1/Calendar/personal/ which is the demo account of the Sogo. Thanks. That'll work. After a bit of fiddling it seems that SOGo really really wants a timezone definition. I have no idea how those can be generated on-the-fly. I have a hunch you have to hard-code them. Anyway, you can put the definition you need into org-caldav-calendar-preamble. But first you need the correct one. For getting it, just create an event in your calendar. Then run org-caldav-sync and it should be put into your org-caldav-inbox. Then, evaluate (pop-to-buffer (org-caldav-get-event ID)) where you have replaced ID with the ID of the event. You should see a buffer with the iCalendar entry in it. Then copypaste everything from BEGIN:VCALENDAR to END:VTIMEZONE into org-caldav-calendar-preamble. For example, for Europe/Berlin it now seems to work with (setq org-caldav-calendar-preamble BEGIN:VCALENDAR PRODID:-//Inverse inc./SOGo 2.0.3a//EN VERSION:2.0 BEGIN:VTIMEZONE TZID:Europe/Berlin X-LIC-LOCATION:Europe/Berlin BEGIN:DAYLIGHT TZOFFSETFROM:+0100 TZOFFSETTO:+0200 TZNAME:CEST DTSTART:19700329T02 RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:+0200 TZOFFSETTO:+0100 TZNAME:CET DTSTART:19701025T03 RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU END:STANDARD END:VTIMEZONE ) If it works for you with such a timezone definition, it'd be interesting to know if SOGo needs all of that or if you could drop most of this stuff. -David
Re: [O] OT: Learning ELISP
I am a huge advocate of using org files and literate programming in your config files. A few reasons why: - Makes it easy to logically group sections of your init and configuration - Agenda tags search on your initialization file? Yes please! Extremely useful for those cross-cutting bits. I have tags like keybinding, osx and linux, and working on others as appropriate. - Add TODOs to your init file. Here is my example, but I stand on the shoulders of giants: https://github.com/jonnay/emagicians-starter-kit __ Jonathan Arkell Sr. Developer Inspired By Drum Bass, Scheme, Kawaii p. 403.206.4377 1011 9th Ave SE, Suite 300 Calgary, AB, Canada T2G 0Y4 jonath...@criticalmass.com criticalmass.com On 21/01/13 4:39 AM, Karl Voit devn...@karl-voit.at wrote: * Memnon Anon gegendosenflei...@googlemail.com wrote: Two days later, no reply so far. I'll give it a shot. Karl, if you are still fiddling to make it work, ignore this posting and keep trying. :) Well, the hook in combination with the ARCHIVE tag did resolve my current issue quite nicely. However, I follow ELISP lessons with great pleasure independent of my current issues :-) But thanks to my time budget, it's low priority for now. :-( I did accomplish some advancement in the last weeks. I could fix some if/when issues in my configuration and I do get the feeling that meanwhile, I am able to judge the quality or the side-effects of ELISP snippets I copy/copied from other people. Even this limited knowledge gives me way more power over my Emacs than before. The core of ELISP is not that huge at all. So far, I tend to think that one key aspect of programming in ELISP is knowing, what functions are out there, waiting to be used to accomplish a task. And learning/finding all these handy functions is not trivial to me. Especially in such a huge project like Org-mode. Even more off-topic: I cleaned out some very old things and summarized my Emacs config in (currently) two files.[1] And I am thinking of moving it to Emacs initialization with babel[2] but so far, I am not sure, if there are that many advantages over the current situation. 1. https://github.com/novoid/dot-emacs 2. http://orgmode.org/worg/org-contrib/babel/intro.html#literate-programming -- Karl Voit The information contained in this message is confidential. It is intended to be read only by the individual or entity named above or their designee. If the reader of this message is not the intended recipient, you are hereby notified that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete or destroy any copy of this message.
Re: [O] Problem exporting code
On Mon, Jan 21, 2013 at 11:45 AM, Ken Williams kena...@gmail.com wrote: On Mon, Jan 21, 2013 at 10:48 AM, John Hendy jw.he...@gmail.com wrote: Awesome that you got it going. Do you still have =(require 'org-install)= in your .emacs? ETA: just checked and you do. I checked as I had an issue with emacs not using the git version of org because I stupidly had =(require 'org-install)= before my load paths! I do have =(require 'org)= in my .emacs. I never really know whether I'm supposed to do 'org or 'org-install, but this seems to get the ball rolling! I don't think this is needed anymore, and in this thread I thought it might even cause potential problems, but I could be wrong! - http://lists.gnu.org/archive/html/emacs-orgmode/2012-10/msg00030.html The only thing that stuck out to me was this: =(add-to-list 'load-path ~/share/emacs/site-lisp/org load-path)= D'oh! I changed that from a ham-fisted (setq ...) to an (add-to-list ...) call, and I forgot to take out the final argument. Thanks for spotting it. It'd be interesting to know how htmlize didn't get updated. Is that provided via org or your emacs variant? Or it'd also be interesting to know if there were multiple versions and the wrong one had been pulled in. Obviously, the main point is that you've got things doing what you want... but as a sort of meticulous engineering sort, it'd still be nice to get closure for any future mailing list hunters :) Best regards, John -Ken
Re: [O] #+PROPERTY documentation
On Mon, Jan 21, 2013 at 12:41 PM, Daimrod daim...@gmail.com wrote: Hi, It would be nice if the documentation mentioned the need to reparse the org buffer with `C-c C-c' when a property is set with #+PROPERTY. (info (org) Property syntax) As in adding to the header arguments? Yeah, probably wouldn't hurt, though it is, as stated below, documented that *any* change to the header arguments requires C-c C-c. On a side note, is there the possibility for normal users to submit git based changes to the manual? I know how to do this for Worg, but I'd be happy to update stuff in the manual, too, when I catch them. These sorts of things could be tweaked by the finder and it would save the maintenance team a bit -- just scan the commit and notes for rationale and accept. John And, IMO, it should also be mentioned here: (info (org) Buffer-wide header arguments). A simple footnote like the one present here: (info (org) Tag inheritance) should be sufficient. (1) As with all these in-buffer settings, pressing `C-c C-c' activates any changes in the line. -- Daimrod/Greg
Re: [O] #+PROPERTY documentation
John Hendy jw.he...@gmail.com writes: On Mon, Jan 21, 2013 at 12:41 PM, Daimrod daim...@gmail.com wrote: Hi, It would be nice if the documentation mentioned the need to reparse the org buffer with `C-c C-c' when a property is set with #+PROPERTY. (info (org) Property syntax) As in adding to the header arguments? Yeah, probably wouldn't hurt, though it is, as stated below, documented that *any* change to the header arguments requires C-c C-c. On a side note, is there the possibility for normal users to submit git based changes to the manual? I know how to do this for Worg, but I'd be happy to update stuff in the manual, too, when I catch them. These sorts of things could be tweaked by the finder and it would save the maintenance team a bit -- just scan the commit and notes for rationale and accept. Sure, one can modify the file doc/org.texi. And you're right, I should have submit a patch. John And, IMO, it should also be mentioned here: (info (org) Buffer-wide header arguments). A simple footnote like the one present here: (info (org) Tag inheritance) should be sufficient. (1) As with all these in-buffer settings, pressing `C-c C-c' activates any changes in the line. -- Daimrod/Greg -- Daimrod/Greg pgpQh8xnK3Ubb.pgp Description: PGP signature
[O] html export list indentation wrong with comments
Recent git. Commenting out a list item works properly, but exporting does not. Export of subtree to HTML. === * asdf 1) top level 2) another more - indented # - necessary to comment out this other indented list # # without ability to comment it out in place, we wouldn't # know what we were commenting out 3) top level -- NOT :( - works fine in ascii (except for the extra blank line) === Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is no hope without action.
Re: [O] Problem exporting code
On Mon, Jan 21, 2013 at 4:16 PM, John Hendy jw.he...@gmail.com wrote: On Mon, Jan 21, 2013 at 11:45 AM, Ken Williams kena...@gmail.com wrote: On Mon, Jan 21, 2013 at 10:48 AM, John Hendy jw.he...@gmail.com wrote: Awesome that you got it going. Do you still have =(require 'org-install)= in your .emacs? ETA: just checked and you do. I checked as I had an issue with emacs not using the git version of org because I stupidly had =(require 'org-install)= before my load paths! I do have =(require 'org)= in my .emacs. I never really know whether I'm supposed to do 'org or 'org-install, but this seems to get the ball rolling! I don't think this is needed anymore, and in this thread I thought it might even cause potential problems, but I could be wrong! - http://lists.gnu.org/archive/html/emacs-orgmode/2012-10/msg00030.html The only thing that stuck out to me was this: =(add-to-list 'load-path ~/share/emacs/site-lisp/org load-path)= D'oh! I changed that from a ham-fisted (setq ...) to an (add-to-list ...) call, and I forgot to take out the final argument. Thanks for spotting it. It'd be interesting to know how htmlize didn't get updated. Is that provided via org or your emacs variant? In my case, version 1.23a was provided by Aquamacs: /Applications/Writing/Aquamacs.app/Contents/Resources/lisp/aquamacs/htmlize.el It's been a while since I've used this machine, so I'd updated to the latest Aquamacs, but it looks like Aquamacs itself hasn't seen a release in over a year. That's probably part of the problem. I wonder if there's something else filling the niche these days? -Ken
Re: [O] #+PROPERTY documentation
Daimrod daim...@gmail.com writes:
John Hendy jw.he...@gmail.com writes:
On Mon, Jan 21, 2013 at 12:41 PM, Daimrod daim...@gmail.com wrote:
Hi,
It would be nice if the documentation mentioned the need to reparse the
org buffer with `C-c C-c' when a property is set with #+PROPERTY.
(info (org) Property syntax)
As in adding to the header arguments? Yeah, probably wouldn't hurt,
though it is, as stated below, documented that *any* change to the
header arguments requires C-c C-c.
On a side note, is there the possibility for normal users to submit
git based changes to the manual? I know how to do this for Worg, but
I'd be happy to update stuff in the manual, too, when I catch them.
These sorts of things could be tweaked by the finder and it would save
the maintenance team a bit -- just scan the commit and notes for
rationale and accept.
Sure, one can modify the file doc/org.texi. And you're right, I should
have submit a patch.
John
And, IMO, it should also be mentioned here:
(info (org) Buffer-wide header arguments).
A simple footnote like the one present here:
(info (org) Tag inheritance) should be sufficient.
(1) As with all these in-buffer settings, pressing `C-c C-c'
activates any changes in the line.
So, here is a patch for this:
From 09e569a651e77e8f2c1c2d1f0a285c69688fbd05 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Gr=C3=A9goire=20Jadi?= gregoire.j...@gmail.com
Date: Mon, 21 Jan 2013 23:45:47 +0100
Subject: [PATCH] add footnote to recall the user to refresh the org buffer
when settings are changed.
---
doc/org.texi |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 61f1ee5..c2bdd58 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -4954,7 +4954,9 @@ publishers and the number of disks in a box like this:
@end example
If you want to set properties that can be inherited by any entry in a
-file, use a line like
+file, use a line like@footnote{As
+with all these in-buffer settings, pressing @kbd{C-c C-c} activates any
+changes in the line.}
@cindex property, _ALL
@cindex #+PROPERTY
@example
@@ -13252,7 +13254,9 @@ of @code{#+PROPERTY:} lines placed anywhere in an Org mode file (see
For example the following would set @code{session} to @code{*R*}, and
@code{results} to @code{silent} for every code block in the buffer, ensuring
that all execution took place in the same session, and no results would be
-inserted into the buffer.
+inserted into the buffer.@footnote{As
+with all these in-buffer settings, pressing @kbd{C-c C-c} activates any
+changes in the line.}
@example
#+PROPERTY: session *R*
--
1.7.10.4
--
Daimrod/Greg
pgp6BspWNmlxz.pgp
Description: PGP signature
Re: [O] Problem exporting code
Ken Williams kena...@gmail.com writes: I believe I've figured it out. I must have an old version of 'htmlize' installed somewhere, I 'edebug' traced through the code and fell through to this part: Glad you sorted it! I couldn't manage to set up my load-path to load htmlize 'properly' (is htmlize not able to be loaded via 'load-path' and 'require'?), but after downloading htmlize 1.43 and adding the following to my .emacs, I seem to be in business again: (load-file ~/share/emacs/site-lisp/htmlize/htmlize.el) Thanks everyone. But htmlize.el (version 1.43 currently) is distributed within org in the contrib directory. It would be more straightforward to add (add-to-list 'load-path [PATH TO ORG]/contrib/lisp/) to your configuration. This does beg the question of whether components in the main org lisp directory should depend on items in the contrib directory... but I will leave that for another day ;-) -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org release_7.9.3d-837-ge37613
Re: [O] #+PROPERTY documentation
On Mon, Jan 21, 2013 at 4:35 PM, Daimrod daim...@gmail.com wrote: John Hendy jw.he...@gmail.com writes: On Mon, Jan 21, 2013 at 12:41 PM, Daimrod daim...@gmail.com wrote: Hi, It would be nice if the documentation mentioned the need to reparse the org buffer with `C-c C-c' when a property is set with #+PROPERTY. (info (org) Property syntax) As in adding to the header arguments? Yeah, probably wouldn't hurt, though it is, as stated below, documented that *any* change to the header arguments requires C-c C-c. On a side note, is there the possibility for normal users to submit git based changes to the manual? I know how to do this for Worg, but I'd be happy to update stuff in the manual, too, when I catch them. These sorts of things could be tweaked by the finder and it would save the maintenance team a bit -- just scan the commit and notes for rationale and accept. Sure, one can modify the file doc/org.texi. And you're right, I should have submit a patch. Wasn't criticizing, for the record :) I actually didn't know one could do that! Glad I learned something, and hopefully I can give back to Org more, now! John John And, IMO, it should also be mentioned here: (info (org) Buffer-wide header arguments). A simple footnote like the one present here: (info (org) Tag inheritance) should be sufficient. (1) As with all these in-buffer settings, pressing `C-c C-c' activates any changes in the line. -- Daimrod/Greg -- Daimrod/Greg
Re: [O] Problem exporting code
Aloha Ken, Ken Williams kena...@gmail.com writes: It's been a while since I've used this machine, so I'd updated to the latest Aquamacs, but it looks like Aquamacs itself hasn't seen a release in over a year. That's probably part of the problem. I wonder if there's something else filling the niche these days? -Ken You can get emacs binaries for the Mac here: http://emacsformacosx.com/ or, you can get emacs-app from macports. I've used both with good results. hth, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] #+PROPERTY documentation
Aloha Daimrod (Greg), Daimrod daim...@gmail.com writes: So, here is a patch for this: If you add [PATCH] to the email Subject, your patch will be brought to the attention of the developers. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] #+PROPERTY documentation
t...@tsdye.com (Thomas S. Dye) writes: Aloha Daimrod (Greg), Daimrod daim...@gmail.com writes: So, here is a patch for this: If you add [PATCH] to the email Subject, your patch will be brought to the attention of the developers. I didn't know, thanks. All the best, Tom -- Daimrod/Greg pgpRUIidjPMtV.pgp Description: PGP signature
[O] [PATCH] Re: #+PROPERTY documentation
Daimrod daim...@gmail.com writes:
Hi,
It would be nice if the documentation mentioned the need to reparse the
org buffer with `C-c C-c' when a property is set with #+PROPERTY.
(info (org) Property syntax)
And, IMO, it should also be mentioned here:
(info (org) Buffer-wide header arguments).
A simple footnote like the one present here:
(info (org) Tag inheritance) should be sufficient.
(1) As with all these in-buffer settings, pressing `C-c C-c'
activates any changes in the line.
Here is a patch for this:
From 09e569a651e77e8f2c1c2d1f0a285c69688fbd05 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Gr=C3=A9goire=20Jadi?= gregoire.j...@gmail.com
Date: Mon, 21 Jan 2013 23:45:47 +0100
Subject: [PATCH] add footnote to recall the user to refresh the org buffer
when settings are changed.
---
doc/org.texi |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 61f1ee5..c2bdd58 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -4954,7 +4954,9 @@ publishers and the number of disks in a box like this:
@end example
If you want to set properties that can be inherited by any entry in a
-file, use a line like
+file, use a line like@footnote{As
+with all these in-buffer settings, pressing @kbd{C-c C-c} activates any
+changes in the line.}
@cindex property, _ALL
@cindex #+PROPERTY
@example
@@ -13252,7 +13254,9 @@ of @code{#+PROPERTY:} lines placed anywhere in an Org mode file (see
For example the following would set @code{session} to @code{*R*}, and
@code{results} to @code{silent} for every code block in the buffer, ensuring
that all execution took place in the same session, and no results would be
-inserted into the buffer.
+inserted into the buffer.@footnote{As
+with all these in-buffer settings, pressing @kbd{C-c C-c} activates any
+changes in the line.}
@example
#+PROPERTY: session *R*
--
1.7.10.4
--
Daimrod/Greg
pgp3DZz0hzsT0.pgp
Description: PGP signature
Re: [O] MobileOrg status
Just to be clear... this is MobileOrg for IOS the Android version is going strong and is still available via the Play store. On Fri, Jan 18, 2013 at 1:24 AM, Mobile Org mobile...@spandrel.org wrote: Hi Everyone, Here is a quick status update regarding MobileOrg. Several people have stepped in to take over maintaining MobileOrg in place of Richard. His excellent work has gotten the app very far and we look forward to improving it further. We've had a lot of questions regarding getting MobileOrg back in the app store and we intend to do so as soon as possible. We are currently working out all the logistics for the transition to new maintainers and adding support for v1 of the Dropbox API. When the app is back in the store we'll be sure to notify the list for those interested. You can track the status and check out the current code on github: https://github.com/MobileOrg/mobileorg We will be tracking all issues there as well. Feel free to contact us directly if you have any further questions and thanks for the continued interest! -MobileOrg team
Re: [O] Problem exporting code
On Mon, Jan 21, 2013 at 5:02 PM, John Hendy jw.he...@gmail.com wrote: On Jan 21, 2013 4:51 PM, Ken Williams kena...@gmail.com wrote: It's been a while since I've used this machine, so I'd updated to the latest Aquamacs, but it looks like Aquamacs itself hasn't seen a release in over a year. That's probably part of the problem. I wonder if there's something else filling the niche these days? I've been using this: - http://vgoulet.act.ulaval.ca/en/emacs/mac/ Ah! I've been using his Emacs for Windows at work, I didn't notice there was a Mac one too. Thanks for the pointer. -Ken
Re: [O] #+PROPERTY documentation
Daimrod daim...@gmail.com wrote: John Hendy jw.he...@gmail.com writes: On Mon, Jan 21, 2013 at 12:41 PM, Daimrod daim...@gmail.com wrote: Hi, It would be nice if the documentation mentioned the need to reparse the org buffer with `C-c C-c' when a property is set with #+PROPERTY. (info (org) Property syntax) As in adding to the header arguments? Yeah, probably wouldn't hurt, though it is, as stated below, documented that *any* change to the header arguments requires C-c C-c. On a side note, is there the possibility for normal users to submit git based changes to the manual? I know how to do this for Worg, but I'd be happy to update stuff in the manual, too, when I catch them. These sorts of things could be tweaked by the finder and it would save the maintenance team a bit -- just scan the commit and notes for rationale and accept. Sure, one can modify the file doc/org.texi. And you're right, I should have submit a patch. I believe that just as with code changes, doc changes also need FSF copyright assignment. Nick
Re: [O] #+PROPERTY documentation
Nick Dokos writes: I believe that just as with code changes, doc changes also need FSF copyright assignment. The FSF owns the copyright to all of Org, including the documentation. So yes, anything over 20 lines non-trivial chnages needs to be assigned to FSF. 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] Problem exporting code
Ken Williams kena...@gmail.com writes: On Mon, Jan 21, 2013 at 5:02 PM, John Hendy jw.he...@gmail.com wrote: On Jan 21, 2013 4:51 PM, Ken Williams kena...@gmail.com wrote: It's been a while since I've used this machine, so I'd updated to the latest Aquamacs, but it looks like Aquamacs itself hasn't seen a release in over a year. That's probably part of the problem. I wonder if there's something else filling the niche these days? I've been using this: - http://vgoulet.act.ulaval.ca/en/emacs/mac/ Ah! I've been using his Emacs for Windows at work, I didn't notice there was a Mac one too. Thanks for the pointer. Interesting, this Emacs distribution removed Org a few days ago. I'm not certain why the distributor refers to this as a rather drastic measure. From my perspective as a user, whose interests required using the git version of Org from the beginning, the Emacs distribution of Org has been nothing but trouble, leading to perplexing (for me) problems with mixed installs that I would rather have avoided. I've enjoyed reading the mailing list for the last two or three years and in that time can only remember a few times that the Org that ships with Emacs was recommended. Typically, advice on the list recommends using the git version, instead. Installation of the git version is *easy* now, even for someone with my limited skills. I didn't have any luck with the ELPA version when it first came out, but the ELPA system works great and it seems like an ideal channel to distribute Org. So, even a user like me has very little difficulty using a non-Emacs version of Org. I'm sure there are reasons for wanting Org to be distributed with Emacs. Would it be OK for me to ask on the list what they are? All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] [PATCH] Bug fix: delete indirect buffer's window only when it exists.
Achim Gratz Stromeko at nexgo.de writes: Muchenxuan Tong writes: Bug fix: delete indirect buffer's window only when it exists. * org-agenda.el (org-agenda-quit): Delete indirect buffer's window only when it exists. Introduces a new bug: when-let is not defined in GNU Emacs. Regards, Achim. Thanks for pointing out. It's my fault, when-let is defined in slime.el and not the Emacs core library. The following patch should be OK: Bug fix: delete indirect buffer's window only when it exists. * org-agenda.el (org-agenda-quit): Delete indirect buffer's window only when it exists. When indirect buffer's window doesn't exist, the original logic will delete the current window. TINYCHANGE diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index f48ff6f..8b9ae81 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -6989,7 +6989,10 @@ When `org-agenda-sticky' is non-nil, only bury the agenda. (interactive) (if (and (eq org-indirect-buffer-display 'other-window) org-last-indirect-buffer) - (delete-window (get-buffer-window org-last-indirect-buffer))) + (let ((org-last-indirect-window +(get-buffer-window org-last-indirect-buffer))) + (if org-last-indirect-window + (delete-window org-last-indirect-window (if org-agenda-columns-active (org-columns-quit) (if org-agenda-sticky
Re: [O] Problem exporting code
Hi Thomas and all, t...@tsdye.com (Thomas S. Dye) writes: Ken Williams kena...@gmail.com writes: I've been using this: - http://vgoulet.act.ulaval.ca/en/emacs/mac/ Thanks for the pointer, I was not aware of this distribution. Interesting, this Emacs distribution removed Org a few days ago. This is a wrong move. Also, the NEWS entry in http://vgoulet.act.ulaval.ca/pub/emacs/NEWS-mac suggests that Org's maintainers are recommending to install Org as an external package, which is a false statement too. I just wrote to Vincent asking for more details and offering to help to ease his life as a maintainer for this Emacs distribution. I'm not certain why the distributor refers to this as a rather drastic measure. From my perspective as a user, whose interests required using the git version of Org from the beginning, the Emacs distribution of Org has been nothing but trouble, leading to perplexing (for me) problems with mixed installs that I would rather have avoided. The distribution of Org as a built-in package in Emacs is *not* the problem. Installing Org through git or through .tar.gz/.zip on top of the Emacs distribution does not create problems if you follow the instructions in the manual -- I made a special effort to simplify them. The real problem is the ELPA distribution, and this problem is due to the package system not being clever enough to handle both a pre-built and a add-on package in all configs. So I'm seriously questioning the value of having Org as an ELPA package and I'm thinking of removing this possibility until Emacs package install is fixed (Achim is working on this, but it looks like the change will not be in Emacs anytime soon.) I've enjoyed reading the mailing list for the last two or three years and in that time can only remember a few times that the Org that ships with Emacs was recommended. Typically, advice on the list recommends using the git version, instead. The pre-built version is not recommended because it does not need to be -- it is pre-built :) When people write to the list, I recommend them to use the latest .tar.gz/.zip or the Git version because this version often fix the bug they are suffering from. Installation of the git version is *easy* now, even for someone with my limited skills. Yes, and installing the .tar.gz/.zip file is even easier! I didn't have any luck with the ELPA version when it first came out, but the ELPA system works great and it seems like an ideal channel to distribute Org. So, even a user like me has very little difficulty using a non-Emacs version of Org. There are many things I don't like with the current packaging system: - The message when downloading is confusing (package contacting...). - AFAIK users don't have the choice but to have the .el files compiled, which will make backtraces unreadable for bug reporters. Also, if Org is not in Emacs anymore, users will not be able to add (org-agenda ...) in their .emacs.el -- they will have to initialize the package system in .emacs.el before they can call Org functions. *We* will have to tell them... I'm sure there are reasons for wanting Org to be distributed with Emacs. Would it be OK for me to ask on the list what they are? I don't have figures, but I think Emacs is the first channel through wich people happen to discover Org. It is advertized on the Emacs homepage, it is in the Emacs manuals, etc. Also, I consider outline.el to be completely unusable, and Org is first an enhanced version of it, which Emacs strongly needs. I plan to push so that files in Emacs use org.el when they use outline.el. I understand this might be tempting to remove Org from Emacs if it causes installation problems... tempting for long-time power users who know how to install it, tempting for maintainers who don't want to deal with the (heavy) burden of sync'ing with Emacs, and tempting for Emacs maintainers who don't want such a big module in the codebase... but this would be a wrong move. The right thing to do is to simplify Org so that requiring org.el does not take too long, and so that installing it on top of a pre-built install does not create problems. If removing the ELPA channel is the way to go temporarily, let's think about it seriously! All best, -- Bastien
