[O] Capture template expansion: feature or bug?
Hello everyone,
When one uses the following template expansion,
> %^{prop}p Prompt the user for a value for property ‘prop’.
it supposes one to supply a non-empty string of characters. If one
simply hits RETURN on a given prompt for property, the capture process
ends with an
> org-capture: Capture abort: (quit)
message. This means that all prompts for properties are mandatory. It
this a feature or a bug?
Of course, if I ask the question, it is because I clearly see use cases
for optional properties prompts (which would leave empty the property in
question): you ask for several information, which you don't always have;
and you don't want the capture process to quit because of that. But may
be there is a better way to achieve this?
Many thanks in advance for your time!
Best,
François
--
Org 9.0.10 / Emacs 25.2.1
http://francois.allisson.co
[O] [PATCH] Tiny correction on documentation (org-capture template expansion)
Hi all,
I couldn't make use of one of the template expansion, and I found that
a backslash was missing in the documentation, and now everything works
as expected. This:
%\n Insert the text entered at the nth %^{prompt}, where n is
a number, starting from 1.
should read like this
%\\nInsert the text entered at the nth %^{prompt}, where n is
a number, starting from 1.
I attached a patch,
Many thanks to all who contribute to this best software in the world,
Best,
François
From 01dd431a07f1e236163696924acb93996e23fa2b Mon Sep 17 00:00:00 2001
From: François Allisson franc...@allisson.co
Date: Sat, 11 Apr 2015 12:05:33 +0200
Subject: [PATCH] Fix documentation for org-capture template expansion
* doc/org.texi
TINYCHANGE
---
doc/org.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/org.texi b/doc/org.texi
index dfc25dc..c400f77 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -7282,7 +7282,7 @@ dynamic insertion of content. The templates are expanded in the order given her
@r{You may specify a default value and a completion table with}
@r{%^@{prompt|default|completion2|completion3...@}.}
@r{The arrow keys access a prompt-specific history.}
-%\n @r{Insert the text entered at the nth %^@{@var{prompt}@}, where @code{n} is}
+%\\n@r{Insert the text entered at the nth %^@{@var{prompt}@}, where @code{n} is}
@r{a number, starting from 1.}
%? @r{After completing the template, position cursor here.}
@end smallexample
--
2.1.4
Re: [O] Colour themes suggestions?
Suvayu Ali fatkasuvayu+li...@gmail.com a écrit: Completely opposite of what you asked, you could checkout dark-emacs[1]. It is a very dark theme, designed to emulate emacs -nw in a black background terminal. It has some org related customisations in (custom-theme-set-variables ...) and some of the org faces are built up on other basic faces; all in all it might give you some ideas to write your own theme. [1] https://github.com/suvayu/.emacs.d/blob/master/themes/dark-emacs-theme.el I really like your dark-emacs. Just adopted it. Perfect for org-mode (and for mu4e, by the way). Thanks Suvayu Ali! François
Re: [O] org-exp-bibtex missing in git?
Le dimanche 3 mars 2013 à 08h06, Vikas Rawal a écrit: org-exp-bibtex seems to have gone missing from git repository. Can somebody confirm pleae. Vikas Dear Vikas, I do confirm. org-exp-bibtex, because of its dependency on the old exporter, was first moved from contrib/lisp to contrib/oldexp during the process of migration towards org new exporter. And yesterday, the directory contrib/oldexp was eventually removed[1]. It is still possible to checkout before this commit to rescue it, and try to update it for the new exporter (which I would do, if I was technically able to do so). In the meanwhile, checking, building, and exporting with the old exporter is still a possible option. Best, François [1] http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=ee3b3eb421e74339119d730a5bf896a070b2ed60
Re: [O] [ANN] Merge of new export framework on Wednesday
Le dimanche 3 février 2013 à 20h00, Nicolas Goaziou a écrit: I will install the new export framework along with a set of back-ends Wednesday evening (UTC). Here are a few notes to help you make the transition. That's an exciting news! Thanks for all the job already done and to be done. If the documentation is as good as this announcement, it will be great! Cheers, François Allisson
Re: [O] [PATCH] Update documentation on handling internal links
Le vendredi 8 mars 2013 à 23h35, Bastien a écrit:
Can you update your patch mentioning this and adding a commit message
and adding TINYCHANGE at the end?
Here it is.
François
From 169d8382f01b8914e002313032c2d123c86b913a Mon Sep 17 00:00:00 2001
From: François Allisson franc...@allisson.co
Date: Wed, 9 Jan 2013 12:32:09 +0100
Subject: [PATCH] org.texi: Update documentation on internal link handling
* Update the mention to the obsolete variable `org-link-to-org-use-id'
with a mention to the newer variable `org-id-link-to-org-use-id'.
* Mention the need to load the org-id library.
TINYCHANGE
---
doc/org.texi |9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 8b0a59f..c6e5b70 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -3445,13 +3445,16 @@ be the description@footnote{If the headline contains a timestamp, it will be
removed from the link and result in a wrong link---you should avoid putting
timestamp in the headline.}.
-@vindex org-link-to-org-use-id
+@vindex org-id-link-to-org-use-id
@cindex property, CUSTOM_ID
@cindex property, ID
If the headline has a @code{CUSTOM_ID} property, a link to this custom ID
will be stored. In addition or alternatively (depending on the value of
-@code{org-link-to-org-use-id}), a globally unique @code{ID} property will be
-created and/or used to construct a link. So using this command in Org
+@code{org-id-link-to-org-use-id}), a globally unique @code{ID} property will
+be created and/or used to construct a link@footnote{The library @code{org-id}
+must first be loaded, either through @code{org-customize} by enabling
+@code{id} in @code{org-modules} , or by adding @code{(require 'org-id)} in
+your @file{.emacs}.}. So using this command in Org
buffers will potentially create two links: a human-readable from the custom
ID, and one that is globally unique and works even if the entry is moved from
file to file. Later, when inserting the link, you need to decide which one
--
1.7.10.4
Re: [O] [PATCH] Update documentation on handling internal links
Le mercredi 9 janvier 2013 à 12h53, Bastien a écrit: Applied (with a small change in the ChangeLog, please check.) Perfect. Thanks!
[O] [PATCH] Update documentation on handling internal links
Hi,
The attached documentation patch updates the mention to the obsolete
variable `org-link-to-org-use-id' with a mention to the newer variable
`org-id-link-to-org-use-id'.
Furthermore, it mentions that (require 'org-id) is necessary for
`org-id-link-to-org-use-id' to work. Perhaps it is not what should be
done. Shall org-id be required by default?
Best,
and thanks all for 7.9.3a ! I'm testing.
François
From 0dc2100e3ce1da1f6a5738dd0cbc13e39d39e433 Mon Sep 17 00:00:00 2001
From: François Allisson franc...@allisson.co
Date: Tue, 8 Jan 2013 21:54:19 +0100
Subject: [PATCH] org.texi: Update documentation on `org-id-link-to-org-use-id'
---
doc/org.texi |8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 6625ed8..35adfa9 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -3445,13 +3445,15 @@ be the description@footnote{If the headline contains a timestamp, it will be
removed from the link and result in a wrong link---you should avoid putting
timestamp in the headline.}.
-@vindex org-link-to-org-use-id
+@vindex org-id-link-to-org-use-id
@cindex property, CUSTOM_ID
@cindex property, ID
If the headline has a @code{CUSTOM_ID} property, a link to this custom ID
will be stored. In addition or alternatively (depending on the value of
-@code{org-link-to-org-use-id}), a globally unique @code{ID} property will be
-created and/or used to construct a link. So using this command in Org
+@code{org-id-link-to-org-use-id}), a globally unique @code{ID} property will
+be created and/or used to construct a link@footnote{In order to use
+@code{org-id} facilities, @code{(require 'org-id)} has to be found in your
+@file{.emacs}.}. So using this command in Org
buffers will potentially create two links: a human-readable from the custom
ID, and one that is globally unique and works even if the entry is moved from
file to file. Later, when inserting the link, you need to decide which one
--
1.7.10.4
Re: [O] new exporter - subtree export and a few keywords
No answer. But I will share a trick. Good way to answer such questions is to do this: M-x find-library RET org-export RET C-s EXPORT_ and with couple of more C-s es you will end up with something like. , C-h v org-export-options-alist | KEYWORD is a string representing a buffer keyword, or nil. Each | property defined this way can also be set, during subtree | export, through an headline property named after the keyword | with the \EXPORT_\ prefix (i.e. DATE keyword and EXPORT_DATE | property). ` Thanks Jambunathan. F.
[O] new exporter - subtree export and a few keywords
Dear org-mode users and developers, The following concerns Nicolas' new exporter.^ I am totally seduced by the concept of export by subtree, and the possibility to use properties to set the export options and parameters (i.e. :EXPORT_TITLE:, :EXPORT_OPTIONS:, :EXPORT_LATEX_HEADER:, etc.). I am wondering if all that could be done by exporting the whole document can be done with exporting by subtree. So far, I am concerned by the following keywords, that I used (here with examples): #+LANGUAGE: ru and #+BIND: org-e-latex-title-command Can these be achieved by subtree export, or using another trick I am not aware of? Best, François
Re: [O] new latex exporter and attr_latex
Le jeudi 12 décembre 2012 à 15h24, Nicolas Goaziou a écrit: Or, perhaps better, since it will work across all export back-ends: | l | c| r | | left | center | right | Thanks for this cross-back-ends tips, this is indeed a powerful tool. Best, François
Re: [O] new latex exporter and attr_latex
Yes, the syntax has changed; see http://thread.gmane.org/gmane.emacs.orgmode/62766 In short, you should use: #+ATTR_LATEX: :align lcr Kind Regards, Mike Thanks. It works like that. Best thoughts, François
[O] new latex exporter and attr_latex
Hi,
The following example used to work for me
***
#+ATTR_LATEX: align=lcr
| left | center | right |
***
i.e. it was exported with the correct alignment rules. But now (Org
7.9.2-666/ Emacs 24.2.50.1), it seems to not work any more, as it get
exported as
**
\begin{center}
\begin{tabular}{lll}
left center right\\
\end{tabular}
\end{center}
**
The lll, instead of lcr is what bother me...
Any change recently around attr_latex or align?
Thanks for any help,
François
Re: [O] new latex exporter and attr_latex
Le mardi 11 décembre 2012 à 17h47, Nick Dokos a écrit: See http://thread.gmane.org/gmane.emacs.orgmode/62766 Thanks Nick! #+attr_latex: :align lcr works fine! François
[O] new latex exporter - emphasise and footnote: feature or bug?
Hello Org mode users, hello Nicolas,
Should it be possible to put a footnote immediately after an
/emphasised/ word, as in the following example?
test.org **
Hello /girls/[fn:1], how do you do?
* Footnotes
[fn:1] There were no boys in the room...
For now, the new latex exporter renders it as follows:
* Relevant passage of test.tex ***
Hello /girls/\footnote{There were no boys in the room\ldots{}}, how do you do?
*
And this is problematic: the emphasise around the word girls is exported
literally, without \emph{}. Is this a bug, or should an emphasised word
never be followed by a footnote?
Thanks.
François
Org-mode version 7.9.2 (release_7.9.2-486-g6726ae @
/Applications/Emacs.app/Contents/Resources/site-lisp/org/)
GNU Emacs 24.2.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2012-08-27
on emacsformacosx.com
Re: [O] new latex exporter - emphasise and footnote: feature or bug?
Nicolas Goaziou writes: It isn't related to the exporter. There is a limited set of charaters allowed just after an emphasis marker, and ] doesn't belong, by default, to them. You may want to tweak the post part of `org-emphasis-regexp-components'. Regards, Cristal clear! Thanks a lot. Best, François.
Re: [O] Speeding up the agenda search
Marcelo de Moraes Serpa writes: Anyone else with huge org databases out there? Any tips on improving performance of the agenda search would be appreciated :) Hi Marcello, 16 files and 3 MB: is that huge for you? Note that only 13 (1.5 MB) are agenda files; the big three others (2 databases and 1 archive file; 1.5 MB) are added to the search via org-agenda-search-extra-files. As I never had to kill a search, that is probably not huge... Best, François.
Re: [O] multiline agenda and/or two-pane agenda selection
Le lundi 15 oct 2012 à 13:10:58 (-0400), Nick Dokos a écrit : Ben mis...@emerose.org wrote: Hi all, I hope this isn't in the FAQ or documentation---I tried to look through both according to the instructions but this seems like a basic question so my apologies if I'm missing something stupid. I'm starting to use org-mode and its agenda view and like it a lot. However, I would like to modify it so one of two things happen: 1) Easy agenda navigation --- Currently I like how I can press Enter (bound to org-agenda-switch-to apparently) in the agenda view and it will show me the relevant spot in an org file. However, it replaces the agenda view with the org file, meaning I have to switch back to the agenda file and press extra keystrokes. Try SPACE instead of ENTER. Nick You can also try the follow mode, with the key F in the agenda view. And then move with n and p. If you like it and would like to make it by default, just add (setq org-agenda-start-with-follow-mode t) in your .emacs . It will perhaps even solve your second point? François.
Re: [O] Headings in agenda view
Le dimanche 14 oct 2012 à 09:00:05 (+), Renger van Nieuwkoop a écrit : Hi I have the following agenda-view in Org-Mode (p Week plan ((tags-todo Monday) (tags-todo Tuesday) (tags-todo Wednesday) (tags-todo Thursday) (tags-todo Friday) (tags-todo Saturday) (tags-todo Sunday)) nil) And would like to have a heading for every day. I tried using (org-agenda-overriding-header Monday), (org-agenda-overriding-header Tuesday), etc. at several positions, but I did not manage, to get the headers. Any hint would be more than welcome. Cheers Renger Hi Renger, The following works for me: (p Week plan ((tags-todo Monday ((org-agenda-overriding-header Monday))) (tags-todo Tuesday ((org-agenda-overriding-header Tuesday))) (tags-todo Wednesday ((org-agenda-overriding-header Wednesday))) (tags-todo Thursday ((org-agenda-overriding-header Thursday))) (tags-todo Friday ((org-agenda-overriding-header Friday))) (tags-todo Saturday ((org-agenda-overriding-header Saturday))) (tags-todo Sunday ((org-agenda-overriding-header Sunday ((org-agenda-compact-blocks t)) nil) PS: I have added compact block, just because I find it looks nicer; feel free to remove it! Best, François. -- http://francois.allisson.co
Re: [O] Problems with habit sorting
Le lundi 08 oct 2012 à 15:32:27 (+), Renger van Nieuwkoop a écrit : Hi I have an agenda-view where I can see all my habits. They have priorities but are not sorted. Any idea how to sort them according to priority. Hi Renger, You should probably customise the variable org-agenda-sorting-strategy, with the symbol priority-down, i.e. by adding this line to the definition of your custom agenda-view: (org-agenda-sorting-strategy '(priority-down todo-state-up tag-up)) You can then fine-tuning inside priorities, according to your needs (here, todo-state-up and tag-up for an example). See the docstring for org-agenda-sorting-strategy: *** * org-agenda-sorting-strategy is a variable defined in `org-agenda.el'. * Its value is ((agenda habit-down time-up priority-down category-keep) * (todo priority-down category-keep) * (tags priority-down category-keep) * (search category-keep)) * * * Documentation: * Sorting structure for the agenda items of a single day. * This is a list of symbols which will be used in sequence to determine * if an entry should be listed before another entry. The following * symbols are recognized: * * time-upPut entries with time-of-day indications first, early first * time-down Put entries with time-of-day indications first, late first * category-keep Keep the default order of categories, corresponding to the * sequence in `org-agenda-files'. * category-upSort alphabetically by category, A-Z. * category-down Sort alphabetically by category, Z-A. * tag-up Sort alphabetically by last tag, A-Z. * tag-down Sort alphabetically by last tag, Z-A. * priority-upSort numerically by priority, high priority last. * priority-down Sort numerically by priority, high priority first. * todo-state-up Sort by todo state, tasks that are done last. * todo-state-downSort by todo state, tasks that are done first. * effort-up Sort numerically by estimated effort, high effort last. * effort-downSort numerically by estimated effort, high effort first. * user-defined-upSort according to `org-agenda-cmp-user-defined', high last. * user-defined-down Sort according to `org-agenda-cmp-user-defined', high first. * habit-up Put entries that are habits first * habit-down Put entries that are habits last * alpha-up Sort headlines alphabetically * alpha-down Sort headlines alphabetically, reversed * * The different possibilities will be tried in sequence, and testing stops * if one comparison returns a not-equal. For example, the default * '(time-up category-keep priority-down) * means: Pull out all entries having a specified time of day and sort them, * in order to make a time schedule for the current day the first thing in the * agenda listing for the day. Of the entries without a time indication, keep * the grouped in categories, don't sort the categories, but keep them in * the sequence given in `org-agenda-files'. Within each category sort by * priority. * * Leaving out `category-keep' would mean that items will be sorted across * categories by priority. * * Instead of a single list, this can also be a set of list for specific * contents, with a context symbol in the car of the list, any of * `agenda', `todo', `tags', `search' for the corresponding agenda views. * * Custom commands can bind this variable in the options section. * * You can customize this variable. ** HTH, François.
Re: [O] Block-Agenda: Show whole entry
Le jeudi 04 oct 2012 à 23:27:48 (+0200), Moritz Ulrich a écrit : Hello, I'm trying to create an Agenda which will be printed / mailed daily. It should include the usual 'today' agenda and my shopping list. This shopping list is stored in an agenda file as a list with checkboxes. I want this list as the second block in my agenda. Is this possible? Hi, I don't think that this is possible, at least easily. Checkboxes are not intended to appear in agendas [1]. You can still play with a few variables in your agenda block definition, or with functions and/or a minor mode [2]. But it looks far simpler if your shopping list appears in one of your agenda files as headlines, with either a shopping specific keyword, or a specific tag, hand by hand with a nice shopping org-capture template. Eventually, you could retrieve your checkboxes by adding [3] in your second agenda block ;-) I cannot help you more... but if you find some solution, please share it! Cheers, François. [1] http://lists.gnu.org/archive/html/emacs-orgmode/2010-06/msg00765.html [2] e.g. org-agenda-entry-text-mode, org-agenda-add-entry-text-maxlines, org-agenda-entry-text-maxlines, org-agenda-entry-text-show, etc. [3] (org-agenda-todo-keyword-format [ ])
Re: [O] Cached agenda views?
Le jeudi 06 sep 2012 à 08:54:04 (-0500), Marcelo de Moraes Serpa a écrit : Hi list, It's a known fact that the more files you put into the agenda, the more likely it is to become slower. I've started using Memacs a few weeks ago, and my agenda is still very useable, but significantly slower than before (due to the big amount of temporal data being processed from my gmail emails and git logs). I was wondering if it would be possible to NOT regenerate the agenda everytime. I think this would mean parsing the org files and dumping the elisp objects created somehow. This way, when visiting the agenda again, it would be loaded from the objects dump and would not go through the parsing of all the agenda files again, unless forced by the user; or within a specific time, via a cron or internal emacs timer. This would also, in theory, allow the agenda to be constantly regenerated in a background worker process. What do you think? Cheers, - Marcelo. Hi Marcello, Have you tried sticky agendas (`*' to toogle on/off in the org-agenda menu)? One of its many uses is to *not* regenerate an agenda each time it is called, but only when the user wants it. Cheers, François.
Re: [O] Narrow to sparse tree
Le jeudi 06 sep 2012 à 15:46:42 (+0200), Christopher Witte a écrit : I keep a bibliography in an org file using the excellent org-bibtex functionality. It has over 100 entries with a first level heading for each item. I tag each of the items with keywords/topics. Using sparse trees I can quickly find and navigate to items matching a particular tag, but if only 4 items out of the 100 have that tag the signal to noise is pretty bad. What I would like to do is narrow the buffer to just those entries that match the tag. I've looked in the manual but I couldn't find a way to do this. Can this be done with org? Thanks for the help, Chris. ps. using M-g n or M-g M-n (next-error) with sparse trees I expected it to wrap when you reach the end of the file but sadly this is not the case. Is there a reason for this? Hi Chris, Have you think of using the agenda views? In four keystrokes, you're there with the best signal to noise ratio: - `C-c a' (or M-x org-agenda) - `' (to restrict the agenda view to the current buffer) - `m' (for tags, property and todo keywords) - `abc' (for tag :abc:), or (`YEAR'=2010 for PROPERTY :YEAR: equal to 2010, etc). HTH, François. PS: +1 for the excellent org-bibtex functionality !
Re: [O] Narrow to sparse tree
Le jeudi 06 sep 2012 à 17:02:06 (+0200), Christopher Witte a écrit : That's great, it gets me part of the way there. I also keep notes for each reference under their heading and I'd like to be able to see/edit them as well. Is there a way to do this in an agenda buffer? Just press space, enter or tab on any of your results. Notice the different behaviours between the three commands, and choose your favourite depending on the context (mine is space anyway). François.
Re: [O] Strange Problem with org-agenda-redo
Thanks a lot! I confirm that everything works just fine. And not just as before, but better than before: I like the fact that, in a block agenda view, one agenda can move in time independently from another one. I'll play with that a bit and give you some feedback on it. Yes -- also note that `r' and `g' now refresh differently in multi agendas. `r' keep the temporary parameters for the agenda under the point, while `g' restore the view from scratch (discard temporary change in the time span etc.) I think this is useful -- at least more useful than a half-broken state of multi-agendas handling :) -- Bastien Hi Bastien, After several tests with multiple agendas in a block agenda view, I just found one strange case (or perhaps it is a feature?): When one tries `.' (org-agenda-today) on an agenda that is either in the past or in the future, *and* if another agenda already shows today's day, then the cursor just jump to that other agenda, and does not go to today on the current agenda. Except for that case, all other commands (`f', `b', `r', `g', etc.) and situations work in that context as one would expect them to work. This is nice! Thanks, François
Re: [O] Please consider making a donation
BTW, if it is to give you money, why not cut the middlemen and provide your IBAN ?(As a fellow countryman, it saddened me to pay for €→$(→€ ?) and to Visa™ and PayPal™ (which I despise) for naught. Here you go: http://lumiere.ens.fr/~guerry/u/bastien_guerry_rib_2012.jpg +1 (iban)
Re: [O] Strange Problem with org-agenda-redo
Le lundi 27 aoû 2012 à 18:19:10 (+0200), Bastien a écrit : Hi Charles, Charles Philip Chan cpc...@bell.net writes: I have a strange problem with org-agenda-redo and I hope that someone can shed some light. I have an Agenda view which contains everything I need for the day which I leave open all the time. The agenda view already contains a schedule for the current day. A couple of days ago I decided to add another block I called Upcoming Events which contains a schedule for the next 6 days (I prefer a separate section, so that I can easily ignore it rather then having a 7 days block). Everything is working fine with the exception that after I mark a TODO (scheduled/deadline) or HABIT as done, all my appointment, habits, scheduled and deadline items disappear from the view after I save all Agenda files and force a redisplay (s g). If I quite the view and enter it again through the dispatcher, everything is displayed again. Mhh... This was a real bug, I had a good sweat on this one. Building agenda blocks didn't behave correctly with multiple (agenda) commands, because it reused the parameters of the last (agenda) command as the default for redoing. This is now fixed. Note that, while fixing this, I added the possibility to change the time span of one block independantly from the other: try `f' in one of your block, it should move to the next day/week and leave the other blocks untouched. Hi Bastien, Hi Charles, Since these changes, I have some troubles with a few org-agenda commands (goto-today, redo, switch to day view, week view, etc.). This happens with multiple blocks custom agenda views (whether there are, or not, multiple agendas in them). Does it work for you, or shall I send an ECM? Best, François. --- Org-mode version 7.9 (release_7.9-133-g1f205a @ /usr/local/share/emacs/site-lisp/org/) GNU Emacs 24.2.50.1 (i686-pc-linux-gnu, GTK+ Version 2.24.10) of 2012-08-21 on debian
Re: [O] Strange Problem with org-agenda-redo
Hi Bastien and Charles, Let me know if you still have this. Thanks! I can't even go into the Agenda view now. Here is the backtrace: , | Debugger entered--Lisp error: (void-variable org-agenda-overriding-cmd) I've just get into the same problem and backtrace... François.
Re: [O] Strange Problem with org-agenda-redo
Le mercredi 29 aoû 2012 à 14:33:17 (-0400), Charles Philip Chan a écrit : Bastien b...@altern.org writes: Hi Bastien: Ops. Fixed! Thanks for all the hard work. Things are working fine now and I see no strangeness. The only thing is, for consistency sake, shouldn't j jump to the specified date in place rather then bringing up a new Agenda buffer? Cheers, Charles Thanks a lot! I confirm that everything works just fine. And not just as before, but better than before: I like the fact that, in a block agenda view, one agenda can move in time independently from another one. I'll play with that a bit and give you some feedback on it. Best, François
Re: [O] Org-mode release 7.9
Hi Bastien, Le vendredi 24 aoû 2012 à 17:48:42 (+0200), Bastien a écrit : Hi all, I've released Org 7.9. http://orgmode.org/org-7.9.zip http://orgmode.org/org-7.9.gz http://orgmode.org/org-mode-download.html After 1885 commits since Org 7.8, it was about time. See the list of changes here: http://orgmode.org/Changes.html Excellent. I've started to use Org with the release 7.7 less than a year ago. It was already *very* good. It is amazing to see, with this huge list of changes, how it improved every single day since my first use of it. *A big thank* to you and all of those who participate to this splendid piece of emacs. BTW, Org 7.9. compiles and runs without problem on my debian/emacs 24.2.50.1. Cheers, François.
[O] [BUG] shell links broken
Hello list, Since last update of org this morning, I cannot open shell links any longer. Instead, I get the message void-variable clean-buffer-list-kill-buffer-names in the mini-buffer. Commit 96551f3dd8885dee6972c70ce06888fd3d5f4dd4 (http://orgmode.org/w/?p=org-mode.git;a=commit;h=96551f3dd8885dee6972c70ce06888fd3d5f4dd4) seems to be responsible. I don't understand the idea behind this huge commit (I just started to read the elisp intro, since all my e-life is in org now, it's time to start understanding the tool I use ;-) hopefully I'll be more useful in some time for these kind of stuffs). Anyway, below are potentially useful stuffs to reproduce the bug. Best, François Versions: Org-mode version 7.8.11 (release_7.8.11-366-g6f571d @ /usr/local/share/emacs/24.1.50/site-lisp/org/) GNU Emacs 24.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.24.10) of 2012-08-02 on debian -*ecm.org* * An eshell link [[shell:echo 'Hello!'][My shell is polite.]] -*Backtrace*-- Debugger entered--Lisp error: (void-variable clean-buffer-list-kill-buffer-names) org-open-at-point(nil) call-interactively(org-open-at-point nil nil) -- -*minimal-org.el*- (setq debug-on-error t debug-on-signal nil debug-on-quit nil) (add-to-list 'load-path (expand-file-name /usr/local/share/emacs/24.1.50/site-lisp/org)) (require 'org-install) --
Re: [O] [BUG] [PATCH] shell links broken
Hi Bastien
Le dimanche 05 aoû 2012 à 11:41:36 (+0200), Bastien a écrit :
Hi François,
François Allisson franc...@allisson.co writes:
Since last update of org this morning, I cannot open shell links any
longer. Instead, I get the message void-variable
clean-buffer-list-kill-buffer-names in the mini-buffer.
Fixed, thanks.
Thanks! I confirm it works.
As I was pulling your latest fix, I noticed there was a little typo in
org.texi. I hope the attached patch will help fix it.
All the best,
François.
From 7277580fd27d91c22e5dbc701af6862392c58a3e Mon Sep 17 00:00:00 2001
From: François Allisson franc...@allisson.co
Date: Sun, 5 Aug 2012 14:07:10 +0200
Subject: [PATCH] org.texi: Fix typo
* doc/org.texi: Remove extra curly bracket.
TINYCHANGE
---
doc/org.texi |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/org.texi b/doc/org.texi
index 44aa362..3fdb4ac 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -5020,7 +5020,7 @@ TIMESTAMP_IA @r{The first inactive timestamp in the entry.}
CLOCKSUM @r{The sum of CLOCK intervals in the subtree. @code{org-clock-sum}}
@r{must be run first to compute the values in the current buffer.}
CLOCKSUM_T @r{The sum of CLOCK intervals in the subtree for today.}
- @r{@code{org-clock-sum-today}} must be run first to compute the}
+ @r{@code{org-clock-sum-today} must be run first to compute the}
@r{values in the current buffer.}
BLOCKED @r{t if task is currently blocked by children or siblings}
ITEM @r{The headline of the entry.}
--
1.7.10.4
[O] [BUG] sticky agenda views and export
Hello, I am testing sticky agenda views, and I think in my case it is a great thing (because I have two custom agenda views that I often check). I sometimes export my custom agenda views with the e key in the org-agenda buffer, or with M-x org-store-agenda-views, and it works well. But when I tried the same export with sticky agenda views enabled, I get the following (reproducible with a minimal configuration) error: org-batch-store-agenda-views: No buffer named *Org Agenda(e)* It seems that org-batch-store-agenda-views is not aware of the existence of the new buffer names according to sticky agenda views, i.e. *Org Agenda(%s), and wait for *Org Agenda buffers. Here are the versions I use: - Org-mode version 7.8.11 (release_7.8.11-296-g8e8955 @ /usr/local/share/emacs/24.1.50/etc/org) - GNU Emacs 24.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.20.1) of 2012-07-13 on debian Thanks for having a look, François.
Re: [O] Year or Month Agenda view without empty days
Le dimanche 15 jui 2012 à 12:38:03 (-0400), James Harkins a écrit : If I set up a custom agenda command for 30 days, I get stuff like this: Month-agenda (W28-W33): Sunday 15 July 2012 Monday 16 July 2012 W29 Tuesday17 July 2012 Wednesday 18 July 2012 Thursday 19 July 2012 agenda_main:12:00.. Scheduled: Sushi then Blueberry fest :Trip2012:: The problem is, in MobileOrg, I see a list of days first, no indication which days have anything in them. So I would like to have this agenda view include only days with items in them: Month-agenda (W28-W33): Thursday 19 July 2012 agenda_main:12:00.. Scheduled: Sushi then Blueberry fest :Trip2012:: *Maybe* include Monday 16 July 2012 W29 for the week number. Then in M-org, I would know if I expand a day, that there's something inside. Possible? The customize interface reveals no settings that would seem to apply. Hi James, The variable org-agenda-show-all-dates is done for you (default value t). Change its value for nil to show only the days with something inside. Either in your custom agenda view, or globally in the customize interface (Org Agenda - Org Agenda Daily/Weekly - Org Agenda Show All Dates). (See also the new useful doc page on Worg: http://orgmode.org/worg/doc.html#org-agenda-show-all-dates) However, this does not answer the other part of your question, i.e. include the Mondays for Week Numbers... HTH, François hjh -- James Harkins /// dewdrop world jamshar...@dewdrop-world.net http://www.dewdrop-world.net Come said the Muse, Sing me a song no poet has yet chanted, Sing me the universal. -- Whitman blog: http://www.dewdrop-world.net/words audio clips: http://www.dewdrop-world.net/audio more audio: http://soundcloud.com/dewdrop_world/tracks
Re: [O] Organizing a collection of papers
Hi Victor, Le lundi 04 jun 2012 à 00:57:53 (+), Victor Miller a écrit : I've just started using org-mode, and so far find it quite useful. I have a very large collection of technical papers in a directory tree, and I'd like to go through them and index them through org-mode. What I'd like is to have a way of going through them and look at the unannotated ones, and annotate them one by one. I imagine doing this by first making up a file of links like [[xxx.pdf][not done yet]], The script dir2org.zsh (located in the contrib/scripts directory) may be a good starting point for you. It transforms (recursively) a directory and all its files into an Org mode file reproducing the directory tree hierarchy with one headline per file, and it creates automatically the links to the files. Briefly, if your files are located in the directory ~/my-big-database (and its sub-directories), just type: - cd path-to-org-mode-distribution-directory/ - cd contrib/scripts - zsh(if, like me, zsh is not your usual shell, you must call it, eventually install it; at the end, type exit to return to your favourite shell) - ./dir2org.zsh ~/my-big-database orgfile.org And it's done. Your orgfile.org contains linked headlines for all your files. You can then start playing with your files with all the Org mode facilities (tags, ordering headlines, adding properties, annotations, todos, etc.). HTH. and then being presented with the not done ones, glancing at them and deciding how what annotations to put in. In addition I'd like to add tags. What I'd really like is to be able to make up new tags on the fly. Has anyone done anything like this in org-mode? I don't know what will be the better workflow to achieve this. I think we are all looking for the best workflow to handle our electronic (and non electronic) libraries. I cannot say yet what my workflow is, because I'm currently working on it. FWIW, I /was/ handling my bibliographic resources in a big BibTeX file, adding custom BibTeX fields for my personal needs. I can only give hint whither I am going: - a big biblio.org file with a lot of headlines (one per item), with three custom todo keyword (in a sequence TOREADLATER TOREAD | READ) - TOREAD: for items on which I still have something to do (read, annotate, decide whether it is worth reading or not, or if I should do something with it, etc.). These appear in my custom agenda-view as a block name Currents readings. - TOREADLATER: idem. But these items do *not* appear in my custom agenda-view. - READ: for items on which I'm done. - each item has a name Author (year) Title of document, it contains tags as keywords, BibTeX properties (using org-bibtex.el), custom properties (physical location if not electronic, date of insert, etc.). It contains link to file (if file). And it contains my reading notes, quotes, comments, TODO items (if I have to check something, or discuss something with someone, I plan it). All this using sub-headings (for respecting chapters, or the papers structure, or other subdivision for my own needs. As this file is in my org-agenda-files, I can take advantage of all Org mode facilities. I can export the whole database as a BibTeX file using only one command (M-x org-bibtex, thanks to the excellent org-bibtex.el), and can use it in my Org mode files (formerly LaTeX files), using the (new) latex exporter. I can also export a headline with the (new) exporter to share my notes on one item with someone (and easily decide which parts of the notes not to share with a few :noexport: headlines) When I have free time (...) or when (I recommend doing this) I scheduled reading hours in my week, I just call my custom agenda command, showing me only TOREAD items, I'm one space key away from my biblio.org file, and I can just fill my notes while reading. I decided to restrict myself to 5 TOREAD keywords. Once a TOREAD is done, it becomes READ and disappear from my agenda view. Once my TOREAD list becomes empty, I decide which TOREADLATER becomes TOREAD (again with the rule of 5). It helps me not starting dozens of things and never finish them... As for the capture of new items, I'm still working on it. I started to use the command M-x org-bibtex-create for new items, and then arrange manually my other needs, but I'm now in the process of creating custom org-capture templates to better achieve my needs. I would happily share a less confused state of my workflow when I'll be more happy with it. Sorry for being such OT. Victor Good luck with your collection of papers, Cheers, François
Re: [O] Makefile restructuring
Achim's branch is now merged in Org's git master branch. Please test this and report any problem while using make to install Org. -- Bastien It runs smoothly for me, using make clean, make, make doc, and make install (without local.mk, having yet no need of it). François.
[O] contrib/README update
Hello, This is a really non-urgent patch, proposing an update of the README file in org-mode contrib directory. Best, François. From c9f9149f358ac97352f2a752bad115705ed01fed Mon Sep 17 00:00:00 2001 From: François Allisson franc...@allisson.co Date: Sat, 21 Apr 2012 14:54:52 +0200 Subject: [PATCH] Update of contrib/README --- contrib/README | 34 -- 1 files changed, 24 insertions(+), 10 deletions(-) diff --git a/contrib/README b/contrib/README index 65a1459..bd8aff4 100644 --- a/contrib/README +++ b/contrib/README @@ -5,13 +5,14 @@ package. But the git repository for Org-mode is glad to provide useful way to distribute and develop them as long as they are distributed under a free software license. -Please put your contribution in one of these three directories: +Please put your contribution in one of these directories: LISP (emacs-lisp code) == htmlize.el --- Convert buffer text and decorations to HTML org2rem.el --- Convert org appointments into reminders org-annotate-file.el --- Annotate a file with org syntax +org-bibtex-extras.el --- Extras for working with org-bibtex entries org-bookmark.el --- Links to bookmarks org-checklist.el --- org functions for checklist handling org-choose.el--- Use TODO keywords to mark decision states @@ -20,46 +21,59 @@ org-contacts --- Contacts management org-contribdir.el--- Dummy file to mark the org contrib Lisp directory org-depend.el--- TODO dependencies for Org-mode org-drill.el --- Self-testing with org-learn -org-depend.el--- TODO dependencies for Org-mode +org-element.el --- Parser and applications for Org syntax org-elisp-symbol.el --- Org links to emacs-lisp symbols -org-eshell.el--- Support for links to working directories in eshell org-eval.el --- The lisp tag, adapted from Muse org-eval-light.el--- Evaluate in-buffer code on demand org-exp-bibtex.el--- Export citations to LaTeX and HTML org-expiry.el --- Expiry mechanism for Org entries +org-export.el--- Generic Export Engine For Org org-export-generic.el--- Export framework for configurable backends org-git-link.el --- Provide org links to specific file version org-interactive-query.el --- Interactive modification of tags query org-invoice.el --- Help manage client invoices in OrgMode org-jira.el --- Add a jira:ticket protocol to Org org-learn.el --- SuperMemo's incremental learning algorithm -org-lparse.el--- Library for building custom exporters org-mac-iCal.el --- Imports events from iCal.app to the Emacs diary org-mac-link-grabber.el --- Grab links and URLs from various Mac applications org-mairix.el --- Hook mairix search into Org for different MUAs org-man.el --- Support for links to manpages in Org-mode org-mime.el --- org html export for text/html MIME emails org-mtags.el --- Support for some Muse-like tags in Org-mode -org-odt.el --- OpenDocumentText exporter for Org-mode +org-notify.el--- Notifications for Org-mode +org-notmuch.el --- Support for links to notmuch messages org-panel.el --- Simple routines for us with bad memory org-registry.el --- A registry for Org links org-screen.el--- Visit screen sessions through Org-mode links org-secretary.el --- Team management with org-mode -org-special-blocks.el--- Turn blocks into LaTeX envs and HTML divs +org-static-mathjax.el--- Muse-like tags in Org-mode org-sudoku.el--- Create and solve SUDOKU puzzles in Org tables orgtbl-sqlinsert.el --- Convert Org-mode tables to SQL insertions org-toc.el --- Table of contents for Org-mode buffer org-track.el --- Keep up with Org development org-velocity.el --- something like Notational Velocity for Org -org-wikinodes--- CamelCase wiki-like links for Org +org-wikinodes.el --- CamelCase wiki-like links for Org + + +BABEL += +library-of-babel.org --- Documentation for the library of babel +langs/ob-fomus.el--- Org-babel functions for fomus evaluation +langs/ob-oz.el --- Org-babel functions for Oz evaluation -PACKAGES - +ODT (OpenDocumentText) +== +README.org --- Legacy documentation for Org ODT exporter + SCRIPTS (shell, bash, etc.) === dir2org.zsh --- Org compatible fs structure output -org2hpda --- Generate hipster pda style printouts from Org-mode ditaa.jar--- ASCII to PNG converter by Stathis Sideris, GPL +org2hpda --- Generate hipster pda style printouts from Org-mode +org-docco.org--- docco side-by-side
Re: [O] Makefile restructuring
Le samedi 21 avr 2012 à 20:30:49 (+0200), Achim Gratz a écrit : Martyn Jago writes: Works nicely for me too, and I have a modified local.mk config for multiple Emacs versions and a non-default org location. Note: `make install check' will make, install, and run the tests! Actually, make up2 will update all remotes, do a git pull on the current branch, compile and test and then finally install org all in one go. Once you have set things up the way you like, that's the fastest way to keep current. The real advantage however is that if there happens to be an error someplace, make is smart enough to stop right there and not install a not-quite working org over an older, but working version. Thanks Martyn and Achim for hints on make install check and make up2. The latter is exactly what I needed. Achim's restructuring made me just realise the utility and power of these Makefile rules... It's so nice to learn by using org. Best, François.
[O] Ever used org-mode contrib packages?
Hello, I've just updated the index of contributed packages on Worg [1]. Have a look, it is full of treasures... Out of the 61 listed contributions: - 43 are hosted on Org-mode's contrib/lisp/ directory - 9 are hosted elsewhere - 9 are already incorporated into the core of org-mode, but remain here for documentation purposes. (Well, 9 is not the right number, since org-babel amounts only for 1 in these stats...) As for the documentation, 24 packages have a dedicated documentation page on Worg (once again, 1 tree of pages for org-babel). Fell free to document those you find useful. On my side, I am only discovering the contrib/lisp directory, but have already tested with profits org-contacts and org-mairix. I'm curious to know what you are using from org-contrib... All the best, François. [1] http://orgmode.org/worg/org-contrib/index.html
Re: [O] [PATCH] Fix broken links in worg (org-contrib/index.org)
Le dimanche 08 avr 2012 à 10:54:49 (-0400), Bernt Hansen a écrit : François Allisson franc...@allisson.co writes: Hello worgers, I've noticed that all links to raw files (.el) on http://orgmode.org/worg/org-contrib/index.html are broken. They used to be pointers to repo.or.cz. The attached patch reactivates these links with pointers to the new orgmode.org git repository. This is my first patch (not to worg, but ever), and I'm still learning how to use git and so on, so please tell me how I could make better patches in the future. Hi François, This patch looks great to me (although I didn't test it). For worg patches you can request commit access directly and just apply the patch yourself. Hi Bernt, Thanks for you answer. I've just asked for a push access. Regards, François. I don't think we need changelog entries for worg patches (only for org-mode source). Please correct me if that's wrong. Regards, Bernt
Re: [O] [PATCH] Fix broken links in worg (org-contrib/index.org)
Hi François, François Allisson franc...@allisson.co writes: I've noticed that all links to raw files (.el) on http://orgmode.org/worg/org-contrib/index.html are broken. They used to be pointers to repo.or.cz. The attached patch reactivates these links with pointers to the new orgmode.org git repository. Great, thanks a lot. This is my first patch (not to worg, but ever), and I'm still learning how to use git and so on, so please tell me how I could make better patches in the future. I applied this patch. Thanks Bastien! BTW, org-contrib/index.org needs an update on a few additional points: - A few new contributions in contrib/lisp are not listed here. - A few contributions passed into the core of org. This should be commented, together with link to the relevant sections in the documentation (org.texi), etc. - A lost last version of org-refer-by-numbers.el - A decision to take with links to raw-files that were removed from the org-mode git repository: either link them to legacy raw file from org-mode git, or remove these links Let's use legacy raw files. OK. - and a few other tiny things... I would happily take care of that, or help anyone in doing it. I welcome any advice on that. Please go ahead -- it's nice to have someone taking care of this area! I'll take care of that very soon. -- François Thanks again, -- Bastien
[O] [PATCH] Fix broken links in worg (org-contrib/index.org)
Hello worgers,
I've noticed that all links to raw files (.el) on
http://orgmode.org/worg/org-contrib/index.html are broken. They used
to be pointers to repo.or.cz. The attached patch reactivates these
links with pointers to the new orgmode.org git repository.
This is my first patch (not to worg, but ever), and I'm still learning
how to use git and so on, so please tell me how I could make better
patches in the future.
BTW, org-contrib/index.org needs an update on a few additional
points:
- A few new contributions in contrib/lisp are not listed here.
- A few contributions passed into the core of org. This should be
commented, together with link to the relevant sections in the
documentation (org.texi), etc.
- A lost last version of org-refer-by-numbers.el
- A decision to take with links to raw-files that were removed from
the org-mode git repository: either link them to legacy raw file
from org-mode git, or remove these links
- and a few other tiny things...
I would happily take care of that, or help anyone in doing it. I
welcome any advice on that.
Thanks for all your job in org and worg,
A happy Org user,
François.
From 8979cc24cefea89d227d13a27f4dfbf7e8f42dec Mon Sep 17 00:00:00 2001
From: François Allisson franc...@allisson.co
Date: Sun, 8 Apr 2012 11:56:29 +0200
Subject: [PATCH] Fix broken links on worg/org-contrib/index.org
* worg/org-contrib/index.org: Added a repofile link definition with
pointer to the orgmode.org git repository, because most links to raw
(.el) files depended on that missing definition.
* worg/org-contrib/index.org: Fixed two additional links.
---
org-contrib/index.org |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/org-contrib/index.org b/org-contrib/index.org
index e8e5467..35aa013 100644
--- a/org-contrib/index.org
+++ b/org-contrib/index.org
@@ -7,6 +7,7 @@
#+EMAIL: bzg AT altern DOT org
#+LANGUAGE: en
#+CATEGORY: worg
+#+LINK: repofile http://orgmode.org/w/?p=org-mode.git;a=blob_plain;f=%s;hb=HEAD
[[file:../index.org][{Back to Worg's index}]]
@@ -166,7 +167,7 @@ hopefully have some documentation.
Written by /Reimar Finken/.
[[repofile:contrib/lisp/org-git-link.el][Link to raw file]].
-- [[http://julien.danjou.info/google-weather-el.html][org-google-weather.el -- weather forecast in the agenda buffer]] ::
+- [[http://julien.danjou.info/software/google-weather.el][org-google-weather.el -- weather forecast in the agenda buffer]] ::
Allow %%(org-google-weather New York) sexps for displaying weather
forecast in the agenda buffer.
Written by /Julien Danjou/.
@@ -215,7 +216,7 @@ hopefully have some documentation.
This approximates a WYSiWYG HTML mail editor from within Emacs, and
can be useful for sending tables, fontified source code, and inline
images in email. Written by /Eric Schulte/.
- [[repofile:lisp/org-mime.el][Link to raw file]].
+ [[repofile:contrib/lisp/org-mime.el][Link to raw file]].
- /org-mtags.el/ -- support for some Muse-like tags in Org-mode ::
This package allows you to write =example= and =src= and other
--
1.7.5.4
Re: [O] Agenda not working
Hello Toni, When I type M-x org-agenda-list with this file (...) I get this agenda view: (...) That displays nothing. Am I doing something wrong? Why the TODO task is not displayed? There is nothing wrong with your file. It is just that it must be added to the org-agenda-files variable to be taken into account. See http://orgmode.org/manual/Agenda-files.html Best regards, François (orgmode enthusiastic newbie)
