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
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 li
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 cl
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
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
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
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 befor
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 be
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 k
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 or
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 som
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 li
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
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
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
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 -*-?
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 item
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: o
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
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,
20 matches
Mail list logo
