Re: [Orgmode] Bug: return key does not show the subtree the first time on a newly opened org file
Carsten Dominik [EMAIL PROTECTED] writes: Yes, but only with this setting will return key be added to the org-mouse-map key map, and be bound to org-open-at-point command under certain contexts (like on the leading stars of a heading). Further, org-open-at-point is advised by org-mouse.el, which will do org-cycle under certain contexts. Yes, this is really an accidental feature by a sequence of events: org-return-follow-link will add org-return to the mouse-map org-mouse.el will activate the stars in a headline Yes, there is an advice for this in org-mouse.el. I think we should remove it since org-mouse.el shouldn't change the behavior of keystrokes (only the behavior of the mouse.) -- Bastien ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Active timestamp with notification in advance
On Feb 28, 2008, at 11:19 AM, Bastien wrote:
Carsten Dominik [EMAIL PROTECTED] writes:
On Feb 28, 2008, at 3:05 AM, Wanrong Lin wrote:
For SCHEDULED and plain active time stamp, I don't think we need to
have a default ahead notification setting as with deadlines, but it
would really be nice to support the . -3d format. It would be
even nicer to have a new keyword (like SCHEDULED@) that indicates
a strictly scheduled item (just a fancy term for appointment) and
hence a default ahead notification setting can be applied. The lack
of real appointment support in org-mode in fact is a little bit
puzzling to me, since SCHEDULED item may or may not be strictly
scheduled, while plain time stamp item may or may not be something
that needs to take actions on (as it could be just an event).
Hmmm, lets discuss this for a while.
It looks like there are two questions here: whether we should have a
dedicated syntax for appointments, distinct from active timestamps,
and
whether we should allow warnings on other timestamps than deadline
ones.
(Maybe a good thing to keep these issue separate as long as possible.)
I don't feel the need of a new APPOINTMENT keyword, or a SCHEDULED@
one,
because I'm using timestamps like this:
- active timestamps for appointments;
- SCHEDULED timestamps for items that (1) need to remain in the agenda
when they are not DONE, and (2) I don't need to be warned about;
- DEADLINE for everything else that I need to attach a date with.
I guess this setup is somewhat counter-intuitive for newcomers, since
the semantic of SCHEDULED makes you believe this is what you need for
most tasks. But I think this semantic is somewhat misleading.
Yes, time has shown tat it is misleading. This is unfortunate,
but I don't think we can move always from this. Too many people
are using this already, and we need to stay compatible and if possible
we should not add complexity.
- Carsten
With the setup above, I tend to use more and more active timestamps
and
deadlines. The need for a scheduled item is very rare, since the two
specific features of SCHEDULED is that I won't be warned about such
tasks and I will be able to find them with `org-check-before-date'...
So, rather than introducing a new keyword, I'd better get rid of them
and redefine timestamps like this:
[2008-02-28 jeu] Inactive timestamp
2008-02-28 jeu Active timestamp
{2008-02-28 jeu} Interactive timestamp
By interactive, I mean that those timestamps would be aware of
`org-deadline-warning-days' and other variables like this one, or be
able to stay in the agenda if the associated task is not DONE, etc.
For exemple:
{2008-02-28 jeu -10d}
= Warn 10 days before
{2008-02-28 jeu -10d--+2d}
= Warn 10 days before and 2 days after, if not DONE
Active timestamp would also use this syntax, but for the purpose of
defining *time spans*, not pre- and post-reminders.
For example:
2008-02-18 jeu +3d
= Define an appointment for a meeting between
2008-02-28 and 2008-02-21.
I'm aware that this change would require a careful redefinition of the
use of scheduled and deadline in variable names and in the manual,
but I think that it would finally help simplifying things a bit.
In a sense, relying spontaneous understanding that people have of the
words SCHEDULED and DEADLINE can be a bit dangerous -- or simply
assumes too much about the normal use of those kinds of timestamps.
--
Bastien
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Bug: return key does not show the subtree the first time on a newly opened org file
Bastien Guerry wrote: Carsten Dominik [EMAIL PROTECTED] writes: Yes, but only with this setting will return key be added to the org-mouse-map key map, and be bound to org-open-at-point command under certain contexts (like on the leading stars of a heading). Further, org-open-at-point is advised by org-mouse.el, which will do org-cycle under certain contexts. Yes, this is really an accidental feature by a sequence of events: org-return-follow-link will add org-return to the mouse-map org-mouse.el will activate the stars in a headline Yes, there is an advice for this in org-mouse.el. I think we should remove it since org-mouse.el shouldn't change the behavior of keystrokes (only the behavior of the mouse.) That probably is true. But I have doubt that removing the advice itself and bind the key in some other place will really solve the problem. To me, it seems somehow the first time you open a org-file, some context is not recognized correctly and hence the key map is not activated. If I just execute a command, any command (like C-g which does nothing), and then press the return key, it will work. Is that puzzling? :-) Wanrong ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Active timestamp with notification in advance
Carsten Dominik wrote: Thanks a lot for the suggestions, but manual workaround does not work for me, as I want org to take care of giving me a notification in advance in the agenda buffer. For SCHEDULED and plain active time stamp, I don't think we need to have a default ahead notification setting as with deadlines, but it would really be nice to support the . -3d format. It would be even nicer to have a new keyword (like SCHEDULED@) that indicates a strictly scheduled item (just a fancy term for appointment) and hence a default ahead notification setting can be applied. The lack of real appointment support in org-mode in fact is a little bit puzzling to me, since SCHEDULED item may or may not be strictly scheduled, while plain time stamp item may or may not be something that needs to take actions on (as it could be just an event). Hmmm, lets discuss this for a while. One thing is that I have been thinking for a while already if we should have an APPOINTMENT keyword to mark plain time stamps that actually are appointments, and in this way to differentiate them from events that you'd like to have in your agenda. However, about ahead warnings of appointments. The way I see it is this: One important goal (at least for me) is to keep my agenda as empty as possible, listing only the things I really need to do. If I have a meeting in a few days and I get an ahead warning, this only distracts me. Because each time I see that reminder, I need to think *again* why I did put that reminder and what I am supposed to be doing to prepare it. Isn't is much better to just put the meeting on the agenda with a timestamp and then immediately think about *tasks* that I need to do before the meeting. List those tasks under the meetig headline, and assign deadlines to them - you will get the ahead warning. This seems to me is a much saner way of working. But I am interested to hear your use case - why do you want to be reminded of future appointments *each* time you look at your list for today? For meetings where I do not have anything to prepare, I do take a look every morning on an extended agenda of 10 days, to see what is coming. Once a day, and that is it. - Carsten A simple example is: sometimes I have very early dental appointment, like 8:00AM. But usually I don't get up that early. So if I open my computer at 9:00AM and find out I have missed an appointment, then the agenda is useless. And I will get haunted by the feeling that I might still have missed something even if I checked my agenda. I do agree that too many ahead notifications is distracting. But on the other hand, my imagination of the ideal org usage is: I look at today's agenda, and things are planned well for me, I just need to follow the agenda blindly (well, ideally). This is the reward for my upfront planning, meaning if I take my diligence in planning tasks when the issues just come up, I don't have to hassle around in the last minute. I want to have that security feeling of I won't miss anything if I checked my agenda. To achieve that goal, sometimes I need some sense of what is going to happen or what I am supposed to do tomorrow, or next a few days, depending on the task and context. To check agendas ahead every day is a good habit, but is not reliable, and I want to eliminate dependency on those habits as much as possible. I want to rely on only one habit: check today's agenda. To reduce the distractions from those ahead notifications, we can do the following: 1. Don't give too early notifications. In my above example, probably one day ahead is good enough 2. Group those ahead notifications at the end of today's agenda, maybe with a divider to separate them out. Another perspective to my above argument is: many of us use org (and emacs) because of its flexibility. It is not the easiest to learn to use, but once you master it, you can configure it to suit your own style. And hence I don't expect everyone will agree with my planning strategy, but if let's say 1/3 of the users think the feature has its value, I think it is well worth consideration, given it is an option that does no harm to people who choose not to use it. Thanks for reading this. Wanrong ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Bug: Invalid face reference
I see you're using Windows. What version of Emacs are you running on it? I am using Emacs 22.1. Actually I also tested on Linux (with Emacs 22.1 too), and I saw the same thing. Just some update: I called (org-restart-font-lock) function inside my tag search result buffer, and I can see a new Invalid face reference: nil [X times] message is generated in the *Messages* buffer, with X keeps increasing. I have jit-lock-mode (Just in time font locking) enabled in my emacs config, so I guess that ticking X number is from the background font locking process. It seems something is wrong with font locking for tags. But this only happens in tag search result buffer. It does not happen in regular agenda buffer. I don't know how to proceed to pin-point this. Can any of you guys also reproduce this? Any suggestions? Thank you. Wanrong ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Active timestamp with notification in advance
If you can stick to the habit of looking into the next day (especially on the last day in you weekly agenda), that will work. But I am not reliable on that. And sometimes you may need to look ahead more than one day. I want to be lazy and dumb with the help of org. :-) Wanrong I simply enter my appointments in my diary, integrate my diary in my agenda and use the week view in the agenda. That way I always see what I'm supposed to do tomorrow. HTH Christian ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Error when switching on org-table minor mode in mail/message buffers
Hi When trying to switch on org table minor mode in mail or message buffers I get: not a keyword: (org-at-table-p), [Sort lines in region org-table-sort-lines (org-at-table-p) :keys C-c ^] The folowing fixes it for me: --- org.el 2008-02-19 09:14:57.0 +0100 +++ /tmp/org.el 2008-02-28 17:42:08.09375 +0100 @@ -11393,7 +11393,7 @@ [Move Row Down org-metadown :active (org-at-table-p) :keys M-down] [Delete Row org-shiftmetaup :active (org-at-table-p) :keys M-S-up] [Insert Row org-shiftmetadown :active (org-at-table-p) :keys M-S-down] -[Sort lines in region org-table-sort-lines (org-at-table-p) :keys C-c ^] +[Sort lines in region org-table-sort-lines :active (org-at-table-p) :keys C-c ^] -- [Insert Hline org-table-insert-hline :active (org-at-table-p) :keys C-c -]) (Rectangle Ciao Volker ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Active timestamp with notification in advance
Set up your agenda to display today forward. My weekly view always shows today and the next 6 days. (setq org-agenda-start-on-weekday nil) -Bernt Wanrong Lin [EMAIL PROTECTED] writes: If you can stick to the habit of looking into the next day (especially on the last day in you weekly agenda), that will work. But I am not reliable on that. And sometimes you may need to look ahead more than one day. I want to be lazy and dumb with the help of org. :-) Wanrong I simply enter my appointments in my diary, integrate my diary in my agenda and use the week view in the agenda. That way I always see what I'm supposed to do tomorrow. HTH Christian ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Active timestamp with notification in advance
This is good! I did not know such a setting exists. I will use this while Carsten and others think about whether it is worth to have appointment notifications. Thanks a lot! Wanrong Bernt Hansen wrote: Set up your agenda to display today forward. My weekly view always shows today and the next 6 days. (setq org-agenda-start-on-weekday nil) -Bernt Wanrong Lin [EMAIL PROTECTED] writes: If you can stick to the habit of looking into the next day (especially on the last day in you weekly agenda), that will work. But I am not reliable on that. And sometimes you may need to look ahead more than one day. I want to be lazy and dumb with the help of org. :-) Wanrong I simply enter my appointments in my diary, integrate my diary in my agenda and use the week view in the agenda. That way I always see what I'm supposed to do tomorrow. HTH Christian ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Error when switching on org-table minor mode in mail/message buffers
Fixed, thanks. - Carsten On Feb 28, 2008, at 6:06 PM, Dr. Volker Zell wrote: Hi When trying to switch on org table minor mode in mail or message buffers I get: not a keyword: (org-at-table-p), [Sort lines in region org-table- sort-lines (org-at-table-p) :keys C-c ^] The folowing fixes it for me: --- org.el 2008-02-19 09:14:57.0 +0100 +++ /tmp/org.el 2008-02-28 17:42:08.09375 +0100 @@ -11393,7 +11393,7 @@ [Move Row Down org-metadown :active (org-at-table-p) :keys M-down] [Delete Row org-shiftmetaup :active (org-at-table-p) :keys M-S-up] [Insert Row org-shiftmetadown :active (org-at-table- p) :keys M-S-down] -[Sort lines in region org-table-sort-lines (org-at-table- p) :keys C-c ^] +[Sort lines in region org-table-sort-lines :active (org- at-table-p) :keys C-c ^] -- [Insert Hline org-table-insert-hline :active (org-at-table- p) :keys C-c -]) (Rectangle Ciao Volker ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] org-bookmark.el
Phil Jackson [EMAIL PROTECTED] writes: Bastien [EMAIL PROTECTED] writes: In any case, this should be implemented in org.el directly. When `org-store-link' checks whether we are in dired-mode or in a buffer visiting a file, then it would also check whether 'org-bookmark is provided (with (featurep 'org-bookmark)...) and act accordingly if it is. I don't think it needs to go into org.el does it? When org-bookmark gets it's turn upon `org-store-link' it should check a variable called, for example, `org-bookmark-check-bookmarks-first' and then if that's non-nil check major-mode and act accordingly. This will keep `org-store-link' nice and clean. Of course, you're right. But I doubt whether `org-bookmark-check-bookmarks-first' would be useful here. People using `org-bookmark.el' are likely to use it in dired-mode and in buffer visiting files as well. Actually, I would use it just for that (not really for creating links from the bookmarks list.) `org-bookmark-store-link' could just check if we are in a dired buffer, in a buffer visiting a file, or in a bookmark list, and act accordingly. When in dired or visiting a file, it would try to fetch a bookmark. If there are more than one, then it will prompt the user for the bookmark to use. Tokuya, what do you think? Do you want to implement this? -- Bastien ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Bug: return key does not show the subtree the first time on a newly opened org file
Yes, this is really an accidental feature by a sequence of events: org-return-follow-link will add org-return to the mouse-map org-mouse.el will activate the stars in a headline I can reproduce the bug, but I have no idea what is causing this, it must be something in the internal setup of Emacs keymaps in a new buffer, I have no idea how to fix this or work around it. Why in the world would you use RET for cycling instead of TAB? - Carsten Because I discovered it and thought that was an official feature and got used to it from day 1. :-) I will try to use Tab from now on. Wanrong ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] org-bookmark.el
Bastien [EMAIL PROTECTED] writes: I don't think it needs to go into org.el does it? When org-bookmark gets it's turn upon `org-store-link' it should check a variable called, for example, `org-bookmark-check-bookmarks-first' and then if that's non-nil check major-mode and act accordingly. This will keep `org-store-link' nice and clean. Of course, you're right. But I doubt whether `org-bookmark-check-bookmarks-first' would be useful here. People using `org-bookmark.el' are likely to use it in dired-mode and in buffer visiting files as well. Actually, I would use it just for that (not really for creating links from the bookmarks list.) I don't think that just through the act of loading a module the unrelated default behaviour should change. I would put a vote in for this behaviour to be off by default (but then I don't use bookmarks). Cheers, Phil -- Phil Jackson http://www.shellarchive.co.uk ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] title for single page export to html
Hi, Is that possible to add a line in the .org file indicating the title of the exported HTML, in stead of the file name? For example: #title This is the title of the HTML Thanks! Xin ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] title for single page export to html
Xin Shi [EMAIL PROTECTED] writes: Is that possible to add a line in the .org file indicating the title of the exported HTML, in stead of the file name? For example: #title This is the title of the HTML #+TITLE: This is the title of the HTML `C-c C-c' on this line to make org-mode aware of it. -- Bastien ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Bug: return key does not show the subtree the first time on a newly opened org file
It *is* puzzling. I have a fix for this. I'm testing it a few days more and will commit it if it works okay. Look forward to it. Although I am trying to get into the habit of using TAB, it won't hurt to have the old way working too. Thanks a lot. Wanrong ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] One table, multiple radio targets?
Anyone have a clever way to generate multiple outputs from one table? It's pretty clear that orgtbl-send-table doesn't handle multiple ORGTBL lines, and I'm not clever enough to hack in a loop over multiple clauses on one ORGTBL line. The context is a probably too clever mechanism to generate both code and documentation at once. I'm using noweb to document a SQL schema, and a few tables are pre-loaded with data. I'd like to send one orgtbl-mode table to LaTeX and SQL insert statements. Jason ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
