[Orgmode] Re: POLL: should we export text before the first headline
Carsten Dominik <[EMAIL PROTECTED]> writes: > Hi everyone, > > I would like to collect opinions on this issue: > > Currently, exporting only starts at the first headline, > ignoring anything before it. There have been request to change > this, I'd like to know if this would break someone's habits. > > So do you use the space before the first headline to put notes/text > that should not be exported? > > Thanks > > - Carsten I do use the space before the 1st headline for internal links, notes and alike which I definitely don't want to be exported. Thanks Thomas ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: POLL: should we export text before the first headline
On 2007-03-18, Thomas Baumann said: > Carsten Dominik <[EMAIL PROTECTED]> writes: > >> Hi everyone, >> >> I would like to collect opinions on this issue: >> >> Currently, exporting only starts at the first headline, >> ignoring anything before it. There have been request to change >> this, I'd like to know if this would break someone's habits. >> >> So do you use the space before the first headline to put notes/text >> that should not be exported? >> >> Thanks >> >> - Carsten > > I do use the space before the 1st headline for internal links, notes > and alike which I definitely don't want to be exported. I also don't want to export text before the first headline. -- Leo (GPG Key: 9283AA3F) ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] #+CATEGORY line being archived
Hello Carsten and list, My org file structure is like the follow: , | * Head1 | * Done Task | | #+CATEGORY: CR | #+ARCHIVE: %s_archive::* CR | | * CR | * anything ` I found that if I do 'C-c C-x C-s' on headline "Done Task", all text up to the next headline "CR" is archived. This clearly is not the right behavior. Am I doing something wrong or is this a bug? I am running org-mode 4.68 on GNU Emacs 22.0.95.6 (i686-pc-linux-gnu, GTK+ Version 2.10.8) of 2007-03-18. Regards, -- Leo (GPG Key: 9283AA3F) ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] POLL: should we export text before the first headline
Oops, sorry, Carsten. I pressed `R' instead of `F' in _gnus_. Now, send it to the list. Carsten Dominik <[EMAIL PROTECTED]> writes: > Hi everyone, > > I would like to collect opinions on this issue: > > Currently, exporting only starts at the first headline, > ignoring anything before it. There have been request to change > this, I'd like to know if this would break someone's habits. > > So do you use the space before the first headline to put notes/text > that should not be exported? It is definitely very handy if you can put some links, internal or external, before the first headline, so that you can access some places much easier. In that case, some people may not want to export that few lines. However, I would vote for adding a new custom variable to control that behavior. It is all about choices. Nevertheless, don't export the line with `-*- mode: org -*-' or any in-buffer options. Xiao-Yong -- c/*__o/* <\ * (__ */\ < ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: POLL: should we export text before the first headline
Carsten Dominik <[EMAIL PROTECTED]> writes: So do you use the space before the first headline to put notes/text that should not be exported? I start every org and outline file with -*- org -*- or -*- outline -*- (ispell-buffer) and then keystrokes that I have a tough time remembering or am just learning and want them at my fingertips. ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] #+CATEGORY line being archived
Leo <[EMAIL PROTECTED]> writes: > I found that if I do 'C-c C-x C-s' on headline "Done Task", all text > up to the next headline "CR" is archived. This clearly is not the > right behavior. Am I doing something wrong or is this a bug? I had this problem before and I'm now using #+ARCHIVE like this: , | * Head1 | * Done Task | | * CR | #+CATEGORY: CR | #+ARCHIVE: %s_archive::* CR | * anything ` Regards, -- Bastien ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: #+CATEGORY line being archived
On 2007-03-18, Bastien said: > Leo <[EMAIL PROTECTED]> writes: > >> I found that if I do 'C-c C-x C-s' on headline "Done Task", all text >> up to the next headline "CR" is archived. This clearly is not the >> right behavior. Am I doing something wrong or is this a bug? > > I had this problem before and I'm now using #+ARCHIVE like this: > > , > | * Head1 > | * Done Task > | > | * CR > | #+CATEGORY: CR > | #+ARCHIVE: %s_archive::* CR > | * anything > ` > > Regards, But the top level (e.g. * CR) will still be archived to the wrong place, isn't it? -- Leo (GPG Key: 9283AA3F) ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] #+CATEGORY line being archived
On Mar 18, 2007, at 17:09, Bastien wrote: Leo <[EMAIL PROTECTED]> writes: I found that if I do 'C-c C-x C-s' on headline "Done Task", all text up to the next headline "CR" is archived. This clearly is not the right behavior. Am I doing something wrong or is this a bug? I had this problem before and I'm now using #+ARCHIVE like this: , | * Head1 | * Done Task | | * CR | #+CATEGORY: CR | #+ARCHIVE: %s_archive::* CR | * anything ` This is a fundamental problem, for which there are only work-arounds, no solutions. Because of the structure of an outline, there is no such thing as a "location between sections". So just like Bastien describes, I also use work-arounds for this. Two come to mind. 1. Bastiens proposal, i.e. placing the parameter lines after the top-level heading. This works as long as the top-level heading itself is never pointed to by an agenda entry (the category would be wrong) and as long as you neve atempt to archive the top-level heading itself. 2. If (1) is not good enough, the only way I see is to insert a "parameter section", like this: , | * Head1 | * Done Task | | * Params for the next file section | #+CATEGORY: CR | #+ARCHIVE: %s_archive::* CR | | * CR | * anything ` You could add an ARCHIVE tag to the parameter section, to keep it from opening. - Carsten ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] POLL: should we export text before the first headline
On Mar 18, 2007, at 16:34, Xiao-Yong Jin wrote: Carsten Dominik <[EMAIL PROTECTED]> writes: Hi everyone, I would like to collect opinions on this issue: Currently, exporting only starts at the first headline, ignoring anything before it. There have been request to change this, I'd like to know if this would break someone's habits. So do you use the space before the first headline to put notes/text that should not be exported? It is definitely very handy if you can put some links, internal or external, before the first headline, so that you can access some places much easier. In that case, some people may not want to export that few lines. However, I would vote for adding a new custom variable to control that behavior. It is all about choices. Nevertheless, don't export the line with `-*- mode: org -*-' or any in-buffer options. Well, even if we export the stuff before the first headline, there would be ways to place stuff there that would not be exported, for example by using a COMMENT section like * COMMENT here is where I put my internal links etc Here is my stuff By the way, the first line with the -*- mode: org -*- should always be a comment - this is a bug I will fix. Anyway, I also like my space before the first headline for internal links and other ramblings, so the default will remain to not exporting it. There will come an options for those who need to get this part exported as well. Thanks to everyone for input. - Carsten ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] org-mode & multiple TODO sequences within a file.
Hi Rick, On Mar 15, 2007, at 17:45, Rick Moynihan wrote: Hi, I've been using org-mode happily for nearly 6 months and think it's a fantastic tool!! I've always quite liked Emacs, but org-mode has led to me really seeing Emacs's potential. I was however wondering if there was anyway for org-mode to support multiple TODO sequences within a single file. I tried specifying sections of the file as operating under particular sequences, but this doesn't seem to work (in 4.52) e.g.: #+SEQ_TODO: REPORT BUG KNOWNCAUSE RESOLVED * BUG there is a bug in foo... * RESOLVED fixed bug. #+SEQ_TODO: TODO DONE No, this does not work. Could be done, of course, but adds complexity, and I am sure once it is there, people will want to switch TODO keywords constantly, filling the entire file with new #+TODO statements. Does not feel right. How about the following alternative: Just make a long sequence containing all the subsequences, like #+SEQ_TODO: REPORT BUG KNOWNCAUSE RESOLVED TODO WAITING VERIFY DONE You can then use command like `M-5 C-c C-t' (or `5 t' in the agenda) to jump to TODO in this sequence. Basically, you need to remember where in your list the different sequences start, put items onto the right starting point, and then work through your states. Hmmm, looking at this it might actually be useful to allow additional DONE states in the middle of the sequence, but this will at least currently lead to problems, both when cycling from DONE to nothing to TODO, and also in the highlighting of TODO keywords in the agenda. I'll check if I can fix these small issues. - Carsten -- Carsten Dominik Sterrenkundig Instituut "Anton Pannekoek" Universiteit van Amsterdam Kruislaan 403 NL-1098SJ Amsterdam phone: +31 20 525 7477 ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: #+CATEGORY line being archived
On 2007-03-18, Carsten Dominik said: > On Mar 18, 2007, at 17:09, Bastien wrote: > >> Leo <[EMAIL PROTECTED]> writes: >> >>> I found that if I do 'C-c C-x C-s' on headline "Done Task", all text >>> up to the next headline "CR" is archived. This clearly is not the >>> right behavior. Am I doing something wrong or is this a bug? >> >> I had this problem before and I'm now using #+ARCHIVE like this: >> >> , >> | * Head1 >> | * Done Task >> | >> | * CR >> | #+CATEGORY: CR >> | #+ARCHIVE: %s_archive::* CR >> | * anything >> ` >> > > This is a fundamental problem, for which there are only work-arounds, > no solutions. Because of the structure of an outline, there is no such > thing as a "location between sections". So just like Bastien describes, > I also use work-arounds for this. Two come to mind. > > 1. Bastiens proposal, i.e. placing the parameter lines after the > top-level > heading. This works as long as the top-level heading itself is never > pointed to by an agenda entry (the category would be wrong) and as > long as > you neve atempt to archive the top-level heading itself. > > 2. If (1) is not good enough, the only way I see is to insert a >"parameter section", like this: > > > , > | * Head1 > | * Done Task > | > | * Params for the next file section > | #+CATEGORY: CR > | #+ARCHIVE: %s_archive::* CR > | > | * CR > | * anything > ` > > You could add an ARCHIVE tag to the parameter section, to keep it from > opening. > > - Carsten Thanks, Carsten. Bastien's seems simpler. -- Leo (GPG Key: 9283AA3F) ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Right click on link bug
On Mar 16, 2007, at 18:38, Leo wrote: Dear all, Put the following line in a buffer: [[http://www.google.com][Musick is wrong]] then enable org-mode and flyspell-mode. Now right click on the word "Musick" and you can see the behavior of mouse1 has be changed to yank instead of opening the link. That will teach you! Don't misspell your links! :-) Well, competing overlays with competing keymaps, I really would not know how to fix this on my side. I know that ispell (and therefore flyspell) has some ways to not check TeX command names, for example. But I am not sure if this is extensible so that we could use it for org-mode, making it skip links. And I am not even sure if this is what you would want, because it is actually nice to have the description part of a link spell-checked! Summary: If you use flyspell, do actually use it to correct your typos :-) Cheers. - Carsten ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Right click on link bug
On Mar 18, 2007, at 22:46, Leo wrote: For example, if I have an internal link [[* MFE][MFE]], mouse1 won't bring it to the right place. This is when it is rather inconvenient. I guess this could be a start: (defun org-flyspell-predicate () (not (org-at-regexp-p org-bracket-link-regexp))) (add-hook 'org-mode-hook (lambda () (setq flyspell-generic-check-word-predicate 'org-flyspell-predicate))) - Carsten ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Feature in org-move-item-down
The manual (section 2.8) says "Indentation also determines the end of a list item. It ends before the next line that is indented like the bullet/number, or less." I think that a blank line has 0 indentation, therefore (by this logic) it should end a list item. Clearly a blank line cannot start a list item, so it must end a list. I think the question is whether list items can contain blank lines. This may be established practice, but it was not what I was expecting. Thanks Mike On Sun, 18 Mar 2007 08:11:08 +0100 Carsten Dominik <[EMAIL PROTECTED]> wrote: > > On Mar 17, 2007, at 4:15, Mike Newman wrote: > > > It appears org-move-item-down treats blank lines as part of the > > preceding list item (whereas I use them to separate a list from > > subsequent text). > > > > So given > > > > - a test > > - b test > > - c test > > > > test > > > > with point on line b, M-x org-move-item-down gives > > - a test > > - c test > > > > - b test > > test > > > The problem with is this is following. Suppose I made the item end > before the > empty line, as you suggest. Then consider the following case: > > - a test > > - b test > > - c test > > If I now move "b" up, I get > > - b test > - a test > > > - c test > > I don't think there is a good solution to this problem - if you > know one, I would be interested. > > - Carsten > -- Mike ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] #+CATEGORY line being archived
Carsten Dominik <[EMAIL PROTECTED]> writes: > 1. Bastiens proposal, i.e. placing the parameter lines after the > top-level heading. This works as long as the top-level heading itself > is never pointed to by an agenda entry (the category would be wrong) > and as long as you neve atempt to archive the top-level heading > itself. This is exactly what i do. I have several projects and i list them within a single file : , | #+CATEGORY: main_categeory | #+ARCHIVE: main_archive::* | | * Project 1 | #+CATEGORY: project_1 | #+ARCHIVE: project1_archive::* | | ** task 1 | | * Project 2 | #+CATEGORY: project_2 | #+ARCHIVE: project2_archive::* | | * Project 1 | #+CATEGORY: project_2 | #+ARCHIVE: project2_archive::* ` Archiving "** task 1" puts it in `project1_archive', as expected. Archiving "* Project 1" will put it in `main_archive'. For me "* Project 1" is not part of the project1-related tasks -- not more than the filename of my main org file is part of this file. So the headline "* Project 1" has not to be archived in `project1_archive', but in `main_archive'. Hence the normal behavior suits my use very well. Regards, -- Bastien ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: POLL: should we export text before the first headline
Carsten Dominik <[EMAIL PROTECTED]> writes: By the way, the first line with the -*- mode: org -*- should always be a comment - this is a bug I will fix. Can I ask a dumb question... is there a difference between the first lines, -*- mode: org -*- and -*- org -*-? ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Fwd: [Orgmode] Feature in org-move-item-down
Once again, it hit reply instead of reply-all. Edd -- Forwarded message -- From: Eddward DeVilla <[EMAIL PROTECTED]> Date: Mar 18, 2007 10:04 PM Subject: Re: [Orgmode] Feature in org-move-item-down To: Mike Newman <[EMAIL PROTECTED]> I sometimes have blank lines in list items. I have lists do visibility cycling like headings and use them as light weight headings. One thing I've found is that empty lines seem to be after an item and not a part. Blank lines, with whitespace characters in them seem to be a part of the item. I use it and tend to like it. I need to turn on a setting to make such blank but not empty lines a little easier to spot. If the behavior would change, I'd probably need to change how I do thing and maybe use heading more. Edd On 3/18/07, Mike Newman <[EMAIL PROTECTED]> wrote: The manual (section 2.8) says "Indentation also determines the end of a list item. It ends before the next line that is indented like the bullet/number, or less." I think that a blank line has 0 indentation, therefore (by this logic) it should end a list item. Clearly a blank line cannot start a list item, so it must end a list. I think the question is whether list items can contain blank lines. This may be established practice, but it was not what I was expecting. Thanks Mike On Sun, 18 Mar 2007 08:11:08 +0100 Carsten Dominik <[EMAIL PROTECTED]> wrote: > > On Mar 17, 2007, at 4:15, Mike Newman wrote: > > > It appears org-move-item-down treats blank lines as part of the > > preceding list item (whereas I use them to separate a list from > > subsequent text). > > > > So given > > > > - a test > > - b test > > - c test > > > > test > > > > with point on line b, M-x org-move-item-down gives > > - a test > > - c test > > > > - b test > > test > > > The problem with is this is following. Suppose I made the item end > before the > empty line, as you suggest. Then consider the following case: > > - a test > > - b test > > - c test > > If I now move "b" up, I get > > - b test > - a test > > > - c test > > I don't think there is a good solution to this problem - if you > know one, I would be interested. > > - Carsten > -- Mike ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: POLL: should we export text before the first headline
On Mar 19, 2007, at 1:09, Sean Sieger wrote: Carsten Dominik <[EMAIL PROTECTED]> writes: By the way, the first line with the -*- mode: org -*- should always be a comment - this is a bug I will fix. Can I ask a dumb question... is there a difference between the first lines, -*- mode: org -*- and -*- org -*-? The effect is the same, setting the major mode of the file. The first is a more general way, because also other local variables can be set in this way, like -*- mode: org; fill-column:60 -*- - Carsten ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Feature in org-move-item-down
On Mar 19, 2007, at 4:26, Mike Newman wrote: The manual (section 2.8) says "Indentation also determines the end of a list item. It ends before the next line that is indented like the bullet/number, or less." Yes, you are right, I am treating an empty line as a line with a large indentation. Suppose I did what you suggest, treating it as a line with no indentation: - one - two - two a - two b - two c - three Now "- three" will not be treated as third item in the list started by "- one", but it will be starting a new list... Whatever I do, this is very fragile, and I would have to require to never put any empty line between items. What we have now is at least stable. I agree that making empty lines always close all levels of items would be another stable implementation. Hmm. - Carsten I think that a blank line has 0 indentation, therefore (by this logic) it should end a list item. Clearly a blank line cannot start a list item, so it must end a list. I think the question is whether list items can contain blank lines. This may be established practice, but it was not what I was expecting. Thanks Mike On Sun, 18 Mar 2007 08:11:08 +0100 Carsten Dominik <[EMAIL PROTECTED]> wrote: On Mar 17, 2007, at 4:15, Mike Newman wrote: It appears org-move-item-down treats blank lines as part of the preceding list item (whereas I use them to separate a list from subsequent text). So given - a test - b test - c test test with point on line b, M-x org-move-item-down gives - a test - c test - b test test The problem with is this is following. Suppose I made the item end before the empty line, as you suggest. Then consider the following case: - a test - b test - c test If I now move "b" up, I get - b test - a test - c test I don't think there is a good solution to this problem - if you know one, I would be interested. - Carsten -- Mike -- Carsten Dominik Sterrenkundig Instituut "Anton Pannekoek" Universiteit van Amsterdam Kruislaan 403 NL-1098SJ Amsterdam phone: +31 20 525 7477 ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Feature in org-move-item-down
Carsten Dominik <[EMAIL PROTECTED]> writes: > I agree that making empty lines always close all levels of items would > be another stable implementation. Hmm. I think the current implementation is okay, leaving the possibility for list items to contain empty lines. Great for long list items, and more publishing-oriented org files. Regards, -- Bastien ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
