[O] bug#9695: allowed date range
After investigating further 2011-10-17 --2011-10-30 works but not
2011-10-17--2011-10-30. The regexp for a timestamp is defined in
org-ts-regexp :
\\([0-9]\\{4\\}-[0-9]\\{2\\}-[0-9]\\{2\\}[^\r\n]*?\\)
Shouldn't the trailing space be optional?
--
Ivan Kanis
http://kanis.fr
When you're looking at life
In a strange new room
Maybe drowning soon
Is this the start of it all?
-- Ian Curtis
[O] refile (or copy/move) sections of journal.org to new file
Hi, I'm using org-mode since a few weeks and want to collect and store some entrys from my journal.org in a complete new file. When using C-c C-w (and TAB completion) only 2011 from the actual journal.org will be offered. The same with C-u C-c C-w. Do I need a special part in .emacs? Now there is only this entry: (j Journal entry (file+datetree D:/Eigene Dateien/org/journal.org) * %?\nEntered on %U\n %i\n %a) aklex -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone
Re: [O] org-refile-use-outline-path question
Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: Hi Arun, Arun Persaud wrote: I use the following settings to refile tasks (setq org-refile-use-outline-path 'file) (setq org-refile-targets '((org-agenda-files . (:maxlevel . 5 this has the nice effect that I can refile across different files, which I do use every now and then. For this I use: file/level1/level2/... However mostly I refile to the same file and therefore I wish I could just use something like: level1/level2/... and it would refile using the current file, which at the moment doesn't work for me (at least the level1s of the current file are not part of the autocomplete, only files are). Is there a way that this can be done or can this be added? Not that I know of. I had the same wish, with eventually `.' or something like that to denote the local file. But it's still on the TODO lists... Add an extra entry to org-refile-targets indicating the current file should be valid for refiling. I use --8---cut here---start-8--- (setq org-refile-targets (quote ((nil :maxlevel . 9) (org-agenda-files :maxlevel . 9 --8---cut here---end---8--- You'll still have to specify the current file in the path though with your setup. Regards, Bernt
Re: [O] Feature idea: show last log entry
Bernt Hansen be...@norang.ca writes: I log stuff in :LOGBOOK: with the items reversed so the newest is always on top. SPC on a task in the agenda opens the task including the drawer so I can see the details for any given task. Or in that case you should be able to type E in the agenda and see it also. John
Re: [O] Ways to make org feasible for huge files
Marcelo de Moraes Serpa celose...@gmail.com writes: Wow.. this worked Torsten. Thank you. I wonder why this happens... linum-mode works with overlays to embed the numbers at the beginnig of lines. Overlays are very flexible but not too efficient, you don't want to have too many of them. Looking at linum.el, it seems it already does pooling of overlays in order not to create one overlay for any line, but I'm not sure. Could you please do M-: (length linum-overlays) RET in that large org file with linum-mode enabled and say what it returns to satisfy my curiosity? Bye, Tassilo
Re: [O] bug#9695: allowed date range
Ivan Kanis ivan.ka...@googlemail.com writes:
Hi!
After investigating further 2011-10-17 --2011-10-30 works but not
2011-10-17--2011-10-30. The regexp for a timestamp is defined in
org-ts-regexp :
\\([0-9]\\{4\\}-[0-9]\\{2\\}-[0-9]\\{2\\}[^\r\n]*?\\)
Shouldn't the trailing space be optional?
In your regex, there is no trailing whitespace, but are right that it is
in the original definition.
,[ C-h v org-ts-regexp RET ]
| org-ts-regexp is a variable defined in `org.el'.
| Its value is
| \\([0-9]\\{4\\}-[0-9]\\{2\\}-[0-9]\\{2\\} [^\r\n]*?\\)
|^
`
Strangely, that timestamp regex didn't change for 3 years...
Oh, now I see what's wrong. All time stamps consist of the date and
then the day's name abbreviation, which is missing with your example.
Correct would be
2011-10-17 Mon--2011-10-30 Sun
Bye,
Tassilo
Re: [O] do it today, or well, tomorrow
Am 12.10.2011 22:25, schrieb John Wiegley: Andrea Crotti andrea.crott...@gmail.com writes: On 10/12/2011 03:54 PM, Dave Abrahams wrote: Binding `org-agenda-date-later' to a key like `f' ought to work out for you. 'f' is already bound to next-week, and it's also quite useful. I bind M-n/p to next/perv-week/day/etc. John Hi John, I think I have read somewhere that you wrote a function which does the following: If a todos schedule date is more than one day in the past it will be scheduled automatically to today when using the function to move the schedule forward for one day. Is that right and if yes could you share it please? Best, Rainer
Re: [O] bug#9695: allowed date range
Tassilo Horn tass...@member.fsf.org writes:
Ivan Kanis ivan.ka...@googlemail.com writes:
Hi!
After investigating further 2011-10-17 --2011-10-30 works but not
2011-10-17--2011-10-30. The regexp for a timestamp is defined in
org-ts-regexp :
\\([0-9]\\{4\\}-[0-9]\\{2\\}-[0-9]\\{2\\}[^\r\n]*?\\)
Shouldn't the trailing space be optional?
In your regex, there is no trailing whitespace, but are right that it is
in the original definition.
,[ C-h v org-ts-regexp RET ]
| org-ts-regexp is a variable defined in `org.el'.
| Its value is
| \\([0-9]\\{4\\}-[0-9]\\{2\\}-[0-9]\\{2\\} [^\r\n]*?\\)
|^
`
Strangely, that timestamp regex didn't change for 3 years...
Oh, now I see what's wrong. All time stamps consist of the date and
then the day's name abbreviation, which is missing with your example.
Correct would be
2011-10-17 Mon--2011-10-30 Sun
Bye,
Tassilo
Although the day is optional according to the regexp. I would
definitely like to have the regexp with the space optional as well as
there are cases where I want to type the date in directly (not in org
mode for whatever reason). In those cases, it is easy to type
2011-01-01 or whatever but it's not necessarily trivial to determine the
day of the week...
Actually, interesting thought experiment: does org actually do any
consistency checks, comparing the date and the day of the week?
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1
: using Org-mode version 7.7 (release_7.7.380.g54d7df)
Re: [O] bug#9695: allowed date range
Eric S Fraga e.fr...@ucl.ac.uk writes: Hi Eric, Oh, now I see what's wrong. All time stamps consist of the date and then the day's name abbreviation, which is missing with your example. Correct would be 2011-10-17 Mon--2011-10-30 Sun Although the day is optional according to the regexp. I would definitely like to have the regexp with the space optional as well as there are cases where I want to type the date in directly (not in org mode for whatever reason). In those cases, it is easy to type 2011-01-01 or whatever but it's not necessarily trivial to determine the day of the week... Yes, I agree, although you can use org-time-stamp everywhere (in emacs). And you can actually insert timestamps simply by writing 2011-10-13 with the whitespace to make it a valid timestamp. That will be shown as day entry in the agenda, and you might have typed it in using some non-emacs text editor on you phone. Now, back in org-mode, simply S-up and S-down on any number, and et voila, the missing day name abbrev is added automatically. Actually, interesting thought experiment: does org actually do any consistency checks, comparing the date and the day of the week? No, I don't think so. Manipulating and creating timestamps using the provided commands ensures their correctness, but for actual calculation the day names are ignored. It's just for humans. Bye, Tassilo
Re: [O] bug#9695: allowed date range
On 13.10.2011, at 09:57, Tassilo Horn wrote: Eric S Fraga e.fr...@ucl.ac.uk writes: Hi Eric, Oh, now I see what's wrong. All time stamps consist of the date and then the day's name abbreviation, which is missing with your example. Correct would be 2011-10-17 Mon--2011-10-30 Sun Although the day is optional according to the regexp. I would definitely like to have the regexp with the space optional as well as there are cases where I want to type the date in directly (not in org mode for whatever reason). In those cases, it is easy to type 2011-01-01 or whatever but it's not necessarily trivial to determine the day of the week... Yes, I agree, although you can use org-time-stamp everywhere (in emacs). And you can actually insert timestamps simply by writing 2011-10-13 with the whitespace to make it a valid timestamp. That will be shown as day entry in the agenda, and you might have typed it in using some non-emacs text editor on you phone. Now, back in org-mode, simply S-up and S-down on any number, and et voila, the missing day name abbrev is added automatically. Actually, interesting thought experiment: does org actually do any consistency checks, comparing the date and the day of the week? No, I don't think so. Manipulating and creating timestamps using the provided commands ensures their correctness, but for actual calculation the day names are ignored. It's just for humans. Just to confirm, this is correct. - Carsten
Re: [O] do it today, or well, tomorrow
Rainer Stengele rainer.steng...@online.de writes: I think I have read somewhere that you wrote a function which does the following: If a todos schedule date is more than one day in the past it will be scheduled automatically to today when using the function to move the schedule forward for one day. Is that right and if yes could you share it please? That was a feature suggestion made by Dave Abrahams. Hasn't been coded yet, sorry. :( But followup on the thread so Carsten sees it has more supporters! :) Thx, John
Re: [O] bug#9695: allowed date range
On 13.10.2011, at 09:48, Eric S Fraga wrote:
Tassilo Horn tass...@member.fsf.org writes:
Ivan Kanis ivan.ka...@googlemail.com writes:
Hi!
After investigating further 2011-10-17 --2011-10-30 works but not
2011-10-17--2011-10-30. The regexp for a timestamp is defined in
org-ts-regexp :
\\([0-9]\\{4\\}-[0-9]\\{2\\}-[0-9]\\{2\\}[^\r\n]*?\\)
Shouldn't the trailing space be optional?
In your regex, there is no trailing whitespace, but are right that it is
in the original definition.
,[ C-h v org-ts-regexp RET ]
| org-ts-regexp is a variable defined in `org.el'.
| Its value is
| \\([0-9]\\{4\\}-[0-9]\\{2\\}-[0-9]\\{2\\} [^\r\n]*?\\)
|^
`
Strangely, that timestamp regex didn't change for 3 years...
Oh, now I see what's wrong. All time stamps consist of the date and
then the day's name abbreviation, which is missing with your example.
Correct would be
2011-10-17 Mon--2011-10-30 Sun
Bye,
Tassilo
Although the day is optional according to the regexp. I would
definitely like to have the regexp with the space optional as well as
there are cases where I want to type the date in directly (not in org
mode for whatever reason).
I am attaching a patch which will make time stamps without a day name
like 2011-10-12 work correctly. Furthermore, pressing C-c C-c on
a time stamp will fill in or fix the day name.
However, I am not sure if this patch is complete, or if it
has side effects. So it would be good if a few people could
apply it and test it during their daily work for a few weeks,
and then report problems in this thread.
- Carsten
time-stamp-no-space.patch
Description: Binary data
In those cases, it is easy to type
2011-01-01 or whatever but it's not necessarily trivial to determine the
day of the week...
Actually, interesting thought experiment: does org actually do any
consistency checks, comparing the date and the day of the week?
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1
: using Org-mode version 7.7 (release_7.7.380.g54d7df)
Re: [O] do it today, or well, tomorrow
On Thu, Oct 13 2011, John Wiegley wrote: Rainer Stengele rainer.steng...@online.de writes: I think I have read somewhere that you wrote a function which does the following: If a todos schedule date is more than one day in the past it will be scheduled automatically to today when using the function to move the schedule forward for one day. Is that right and if yes could you share it please? That was a feature suggestion made by Dave Abrahams. Hasn't been coded yet, sorry. :( But followup on the thread so Carsten sees it has more supporters! :) This may very well be a nice thing to have, but also note that you can go onto a scheduled item, hit C-c C-s, then type +1 to have it scheduled to tomorrow. That seems pretty close to enough, though it's not quite automated. Bulk agenda action? -- GNU Emacs 24.0.90.1 (i686-pc-linux-gnu, GTK+ Version 2.24.4) of 2011-10-06 on pellet Org-mode version 7.7 (release_7.7.374.g9bd1)
Re: [O] `f' in agenda view
Am 04.10.2011 23:04, schrieb John Wiegley: Dave Abrahams d...@boostpro.com writes: It always strikes me as odd that `f' in agenda view moves the item forward by a day even if that leaves it still in the past. Typically if I have an overdue item, I just want to schedule it for today or a certain number of days in the future, and as it stands it's even a bit non-obvious when I've finally bumped it up to today if it's a few days old. Shouldn't the first `f' on an overdue item schedule it for today? Just to clarify, by 'f' dave means `org-agenda-date-later'. I believe he's using my keybinding for this command... I'm happy to hack something locally if the group doesn't agree, but moving things around in the past seems like such a corner case that I thought maybe this would be a better default behavior. I agree with Dave here. 'f' on a past-dated item maybe should move it today on the first press, and then into the future on subsequent presses. John +1 Me too I sometimes run into this situation where I just want to shift past-dated items to today. I never had a use case where I wanted to shift an item from past to past+n-daystoday. Rainer
Re: [O] org-contacts completion stopped working
Hi, No, but you are not alone. I use a very recent emacs 24 bzr checkout and org master from git. Not sure who's the culprit. Same problem here. After a quick look it seems that there has been a recent change in the arguments taken by the completion-table-case-fold function in minibuffer.el : http://bzr.savannah.gnu.org/lh/emacs/trunk/revision/105991 But I don't think I could be able to find a fix by myself. -- Julien
[O] ORG_MODE_PARSER_0.0.6 [ANN] Any idea for improvements?
Hi all, I have released version 0.0.6 of org-mode-parser for nodejs: http://gioorgi.com/tag/org-mode-parser/ Org mode parser is a parser for reading org-mode files in nodejs. It features more then 80 unit tests, and support also for :DRAWER: and archive tag. The parser can query on the structure, extract subtrees, regenerate the original input via an handy toOrgString() method. It is quite fast: I have done some small optimizations, and it seems good for general use. Please try it out and let me know if there are some bugs: it needs some real-world testing. Do you have some feature request? Version 0.0.7 is due soon, so if you have some idea, let me know! For every question, feel free to email me. -- Giovanni Giorgi http://gioorgi.com
[O] How to get numbered lists (1), (2), … ?
Dear all, In the manual, I found that numbered lists can be created with 1), 2), ... or 1., 2., ... How can I get numbered lists like this: (1), (2),...? I found org-list-demote-modify-bullet, but the help (and a google search) did not help me in finding a solution to this. Cheers, Marius
Re: [O] How to get numbered lists (1), (2), … ?
On Thu, Oct 13, 2011 at 11:11 AM, Marius Hofert marius.hof...@math.ethz.ch wrote: Dear all, In the manual, I found that numbered lists can be created with 1), 2), ... or 1., 2., ... How can I get numbered lists like this: (1), (2),...? I found org-list-demote-modify-bullet, but the help (and a google search) did not help me in finding a solution to this. I don't think you can. But you can customise latex export (maybe even html export, but I don't know) to show lists like that in the exported file. I hope this helps. Cheers, Marius -- Suvayu Open source is the future. It sets us free.
Re: [O] `f' in agenda view
Am 13.10.2011 10:47, schrieb Rainer Stengele: Am 04.10.2011 23:04, schrieb John Wiegley: Dave Abrahams d...@boostpro.com writes: It always strikes me as odd that `f' in agenda view moves the item forward by a day even if that leaves it still in the past. Typically if I have an overdue item, I just want to schedule it for today or a certain number of days in the future, and as it stands it's even a bit non-obvious when I've finally bumped it up to today if it's a few days old. Shouldn't the first `f' on an overdue item schedule it for today? Just to clarify, by 'f' dave means `org-agenda-date-later'. I believe he's using my keybinding for this command... I'm happy to hack something locally if the group doesn't agree, but moving things around in the past seems like such a corner case that I thought maybe this would be a better default behavior. I agree with Dave here. 'f' on a past-dated item maybe should move it today on the first press, and then into the future on subsequent presses. John +1 Me too I sometimes run into this situation where I just want to shift past-dated items to today. I never had a use case where I wanted to shift an item from past to past+n-daystoday. Rainer Well, as indicated somewhere else a C-c C-s +1 for shifting to tomorrow or C-c C-s . for shifting to today does exactly what I wanted. The power is in the house already. Thank you, Rainer
[O] How to count archived trees in :scope subtree
Hi all, For clocktables in the manual I find :scope The scope to consider. This can be any of the following: nilthe current buffer or narrowed region file the full current buffer subtreethe subtree where the clocktable is located treeN the surrounding level N tree, for example tree3 tree the surrounding level 1 tree agenda all agenda files (file..) scan these files file-with-archivescurrent file and its archives agenda-with-archives all agenda files, including archives How would I create a clocktable for a subtree counting locally archived trees (tag ARCHIVE)? 5 minutes later: I see that clocktable already always includes archived subtrees! Sorry for the noise, maybe this would be good to be noted in the manual. Thanks, Rainer
Re: [O] bug#9695: allowed date range
Carsten Dominik carsten.domi...@gmail.com writes: On 13.10.2011, at 09:48, Eric S Fraga wrote: Although the day is optional according to the regexp. I would definitely like to have the regexp with the space optional as well as there are cases where I want to type the date in directly (not in org mode for whatever reason). I am attaching a patch which will make time stamps without a day name like 2011-10-12 work correctly. Furthermore, pressing C-c C-c on a time stamp will fill in or fix the day name. However, I am not sure if this patch is complete, or if it has side effects. So it would be good if a few people could apply it and test it during their daily work for a few weeks, and then report problems in this thread. Excellent. Thanks. I've applied the patch and will let you know if anything strange happens! Silence should be taken as indicating no problems encountered :-) -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.7 (release_7.7.380.g54d7df.dirty)
Re: [O] bug#9695: allowed date range
Carsten Dominik carsten.domi...@gmail.com writes: On 13.10.2011, at 09:57, Tassilo Horn wrote: Eric S Fraga e.fr...@ucl.ac.uk writes: Hi Eric, Oh, now I see what's wrong. All time stamps consist of the date and then the day's name abbreviation, which is missing with your example. Correct would be 2011-10-17 Mon--2011-10-30 Sun Although the day is optional according to the regexp. I would definitely like to have the regexp with the space optional as well as there are cases where I want to type the date in directly (not in org mode for whatever reason). In those cases, it is easy to type 2011-01-01 or whatever but it's not necessarily trivial to determine the day of the week... Yes, I agree, although you can use org-time-stamp everywhere (in emacs). And you can actually insert timestamps simply by writing 2011-10-13 with the whitespace to make it a valid timestamp. That will be shown as day entry in the agenda, and you might have typed it in using some non-emacs text editor on you phone. Now, back in org-mode, simply S-up and S-down on any number, and et voila, the missing day name abbrev is added automatically. Actually, interesting thought experiment: does org actually do any consistency checks, comparing the date and the day of the week? No, I don't think so. Manipulating and creating timestamps using the provided commands ensures their correctness, but for actual calculation the day names are ignored. It's just for humans. Just to confirm, this is correct. - Carsten so, in that case, it does make sense to allow date stamps without the day! (and I see that Carsten has already provided a patch for this :-) -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.7 (release_7.7.380.g54d7df.dirty)
[O] Import efforts
Dear all, I'm looking for an easy way to incorporate efforts from other, non-org users into an org file. Assume you do project accounting using org. Recording and displaying the efforts /you/ have spent on the different items is no problem thanks to the clocking mechanism. However, I'd like to incorporate efforts that have been spent on delegated tasks, as well. Co-workers not using org can usually give me something like `It took me n hours to complete task x on day y' or `I've spent n hours between day y and z on task x' (unless they use a time-tracking tool with export function, but that's a different story). Is there a better solution to import this kind of data than to create `fake' logbook entries, may it be manually or with help of functions? Ulf
[O] bug#9179: 24.0.50; Org-agenda window splitting does not use full frame when fraction set to 1.0
1. M-: (setq org-agenda-window-frame-fractions '(1.0 . 1.0)) RET 2. M-x org-agenda a Expected results: The *Org Agenda* buffer occupies the entire frame Actual results: The *Org Agenda* buffer occupies the entire frame EXCEPT for a five line window at the top of the frame Due to fact that `fit-window-to-buffer' no more deletes other windows by side-effect. Hence for the '(1.0 . 1.0) case `org-fit-agenda-window' (or `org-fit-window-to-buffer') should call `delete-other-windows' or something the like. martin
Re: [O] Idea: insert current sort order property
On 12 October 2011 20:51, Christian Moe m...@christianmoe.com wrote: Then we need a way to keep track of what property keys are used to store outlines in, so we can offer those and only those for completion. (We don't want to offer all the property keys used in the buffer -- that's an invitation to overwrite data.) That makes sense So in my second pass (below), when you use a :foo: property to store the outline index, `foo' gets added to a list of keys in the :Stored_outlines: property of the parent. When you store an outline, the prompt for a property key offers completion on all the keys stored in :Stored_outlines:. See how this works for you. Thanks. I got it to work from a scratch buffer but not from .emacs (previous version worked fine from my .emacs). Restarting emacs showed an error. --- Warning (initialization): An error occurred while loading `q:/Q_Synced/Portable/emacs-23.3/home/.emacs': Invalid read syntax: # To ensure normal operation, you should investigate and remove the cause of the error in your initialization file. Start Emacs with the `--debug-init' option to view a complete error backtrace. - I couldn't copy the whole backtrace here (an encoding issue?) Here's the start and end of it in case it's any help: ___ Debugger entered--Lisp error: (invalid-read-syntax #) eval-buffer(#buffer *load* nil q:/Q_Synced/Portable/emacs-23.3/home/.emacs nil t) ; Reading at buffer position 13136 load-with-code-conversion(q:/Q_Synced/Portable/emacs-23.3/home/.emacs q:/Q_Synced/Portable/emacs-23.3/home/.emacs t t) load(~/.emacs t t) #[nil un-pastable stuff snipped [init-file-user system-type user-init-file-1 user-init-file otherfile source ms-dos ~ /_emacs windows-nt directory-files nil ^\\.emacs\\(\\.elc?\\)?$ ~/.emacs ^_emacs\\(\\.elc?\\)?$ ~/_emacs /.emacs t load expand-file-name init file-name-as-directory /.emacs.d file-name-extension elc file-name-sans-extension .el file-exists-p file-newer-than-file-p message Warning: %s is newer than %s sit-for 1 default alt inhibit-default-init inhibit-startup-screen] 7]() command-line() normal-top-level() _ Gez
Re: [O] Feature idea: show last log entry
John Wiegley jwieg...@gmail.com writes: Bernt Hansen be...@norang.ca writes: I log stuff in :LOGBOOK: with the items reversed so the newest is always on top. SPC on a task in the agenda opens the task including the drawer so I can see the details for any given task. Or in that case you should be able to type E in the agenda and see it also. That doesn't work for me - it skips the drawer. -Bernt
Re: [O] Bug Report: latex export interaction with inlinetasks
Hello, Colin Fraizer orgm...@cfraizer.com writes: Please pardon my ignorance, but I don't know how to generate a patch for distribution. You have all instructions you want at: http://orgmode.org/worg/org-contribute.html If you don't want/can't follow them, please tell me. I will push your patch. Since I sent that e-mail, I added a few more items from the opt-plist to include :todo, :todo-keywords, :tags, and :priority. I see, but you also included changes not directly related to the thread's subject (i.e. changes to verbatim environment). Be sure to filter them out if you create the patch. Regards, -- Nicolas Goaziou
[O] Blocked tasks also dimmed in export?
I use org-agenda-dim-blocked-tasks to keep track of tasks that have no current todo's, but in my exported html agenda view (C-c a e) which I share via dropbox, there is unfortunately no dimming. Is there a way to preserve the grey face in html export? Gez
Re: [O] Feature idea: show last log entry
Hi Bernt and John, Bernt Hansen wrote: John Wiegley jwieg...@gmail.com writes: Bernt Hansen be...@norang.ca writes: I log stuff in :LOGBOOK: with the items reversed so the newest is always on top. SPC on a task in the agenda opens the task including the drawer so I can see the details for any given task. Or in that case you should be able to type E in the agenda and see it also. That doesn't work for me - it skips the drawer. Same for me: it skips the drawer. Best regards, Seb -- Sebastien Vauban
Re: [O] Column view capture specific parts only
Johnny yggdra...@gmx.co.uk writes: Hi Johnny I have a nice outline set up in column view and would like to capture different versions of this into org-tables. There is far too many properties to get quick overviews, e.g. one table-capture I'd like to do contains only the task name and the committed delivery in ascending order, A case-study org file would have helped here. :-( No file? vague answers :-( Use different definition of columns: * first 2 properties :PROPERTIES: :COLUMNS: %40prop_1 %Prop_2 :END: #+BEGIN: columnview :hlines 1 #+END and another would contain only task and task-lead in ascending order. * other propts :PROPERTIES: :COLUMNS: %40prop_3 %Prop_4 :END: #+BEGIN: columnview :hlines 1 #+END you can change the order with M-x org-sort hth Giovanni
[O] No date/day title in agenda column view
A short while ago I stopped being able to see the names/dates of the
days when viewing the agenda in column view. I can see the overall
title (Week-agenda (W41-W42):) and then the next row displays totalled
effort for the first day in a blue face at the top of the effort
column. The next rows are the entries for that day, followed by the
totalled effort for the following day, and so on. The names/dates of
the days are not displayed. I can't remember if they used to take up
an extra row each or if they were on the same row as the totalled
effort, but either way I can't see them now - perhaps since using my
current version - GNU Emacs 23.3.1 and org-mode version 7.7
My org-columns-default-format is %1BLOCKED %4TODO %CATEGORY
%5Effort{:} %50ITEM %20TAGS %21ALLTAGS
Could this be a bug, or have I made this happen with a setting that I
can't remember?
Gez
Re: [O] Idea: insert current sort order property
Hi, Not sure I can help; I don't quite see how this error could be caused by anything in the code I sent you. Is this happening on the same system as you used before? What version of Emacs are you on when this happens? Yours, Christian On 10/13/11 1:40 PM, Gez wrote: Thanks. I got it to work from a scratch buffer but not from .emacs (previous version worked fine from my .emacs). Restarting emacs showed an error. --- Warning (initialization): An error occurred while loading `q:/Q_Synced/Portable/emacs-23.3/home/.emacs': Invalid read syntax: # To ensure normal operation, you should investigate and remove the cause of the error in your initialization file. Start Emacs with the `--debug-init' option to view a complete error backtrace. - I couldn't copy the whole backtrace here (an encoding issue?) Here's the start and end of it in case it's any help: ___ Debugger entered--Lisp error: (invalid-read-syntax #) eval-buffer(#buffer *load* nil q:/Q_Synced/Portable/emacs-23.3/home/.emacs nil t) ; Reading at buffer position 13136 load-with-code-conversion(q:/Q_Synced/Portable/emacs-23.3/home/.emacs q:/Q_Synced/Portable/emacs-23.3/home/.emacs t t) load(~/.emacs t t) #[nil un-pastable stuff snipped [init-file-user system-type user-init-file-1 user-init-file otherfile source ms-dos ~ /_emacs windows-nt directory-files nil ^\\.emacs\\(\\.elc?\\)?$ ~/.emacs ^_emacs\\(\\.elc?\\)?$ ~/_emacs /.emacs t load expand-file-name init file-name-as-directory /.emacs.d file-name-extension elc file-name-sans-extension .el file-exists-p file-newer-than-file-p message Warning: %s is newer than %s sit-for 1 default alt inhibit-default-init inhibit-startup-screen] 7]() command-line() normal-top-level() _ Gez
[O] C-c a e closes agenda buffer
I'm mostly working in a custom agenda view, refreshing with q or r, but I like to frequently update my exported html agenda view (shared in dropbox). Each time I export with C-c a e the agenda buffer closes and I have to call my custom agenda view again. Would it be possible to make it so that C-c a e aborts the refresh of the agenda buffer (as if C-g were used after C-c a)? Alternatively could a particular custom agenda view be designated as a default to return to after C-c a e? Gez
[O] GNU Emacs crashing on large Orgmode files (was: Ways to make org feasible for huge files)
* Marcelo de Moraes Serpa celose...@gmail.com wrote: Hi list, Hi individual! I love org and I think there's nothing like it out there, Ack! but I'm considering using Evernote for reference notes, because my reference.orgfile has grown too big (4234k + lines). This makes the rendering of the file way too slow, and 2 times out of 10 emacs crashes because of that. Not exactly the topic you mentioned but as a side mark to crashes on Mac OS X I want to add: I am trying to implement life-logging [1] with Org-mode and GNU Emacs. Therefore I created [2]. Even in this early stage, it ends up with 150.000 lines in approx. 30 Org-mode files. Most of them are in «*.org_archive» files though. (Further performance information: [3]) On my notebook I am using GNU Linux (Ubuntu 11.04) with GNU Emacs 23.2.1 (i686-pc-linux-gnu, GTK+ Version 2.24.4). At home I've got Mac OS X 10.5 with http://emacsformacosx.com/ (sorry, no detailed version number since I am currently sitting in my office *g*). I never noticed *any* crash of Emacs using Org-mode on my Linux machine. But on my OS X box, I notice crashes many times. Mostly when navigating (vertically or horizontally) in the Agenda view. Maybe there is an (hidden?) issue with GNU Emacs on OS X (too). 1. http://en.wikipedia.org/wiki/Lifelogging 2. https://github.com/novoid/Memacs 3. https://github.com/novoid/Memacs/blob/master/FAQs_and_Best_Practices.org -- Karl Voit
Re: [O] bug#9695: allowed date range
Eric S Fraga e.fr...@ucl.ac.uk writes: I am attaching a patch which will make time stamps without a day name like 2011-10-12 work correctly. Furthermore, pressing C-c C-c on a time stamp will fill in or fix the day name. However, I am not sure if this patch is complete, or if it has side effects. So it would be good if a few people could apply it and test it during their daily work for a few weeks, and then report problems in this thread. Excellent. Thanks. I've applied the patch and will let you know if anything strange happens! Silence should be taken as indicating no problems encountered :-) Ditto. Bye, Tassilo
[O] How to show done items in specific agenda views
I'd like to include done items only in certain views, including the one below, but I can't work out how to do it. At the moment I have org-agenda-skip-scheduled-if-done set as nil but that affects all my views (and messes up undone totalled effort estimates). Ideally I'd like to export log mode, but I couldn't work out a way to do that. My current set up means that items done today but scheduled for a previous day don't show up on this view unless they are rescheduled for today. Is there a way round this? --- (quote ((7e For export ((agenda ((org-agenda-overriding-header Scheduled todo's) (org-agenda-span (quote week)) (org-agenda-skip-function (quote (org-agenda-skip-entry-if (quote regexp) habit))) (org-agenda-sorting-strategy (quote (todo-state-up))) (org-agenda-prefix-format %-7e) (org-agenda-todo-keyword-format %-10s))) (tags-todo thisweek ((org-agenda-overriding-header Unscheduled todo's; also tasks (from which todo's were generated)) (org-agenda-skip-function (quote (org-agenda-skip-entry-if (quote scheduled (org-agenda-prefix-format %-7e) (org-agenda-todo-keyword-format %-10s) (org-agenda-sorting-strategy (quote (todo-state-up)) ((org-agenda-remove-tags t)) (Q:\\Q_Synced\\My Dropbox\\OrgModeExports\\agenda.html)) --- Gez
[O] underscore behaviour
I use names with _ very often, and I like to export to PDF, because it' the one that looks nicest. But the _ in latex means something different, and I find my output a bit messed up. Isn't it possible to add an automatic quote for every _ when exporting to latex/pdf maybe? Or is there a better way to write things like function names __init__ or similar?
Re: [O] FR: revivable marks in agenda
On 10/13/2011 03:41 AM, Samuel Wales wrote: I have an agenda view for urgent and now tags. I just spent a lot of time choosing which ones to mark to remove the tags. I then did B - to remove the tags. I was a little too quick and told it to remove urgent. It did not offer the possibility to remove more than one that I know of. This meant that all of the marks I did on now disappeared. :( I wonder if we should have revivable marks (a command revives them). In this case, and also for speed, it would be useful to be able to specify more than one tag to remove. Samuel Well in general you should use some revision control system, (git bzr mercurial fossil you have a large choice). In this way you can safely modify things and be sure that you can get back what you lost in case you make a mistake..
Re: [O] underscore behaviour
Andrea Crotti andrea.crott...@gmail.com wrote:
I use names with _ very often, and I like to export to PDF, because
it' the one that looks nicest.
But the _ in latex means something different, and I find my output a
bit messed up.
Isn't it possible to add an automatic quote for every _ when
exporting to latex/pdf maybe?
Or is there a better way to write things like function names
__init__ or similar?
#+OPTIONS: ^:nil
or
#+OPTIONS: ^:{}
should do it - see
(info (org) Export options)
for more options than you can shake a stick at.
Nick
Re: [O] `f' in agenda view
on Thu Oct 13 2011, Rainer Stengele rainer.stengele-AT-online.de wrote: Am 13.10.2011 10:47, schrieb Rainer Stengele: Me too I sometimes run into this situation where I just want to shift past-dated items to today. I never had a use case where I wanted to shift an item from past to past+n-daystoday. Rainer Well, as indicated somewhere else a C-c C-s +1 for shifting to tomorrow or C-c C-s . for shifting to today does exactly what I wanted. The power is in the house already. Yeah, it's just a question of having to think absolutely when you want to think incrementally. That's a lot of keystrokes when what I want is to hit `f' (or something) 3 times to move the items to three days from now. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
Re: [O] GNU Emacs crashing on large Orgmode files
Hi Karl Karl Voit devn...@karl-voit.at writes: * Marcelo de Moraes Serpa celose...@gmail.com wrote: Hi list, Hi individual! I love org and I think there's nothing like it out there, Ack! but I'm considering using Evernote for reference notes, because my reference.orgfile has grown too big (4234k + lines). This makes the rendering of the file way too slow, and 2 times out of 10 emacs crashes because of that. Not exactly the topic you mentioned but as a side mark to crashes on Mac OS X I want to add: I am trying to implement life-logging [1] with Org-mode and GNU Emacs. Therefore I created [2]. Even in this early stage, it ends up with 150.000 lines in approx. 30 Org-mode files. Most of them are in «*.org_archive» files though. (Further performance information: [3]) On my notebook I am using GNU Linux (Ubuntu 11.04) with GNU Emacs 23.2.1 (i686-pc-linux-gnu, GTK+ Version 2.24.4). At home I've got Mac OS X 10.5 with http://emacsformacosx.com/ (sorry, no detailed version number since I am currently sitting in my office *g*). I never noticed *any* crash of Emacs using Org-mode on my Linux machine. But on my OS X box, I notice crashes many times. Mostly when navigating (vertically or horizontally) in the Agenda view. Maybe there is an (hidden?) issue with GNU Emacs on OS X (too). Just for your information I use emacsformacosx port on Mac OS X 10.6.8, currently GNU Emacs 24.0.50.1 with 2GB RAM and 2.4GHz. On larger org files (over 13000 lines) navigation slows considerably, but I have never had Emacs crash, despite fairly heavy usage. However, I tend to maintain fairly compact files, through archiving. 1. http://en.wikipedia.org/wiki/Lifelogging 2. https://github.com/novoid/Memacs 3. https://github.com/novoid/Memacs/blob/master/FAQs_and_Best_Practices.org mj --- Org-mode version 7.7 (release_7.7.359.g18e67) GNU Emacs 24.0.50.1 (x86_64-apple-darwin, NS apple-appkit-1038.35) of 2011-08-21 on virtualmac.porkrind.org
[O] [PATCH] Fix org-contacts completion at point (was: org-contacts completion stopped working)
julien Barnier jul...@nozav.org writes: Hi Julien, I use a very recent emacs 24 bzr checkout and org master from git. Not sure who's the culprit. Same problem here. After a quick look it seems that there has been a recent change in the arguments taken by the completion-table-case-fold function in minibuffer.el : http://bzr.savannah.gnu.org/lh/emacs/trunk/revision/105991 Thanks for the pointer! But I don't think I could be able to find a fix by myself. But I was able, so good teamwork, mate. :-) --8---cut here---start-8--- From d89ca3ce39cd7436e5205744adcf468d9619180f Mon Sep 17 00:00:00 2001 From: Tassilo Horn tass...@member.fsf.org Date: Thu, 13 Oct 2011 17:02:07 +0200 Subject: [PATCH 2/2] Fix org-contacts completion at point. --- contrib/lisp/org-contacts.el | 11 +-- 1 files changed, 5 insertions(+), 6 deletions(-) diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index 167caa0..74d68dc 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -169,9 +169,10 @@ If both match values are nil, return all contacts. (when (not (fboundp 'completion-table-case-fold)) ;; That function is new in Emacs 24... - (defun completion-table-case-fold (table string pred action) -(let ((completion-ignore-case t)) - (complete-with-action action table string pred + (defun completion-table-case-fold (table optional dont-fold) +(lambda (string pred action) + (let ((completion-ignore-case (not dont-fold))) + (complete-with-action action table string pred) (defun org-contacts-complete-name (optional start) Complete text at START with a user name and email. @@ -226,9 +227,7 @@ If both match values are nil, return all contacts. ;; If the user has an email address, append USER EMAIL. if email collect (org-contacts-format-email contact-name email)) , ) -(list start end (if org-contacts-completion-ignore-case - (apply-partially #'completion-table-case-fold completion-list) - completion-list +(list start end (completion-table-case-fold completion-list (not org-contacts-completion-ignore-case) (defun org-contacts-message-complete-function () Function used in `completion-at-point-functions' in `message-mode'. -- 1.7.7 --8---cut here---end---8---
Re: [O] How to get numbered lists (1), (2), … ?
Dear Suvayu, thanks. It would be good to know how latex export can be customized to achieve this. Cheers, Marius On 2011-10-13, at 11:37 , suvayu ali wrote: On Thu, Oct 13, 2011 at 11:11 AM, Marius Hofert marius.hof...@math.ethz.ch wrote: Dear all, In the manual, I found that numbered lists can be created with 1), 2), ... or 1., 2., ... How can I get numbered lists like this: (1), (2),...? I found org-list-demote-modify-bullet, but the help (and a google search) did not help me in finding a solution to this. I don't think you can. But you can customise latex export (maybe even html export, but I don't know) to show lists like that in the exported file. I hope this helps. Cheers, Marius -- Suvayu Open source is the future. It sets us free.
[O] Links to C/C++ source code lines
Hi, I wrote a small hook for creating org-mode links to C/C++ source code lines in the form of a regexp so the links stay valid even if the source code changes eg. a source line while(ptr ptr_end) has a link file:/home/user/src/example.cpp::/while[ \t]*([ \t]*ptr[ \t]*[ \t]*ptr_end[ \t] *)#1/ The number after the hash is a sequence number in case there are more than one such line If you are interested: http://rafflo.w.interia.pl/org-c-link.el regards, Rafal
Re: [O] FR: revivable marks in agenda
On 2011-10-13, Andrea Crotti andrea.crott...@gmail.com wrote: Well in general you should use some revision control system, Those do not store things that never save to disk.
Re: [O] Error args-out-of-range when using org-babel-tangle with org7.7
Thanks, that was part of the problem. The other part was a chunk of stub code: #source: el-stack-keys #+begin_src emacs-lisp #+end_src Replacing it with: #source: el-stack-keys #+begin_src emacs-lisp #+end_src Seems to work. __ Jonathan Arkell Tech Lead Inspired By Drum Bass, Scheme, Kawaii p. 403.206.4377 402 -- 11th Ave SE Calgary, AB, Canada T2G 0Y4 jonath...@criticalmass.com criticalmass.com On 12/10/11 1:54 PM, Thomas S. Dye t...@tsdye.com wrote: Hi Jonathan, Does it help if you change #+src_name to #+source:? Tom Jonathan Arkell jonath...@criticalmass.com writes: Hi Everyone I am having some problems with using org-babel-tangle. Each time I try to use it, I get the error '(args-out-of-range -1 0)'. I've simplified the source code chunk I want to tangle to this: #+src_name stack-el #+begin_src emacs-lisp :tangle stack.el ;;; stack.el -- custom elisp for the stack development #+end_src I am on org-mode 7.7, on Mac OS 10.6.8, Emacs for Mac Os (23.2.1) I am sure I am doing something totally wrong and/or silly. Can someone help me out? Thanks! Here is a full backtrace: Debugger entered--Lisp error: (args-out-of-range -1 0) org-babel-parse-src-block-match() org-babel-get-src-block-info(light) (let* ((start-line ...) (file ...) (info ...) (src-lang ...)) (unless (string= ... no) (unless ... ...))) (let ((full-block ...) (beg-block ...) (end-block ...) (lang ...) (beg-lang ...) (end-lang ...) (switches ...) (beg-switches ...) (end-switches ...) (header-args ...) (beg-header-args ...) (end-header-args ...) (body ...) (beg-body ...) (end-body ...)) ((lambda ... ...) (replace-regexp-in-string [ ] - ...)) (let* (... ... ... ...) (unless ... ...)) (goto-char end-block)) (while (re-search-forward org-babel-src-block-regexp nil t) (goto-char (match-beginning 0)) (let (... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) (... ...) (let* ... ...) (goto-char end-block))) (save-window-excursion (when file (find-file file)) (setq to-be-removed (current-buffer)) (goto-char (point-min)) (while (re-search-forward org-babel-src-block-regexp nil t) (goto-char ...) (let ... ... ... ...))) (let* ((file ...) (visited-p ...) (point ...) to-be-removed) (save-window-excursion (when file ...) (setq to-be-removed ...) (goto-char ...) (while ... ... ...)) (unless visited-p (kill-buffer to-be-removed)) (goto-char point)) (org-babel-map-src-blocks (buffer-file-name) ((lambda ... ...) (replace-regexp-in-string [] - ...)) (let* (... ... ... ...) (unless ... ...))) (let ((block-counter 1) (current-heading ) blocks) (org-babel-map-src-blocks (buffer-file-name) (... ...) (let* ... ...)) (setq blocks (mapcar ... blocks)) blocks) org-babel-tangle-collect-blocks(nil) (mapc (lambda (by-lang) (let* ... ...)) (org-babel-tangle-collect-blocks lang)) (let ((block-counter 0) (org-babel-default-header-args ...) path-collector) (mapc (lambda ... ...) (org-babel-tangle-collect-blocks lang)) (message tangled %d code block%s from %s block-counter (if ... s) (file-name-nondirectory ...)) (when org-babel-post-tangle-hook (mapc ... path-collector)) path-collector) (save-excursion (let (... ... path-collector) (mapc ... ...) (message tangled %d code block%s from %s block-counter ... ...) (when org-babel-post-tangle-hook ...) path-collector)) (save-restriction (when only-this-block (unless ... ...) (unless target-file ...) (narrow-to-region ... ...)) (save-excursion (let ... ... ... ... path-collector))) org-babel-tangle(nil) call-interactively(org-babel-tangle nil nil) 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. -- Thomas S. Dye http://www.tsdye.com 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] FR: revivable marks in agenda
On 10/13/2011 05:57 PM, Samuel Wales wrote: On 2011-10-13, Andrea Crottiandrea.crott...@gmail.com wrote: Well in general you should use some revision control system, Those do not store things that never save to disk. Sorry I don't understand the answer... If you're talking about tags and orgmode, how is it possible that is not stored to disk?
[O] Bug: Markup not rendered in document title [7.7 (release_7.7.396.g25c21)]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
For example, I can get strikethrough in a headline by writing
** +crossed out+
but if I write:
#+TITLE: +crossed out+
I don't see anything like that.
Emacs : GNU Emacs 23.3.1 (x86_64-apple-darwin10.8.0, Carbon Version 1.6.0
AppKit 1038.36)
of 2011-09-12 on pluto.luannocracy.com
Package: Org-mode version 7.7 (release_7.7.396.g25c21)
current state:
==
(setq
org-x-backends '(ox-org ox-redmine)
org-agenda-deadline-leaders '(D: D%d: )
org-clock-in-switch-to-state STARTED
org-agenda-skip-scheduled-if-deadline-is-shown t
org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
org-special-ctrl-a/e '(nil . t)
org-x-redmine-title-prefix-match-function 'org-x-redmine-title-prefix-match
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-agenda-custom-commands '((E Errands (next 3 days) tags
ErrandTODO\DONE\TODO\CANCELED\STYLE\habit\SCHEDULED\+3d\
((org-agenda-overriding-header Errands (next 3
days))
)
)
(A Priority #A tasks agenda
((org-agenda-ndays 1)
(org-agenda-overriding-header
Today's priority #A tasks: )
(org-agenda-skip-function
(quote
(org-agenda-skip-entry-if (quote notregexp)
\\=.*\\[#A\\])
)
)
)
)
(b Priority #A and #B tasks agenda
((org-agenda-ndays 1)
(org-agenda-overriding-header
Today's priority #A and #B tasks: )
(org-agenda-skip-function
(quote
(org-agenda-skip-entry-if (quote regexp)
\\=.*\\[#C\\])
)
)
)
)
(w Waiting/delegated tasks tags
TODO=\WAITING\|TODO=\DELEGATED\
((org-agenda-overriding-header
Waiting/delegated tasks:)
(org-agenda-sorting-strategy
(quote (todo-state-up priority-down
category-up)))
)
)
(p Unprioritized tasks tags
AREA\Work\TODO\\TODO{DONE\\|CANCELED\\|NOTE\\|PROJECT\\|DEFERRED\\|SOMEDAY}
((org-agenda-files
(quote
(~/Documents/Tasks/todo.txt)
)
)
(org-agenda-overriding-header
Unprioritized tasks: )
(org-agenda-skip-function
Re: [O] How to get numbered lists (1), (2), … ?
Hi Marius, On Thu, Oct 13, 2011 at 5:26 PM, Marius Hofert marius.hof...@math.ethz.ch wrote: Dear Suvayu, thanks. It would be good to know how latex export can be customized to achieve this. This thread might be helpful: http://thread.gmane.org/gmane.emacs.orgmode/46763/focus=46771 -- Suvayu Open source is the future. It sets us free.
Re: [O] Idea: insert current sort order property
That was my duh - I accidentally left a # in when copying to my .emacs. It works fine now. Thank you. Gez On 13 October 2011 13:39, Christian Moe m...@christianmoe.com wrote: Hi, Not sure I can help; I don't quite see how this error could be caused by anything in the code I sent you. Is this happening on the same system as you used before? What version of Emacs are you on when this happens? Yours, Christian On 10/13/11 1:40 PM, Gez wrote: Thanks. I got it to work from a scratch buffer but not from .emacs (previous version worked fine from my .emacs). Restarting emacs showed an error. --- Warning (initialization): An error occurred while loading `q:/Q_Synced/Portable/emacs-23.3/home/.emacs': Invalid read syntax: # To ensure normal operation, you should investigate and remove the cause of the error in your initialization file. Start Emacs with the `--debug-init' option to view a complete error backtrace. -
Re: [O] How to get numbered lists (1), (2), … ?
[ I started this earlier but I guess I didn't send it out. Suvayu has
replied in the meantime with a pointer to a better solution than this
one, but this might be of some minor interest to some people as well -
besides, I spent a whole 20 minutes on it, half of it trying to figure
out why my mail was not working :-( : why let that effort go to
waste?:-) ]
Marius Hofert marius.hof...@math.ethz.ch wrote:
Dear Suvayu,
thanks.
It would be good to know how latex export can be customized to achieve this.
Depends on how much customization you are willing to go through: there is an
enumerate.sty package in LaTeX that can do that:
--8---cut here---start-8---
...
\usepackage{enumerate}
...
\begin{enumerate}[(1)]
\item foo
\item bar
\end{enumerate}
...
--8---cut here---start-8---
Inserting the \usepackage from the org file is no problem:
--8---cut here---end---8---
#+LATEX_HEADER: \usepackage{enumerate}
...
--8---cut here---end---8---
Getting the argument to the enumerate environment in the right place is
another matter. I think the only way is to redefine org-list-generic-to-latex
like this (add this to your initialization file, .emacs or whatever, after you
load org):
--8---cut here---start-8---
(require 'org-list)
(defun org-list-to-latex (list optional params)
Convert LIST into a LaTeX list.
LIST is as returned by `org-list-parse-list'. PARAMS is a property list
with overruling parameters for `org-list-to-generic'.
(org-list-to-generic
list
(org-combine-plists
'(:splice nil :ostart \\begin{enumerate}[(1)]\n :oend \\end{enumerate}
:ustart \\begin{itemize}\n :uend \\end{itemize}
:dstart \\begin{description}\n :dend \\end{description}
:dtstart [ :dtend ]
:istart \\item :iend \n
:icount (let ((enum (nth depth '(i ii iii iv
(if enum
;; LaTeX increments counter just before
;; using it, so set it to the desired
;; value, minus one.
(format \\setcounter{enum%s}{%s}\n\\item
enum (1- counter))
\\item ))
:csep \n
:cbon \\texttt{[X]} :cboff \\texttt{[ ]}
:cbtrans $\\boxminus$)
params)))
--8---cut here---end---8---
The only change is the definition of :ostart. Not a very flexible method,
but it will serve in a pinch. ngz et al. might have better ideas.
I should say that there are other ways to customize enumeration labels
in LaTeX - see e.g. http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enumerate -
but afaict they would all require some rewiring of the above function, similar
to the above.
Nick
Cheers,
Marius
On 2011-10-13, at 11:37 , suvayu ali wrote:
On Thu, Oct 13, 2011 at 11:11 AM, Marius Hofert
marius.hof...@math.ethz.ch wrote:
Dear all,
In the manual, I found that numbered lists can be created with 1), 2), ...
or 1., 2., ...
How can I get numbered lists like this: (1), (2),...?
I found org-list-demote-modify-bullet, but the help (and a google search)
did not help me in finding a solution to this.
I don't think you can. But you can customise latex export (maybe even
html export, but I don't know) to show lists like that in the exported
file.
I hope this helps.
Cheers,
Marius
--
Suvayu
Open source is the future. It sets us free.
Re: [O] How to get numbered lists (1), (2), … ?
Dear Nick,
thanks for helping.
What do you mean by better solution? As far as I can tell, your approach is
precisely what Suvayu pointed to. Using your approach, of course much more is
possible, please look at the create enumitem package with all its
customizations.
But this approach is a no-go for me (at least at the moment) mainly due to the
following reasons (please let me know if I'm wrong, I'm a total newbie to
org-mode):
1) I have about 40 lists in one file. Having to put in special LaTeX commands
is not an option (maybe on only has to type it in once, but then it can easily
get overseen, e.g., when you move lists around and the one containing the LaTeX
commands is not the first one in the document anymore)
2) org-mode is basically a better text-mode. I don't want to have LaTeX code
in there if I print it as a .txt file.
Is there a solution without having to put
#+LATEX_HEADER: \usepackage{enumerate}
before each list? Can this be set anywhere in the preferences?
But I assume that I still have to put in lists in org-mode like this: 1.,2.,...
or 1),2),... and can't put them in like this (1),(2),...?
Hmm... this is indeed a drawback. The latter lists a far better visible, they
are more consistent with respect to other list types such as (i), (ii), etc.,
and ultimately also with respect to numbering of equations. There are probably
even more typographic reasons to display lists like this. For example, if you
refer to a list within a theorem environment (which has a label itself) and you
use 1., 2.,... lists, then this looks like this:
Theorem 1.2 2. shows that ...
The eye hardly sees that one means Theorem 1.2 Part (2). Even worse, when
reading this, one thinks that the sentence stops after 2.. It's really a bad
thing, and not getting much better with right-sided parentheses.
Cheers,
Marius
On 2011-10-13, at 21:10 , Nick Dokos wrote:
[ I started this earlier but I guess I didn't send it out. Suvayu has
replied in the meantime with a pointer to a better solution than this
one, but this might be of some minor interest to some people as well -
besides, I spent a whole 20 minutes on it, half of it trying to figure
out why my mail was not working :-( : why let that effort go to
waste?:-) ]
Marius Hofert marius.hof...@math.ethz.ch wrote:
Dear Suvayu,
thanks.
It would be good to know how latex export can be customized to achieve this.
Depends on how much customization you are willing to go through: there is an
enumerate.sty package in LaTeX that can do that:
--8---cut here---start-8---
...
\usepackage{enumerate}
...
\begin{enumerate}[(1)]
\item foo
\item bar
\end{enumerate}
...
--8---cut here---start-8---
Inserting the \usepackage from the org file is no problem:
--8---cut here---end---8---
#+LATEX_HEADER: \usepackage{enumerate}
...
--8---cut here---end---8---
Getting the argument to the enumerate environment in the right place is
another matter. I think the only way is to redefine org-list-generic-to-latex
like this (add this to your initialization file, .emacs or whatever, after you
load org):
--8---cut here---start-8---
(require 'org-list)
(defun org-list-to-latex (list optional params)
Convert LIST into a LaTeX list.
LIST is as returned by `org-list-parse-list'. PARAMS is a property list
with overruling parameters for `org-list-to-generic'.
(org-list-to-generic
list
(org-combine-plists
'(:splice nil :ostart \\begin{enumerate}[(1)]\n :oend \\end{enumerate}
:ustart \\begin{itemize}\n :uend \\end{itemize}
:dstart \\begin{description}\n :dend \\end{description}
:dtstart [ :dtend ]
:istart \\item :iend \n
:icount (let ((enum (nth depth '(i ii iii iv
(if enum
;; LaTeX increments counter just before
;; using it, so set it to the desired
;; value, minus one.
(format \\setcounter{enum%s}{%s}\n\\item
enum (1- counter))
\\item ))
:csep \n
:cbon \\texttt{[X]} :cboff \\texttt{[ ]}
:cbtrans $\\boxminus$)
params)))
--8---cut here---end---8---
The only change is the definition of :ostart. Not a very flexible method,
but it will serve in a pinch. ngz et al. might have better ideas.
I should say that there are other ways to customize enumeration labels
in LaTeX - see e.g. http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enumerate -
but afaict they would all require some rewiring of the above function, similar
to the above.
Nick
Cheers,
Marius
On 2011-10-13, at
Re: [O] How to get numbered lists (1), (2), … ?
Without diving into how to set it up in org-mode, the paralist package for
LaTeX enables inline numbered lists, as in
%% In preamble
\usepackage{paralist}
%% In document
\begin{inparaenum}
\item first element
\item second element
\end{inparaenum}
As to how to organize this to be an option for org-mode without
incorporating above into the setup, I would also be interested.
Alan
On Thu, Oct 13, 2011 at 12:10 PM, Nick Dokos nicholas.do...@hp.com wrote:
[ I started this earlier but I guess I didn't send it out. Suvayu has
replied in the meantime with a pointer to a better solution than this
one, but this might be of some minor interest to some people as well -
besides, I spent a whole 20 minutes on it, half of it trying to figure
out why my mail was not working :-( : why let that effort go to
waste?:-) ]
Marius Hofert marius.hof...@math.ethz.ch wrote:
Dear Suvayu,
thanks.
It would be good to know how latex export can be customized to achieve
this.
Depends on how much customization you are willing to go through: there is
an
enumerate.sty package in LaTeX that can do that:
--8---cut here---start-8---
...
\usepackage{enumerate}
...
\begin{enumerate}[(1)]
\item foo
\item bar
\end{enumerate}
...
--8---cut here---start-8---
Inserting the \usepackage from the org file is no problem:
--8---cut here---end---8---
#+LATEX_HEADER: \usepackage{enumerate}
...
--8---cut here---end---8---
Getting the argument to the enumerate environment in the right place is
another matter. I think the only way is to redefine
org-list-generic-to-latex
like this (add this to your initialization file, .emacs or whatever, after
you
load org):
--8---cut here---start-8---
(require 'org-list)
(defun org-list-to-latex (list optional params)
Convert LIST into a LaTeX list.
LIST is as returned by `org-list-parse-list'. PARAMS is a property list
with overruling parameters for `org-list-to-generic'.
(org-list-to-generic
list
(org-combine-plists
'(:splice nil :ostart \\begin{enumerate}[(1)]\n :oend
\\end{enumerate}
:ustart \\begin{itemize}\n :uend \\end{itemize}
:dstart \\begin{description}\n :dend \\end{description}
:dtstart [ :dtend ]
:istart \\item :iend \n
:icount (let ((enum (nth depth '(i ii iii iv
(if enum
;; LaTeX increments counter just before
;; using it, so set it to the desired
;; value, minus one.
(format \\setcounter{enum%s}{%s}\n\\item
enum (1- counter))
\\item ))
:csep \n
:cbon \\texttt{[X]} :cboff \\texttt{[ ]}
:cbtrans $\\boxminus$)
params)))
--8---cut here---end---8---
The only change is the definition of :ostart. Not a very flexible method,
but it will serve in a pinch. ngz et al. might have better ideas.
I should say that there are other ways to customize enumeration labels
in LaTeX - see e.g.
http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enumerate -
but afaict they would all require some rewiring of the above function,
similar
to the above.
Nick
Cheers,
Marius
On 2011-10-13, at 11:37 , suvayu ali wrote:
On Thu, Oct 13, 2011 at 11:11 AM, Marius Hofert
marius.hof...@math.ethz.ch wrote:
Dear all,
In the manual, I found that numbered lists can be created with 1), 2),
... or 1., 2., ...
How can I get numbered lists like this: (1), (2),...?
I found org-list-demote-modify-bullet, but the help (and a google
search) did not help me in finding a solution to this.
I don't think you can. But you can customise latex export (maybe even
html export, but I don't know) to show lists like that in the exported
file.
I hope this helps.
Cheers,
Marius
--
Suvayu
Open source is the future. It sets us free.
Re: [O] How to get numbered lists (1), (2), … ?
Marius Hofert marius.hof...@math.ethz.ch wrote:
What do you mean by better solution? As far as I can tell, your
approach is precisely what Suvayu pointed to.
No: what Suvayu pointed to can be done with the standard latex exporter,
so it would not require changes to org-list-generic-to-latex. Just add
something like this at the top of your org file:
#+LATEX: \renewcommand{\theenumi}{(\arabic{enumi})}
It's better in that it is simpler. There are drawbacks however: the
above produces lists like this:
(1). foo
(2). bar
with a period after the closing paren.
Using your approach, of course much more is possible, please look at
the create enumitem package with all its customizations.
That is true: which one is better depends on one's requirements (both
the desired output and how much pain one is willing to suffer in order
to get there).
But this approach is a no-go for me (at least at the moment) mainly
due to the following reasons (please let me know if I'm wrong, I'm a
total newbie to org-mode):
1) I have about 40 lists in one file. Having to put in special LaTeX
commands is not an option (maybe on only has to type it in once, but
then it can easily get overseen, e.g., when you move lists around and
the one containing the LaTeX commands is not the first one in the
document anymore)
That's no problem: the LATEX_HEADER line goes in once at the top
of the org file. You can move lists around at will.
2) org-mode is basically a better text-mode. I don't want to have
LaTeX code in there if I print it as a .txt file.
Is there a solution without having to put #+LATEX_HEADER:
\usepackage{enumerate} before each list? Can this be set anywhere in
the preferences?
You can customize the latex preamble that org adds to latex files to do
that. The disadvantage is that you get the modified preamble always.
See the org-export-latex-packages-alist variable for one way to do that.
But I assume that I still have to put in lists in org-mode like this:
1.,2.,... or 1),2),... and can't put them in like this (1),(2),...?
Correct: that would require changes to org-list.el I think - but Nicolas
will have to say the final word on this. All the solutions so far work
by modifying the latex output only, not the way you enter the list into
the org file.
Nick
Hmm... this is indeed a drawback. The latter lists a far better
visible, they are more consistent with respect to other list types
such as (i), (ii), etc., and ultimately also with respect to numbering
of equations. There are probably even more typographic reasons to
display lists like this. For example, if you refer to a list within a
theorem environment (which has a label itself) and you use 1.,
2.,... lists, then this looks like this:
Theorem 1.2 2. shows that ...
The eye hardly sees that one means Theorem 1.2 Part (2). Even worse,
when reading this, one thinks that the sentence stops after 2.. It's
really a bad thing, and not getting much better with right-sided
parentheses.
Cheers,
Marius
On 2011-10-13, at 21:10 , Nick Dokos wrote:
[ I started this earlier but I guess I didn't send it out. Suvayu has
replied in the meantime with a pointer to a better solution than this
one, but this might be of some minor interest to some people as well -
besides, I spent a whole 20 minutes on it, half of it trying to figure
out why my mail was not working :-( : why let that effort go to
waste?:-) ]
Marius Hofert marius.hof...@math.ethz.ch wrote:
Dear Suvayu,
thanks.
It would be good to know how latex export can be customized to achieve
this.
Depends on how much customization you are willing to go through: there is an
enumerate.sty package in LaTeX that can do that:
--8---cut here---start-8---
...
\usepackage{enumerate}
...
\begin{enumerate}[(1)]
\item foo
\item bar
\end{enumerate}
...
--8---cut here---start-8---
Inserting the \usepackage from the org file is no problem:
--8---cut here---end---8---
#+LATEX_HEADER: \usepackage{enumerate}
...
--8---cut here---end---8---
Getting the argument to the enumerate environment in the right place is
another matter. I think the only way is to redefine
org-list-generic-to-latex
like this (add this to your initialization file, .emacs or whatever, after
you
load org):
--8---cut here---start-8---
(require 'org-list)
(defun org-list-to-latex (list optional params)
Convert LIST into a LaTeX list.
LIST is as returned by `org-list-parse-list'. PARAMS is a property list
with overruling parameters for `org-list-to-generic'.
(org-list-to-generic
list
(org-combine-plists
'(:splice nil :ostart \\begin{enumerate}[(1)]\n :oend
\\end{enumerate}
:ustart \\begin{itemize}\n
Re: [O] `f' in agenda view
Dave Abrahams d...@boostpro.com writes: Yeah, it's just a question of having to think absolutely when you want to think incrementally. That's a lot of keystrokes when what I want is to hit `f' (or something) 3 times to move the items to three days from now. +1. John
Re: [O] How to get numbered lists (1), (2), … ?
Alan E. Davis lngn...@gmail.com wrote:
Without diving into how to set it up in org-mode, the paralist package for
LaTeX enables inline numbered lists, as in
%% In preamble
\usepackage{paralist}
%% In document
\begin{inparaenum}
\item first element
\item second element
\end{inparaenum}
As to how to organize this to be an option for org-mode without incorporating
above into the setup, I would also be interested.
The method described below can of course accomplish this: you need to
change the :ostart and :oend settings. It's also fairly easy to define
customizable variables for all of this, but that is left as an exercise
to the interested reader... Nicolas might be interested in anything you
come up with.
Nick
Hint (entirely untested):
(defcustom o-e-l-l-s-ostart \begin{enumerate}\n ...)
(defcustom o-e-l-l-s-oend ...)
...
(setq org-export-latex-list-settings `(:splice nil :ostart ,o-e-l-l-s-ostart
:oend ,o-e-l-l-s-oend
:ustart .)
...[ some way to reevaluate the above variable if any of its components change
- does custom provide anything like that?? ]...
(defun org-list-to-latex (...)
...
(org-combine-plists
org-export-latex-list-settings
params)
...
Alan
On Thu, Oct 13, 2011 at 12:10 PM, Nick Dokos nicholas.do...@hp.com wrote:
[ I started this earlier but I guess I didn't send it out. Suvayu has
replied in the meantime with a pointer to a better solution than this
one, but this might be of some minor interest to some people as well -
besides, I spent a whole 20 minutes on it, half of it trying to figure
out why my mail was not working :-( : why let that effort go to
waste?:-) ]
Marius Hofert marius.hof...@math.ethz.ch wrote:
Dear Suvayu,
thanks.
It would be good to know how latex export can be customized to achieve
this.
Depends on how much customization you are willing to go through: there is
an
enumerate.sty package in LaTeX that can do that:
--8---cut here---start-8---
...
\usepackage{enumerate}
...
\begin{enumerate}[(1)]
\item foo
\item bar
\end{enumerate}
...
--8---cut here---start-8---
Inserting the \usepackage from the org file is no problem:
--8---cut here---end---8---
#+LATEX_HEADER: \usepackage{enumerate}
...
--8---cut here---end---8---
Getting the argument to the enumerate environment in the right place is
another matter. I think the only way is to redefine
org-list-generic-to-latex
like this (add this to your initialization file, .emacs or whatever,
after you
load org):
--8---cut here---start-8---
(require 'org-list)
(defun org-list-to-latex (list optional params)
Convert LIST into a LaTeX list.
LIST is as returned by `org-list-parse-list'. PARAMS is a property list
with overruling parameters for `org-list-to-generic'.
(org-list-to-generic
list
(org-combine-plists
'(:splice nil :ostart \\begin{enumerate}[(1)]\n :oend
\\end{enumerate}
:ustart \\begin{itemize}\n :uend \\end{itemize}
:dstart \\begin{description}\n :dend \\end{description}
:dtstart [ :dtend ]
:istart \\item :iend \n
:icount (let ((enum (nth depth '(i ii iii iv
(if enum
;; LaTeX increments counter just before
;; using it, so set it to the desired
;; value, minus one.
(format \\setcounter{enum%s}{%s}\n\\item
enum (1- counter))
\\item ))
:csep \n
:cbon \\texttt{[X]} :cboff \\texttt{[ ]}
:cbtrans $\\boxminus$)
params)))
--8---cut here---end---8---
The only change is the definition of :ostart. Not a very flexible method,
but it will serve in a pinch. ngz et al. might have better ideas.
I should say that there are other ways to customize enumeration labels
in LaTeX - see e.g.
http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enumerate -
but afaict they would all require some rewiring of the above function,
similar
to the above.
Nick
Cheers,
Marius
On 2011-10-13, at 11:37 , suvayu ali wrote:
On Thu, Oct 13, 2011 at 11:11 AM, Marius Hofert
marius.hof...@math.ethz.ch wrote:
Dear all,
In the manual, I
Re: [O] Ways to make org feasible for huge files
4328, exactly the same amount of lines I have in the file. On Thu, Oct 13, 2011 at 2:07 AM, Tassilo Horn tass...@member.fsf.orgwrote: Marcelo de Moraes Serpa celose...@gmail.com writes: Wow.. this worked Torsten. Thank you. I wonder why this happens... linum-mode works with overlays to embed the numbers at the beginnig of lines. Overlays are very flexible but not too efficient, you don't want to have too many of them. Looking at linum.el, it seems it already does pooling of overlays in order not to create one overlay for any line, but I'm not sure. Could you please do M-: (length linum-overlays) RET in that large org file with linum-mode enabled and say what it returns to satisfy my curiosity? Bye, Tassilo
Re: [O] Can't have tags with a dash
Thanks. On Wed, Oct 12, 2011 at 1:08 PM, Nick Dokos nicholas.do...@hp.com wrote: suvayu ali fatkasuvayu+li...@gmail.com wrote: On Wed, Oct 12, 2011 at 7:37 PM, Marcelo de Moraes Serpa celose...@gmail.com wrote: I've noticed org can't handle a single tag with a dash in it. If I try to tag an item with 'payment-integration' for example, org turns it into two tags - ':payment:integration'. Is that intended? I believe so. Yes - look at the match syntax for tags: (info (org) Matching tags and properties) Nick
[O] org-bibtex org-exp-bibtex tutorial and config needed
I am trying to get the most of org-bibtex and org-exp-bibtex. Could anybody describe briefly his configuration and workflow? Especially with regards to reftex. Tanks -- Ezequiel Birman
Re: [O] Ways to make org feasible for huge files
For my org files my linum-overlays length is equal to the number of lines on the screen so perhaps there's something you can do to get better performance. I'm not sure what setting it would be, I'm running e24 with my own complicated linum-format. Scott On Thu, Oct 13, 2011 at 9:23 PM, Marcelo de Moraes Serpa celose...@gmail.com wrote: 4328, exactly the same amount of lines I have in the file. On Thu, Oct 13, 2011 at 2:07 AM, Tassilo Horn tass...@member.fsf.orgwrote: Marcelo de Moraes Serpa celose...@gmail.com writes: Wow.. this worked Torsten. Thank you. I wonder why this happens... linum-mode works with overlays to embed the numbers at the beginnig of lines. Overlays are very flexible but not too efficient, you don't want to have too many of them. Looking at linum.el, it seems it already does pooling of overlays in order not to create one overlay for any line, but I'm not sure. Could you please do M-: (length linum-overlays) RET in that large org file with linum-mode enabled and say what it returns to satisfy my curiosity? Bye, Tassilo
[O] property values and timestamps
I store a timestamp in a property. I create the property by typing C-c C-x p and then entering the property name, say BIRTHDAY. Then I have to enter the date manually. It would be nice if C-c ! and other timestamp creation commands were available in the minibuffer when entering property values.
Re: [O] property values and timestamps
Skip Collins skip.coll...@gmail.com wrote: I store a timestamp in a property. I create the property by typing C-c C-x p and then entering the property name, say BIRTHDAY. Then I have to enter the date manually. You can plan ahead a bit and avoid the manual entry: o enter the time stamp into the org file: C-c ! or whatever. o kill the timestamp o enter the property - when it's time to enter the value, yank the killed timestamp. It would be nice if C-c ! and other timestamp creation commands were available in the minibuffer when entering property values. But this *would* be nicer, indeed. Nick
Re: [O] property values and timestamps
Skip Collins skip.coll...@gmail.com wrote: I store a timestamp in a property. I create the property by typing C-c C-x p and then entering the property name, say BIRTHDAY. Then I have to enter the date manually. It would be nice if C-c ! and other timestamp creation commands were available in the minibuffer when entering property values. They cannot be: org-time-stamp-inactive uses the minibuffer, and calling a function that uses the minibuffer *from* the minibuffer (as org-set-property would do) make emacs unhappy. You might be able to get away with a simpler function that inserts e.g. the current timestamp without asking the user any questions, but you cannot have the full generality of C-c ! Nick
