From: Bernt Hansen <bernt@norang.ca>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: BUG - Attachment directories with newlines
Date: Fri, 07 Nov 2008 08:08:03 -0500 [thread overview]
Message-ID: <87r65nadl8.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <912.1226042463@gamaville.dokosmarshall.org> (Nick Dokos's message of "Fri\, 07 Nov 2008 02\:21\:03 -0500")
Nick Dokos <nicholas.dokos@hp.com> writes:
> Carsten Dominik <dominik@science.uva.nl> wrote:
>
>> This is very strange. I cannot reproduce this. When I evaluate in
>> your example
>>
>> > | (org-id-get (point))
>> > | (org-entry-get (point) "ID")
>>
>> I get in both cases just the ID, no newline with it. Also, new
>> newlines are created for me after the attachment property. Can please
>> more people try Bernt's example?
>>
>
> I cannot reproduce it either. This is a shot in the dark but I noticed
> that org-entry-get uses a regexp using "\\S-", which is supposed to
> match whitespace. Maybe Bernt has somehow modified his syntax tables so
> that newline is not whitespace? If so, I believe that the return value
> will include the newline and org-id-get will return it unchanged as well,
> thereby explaining what Bernt sees.
I haven't knowingly modified it :) I'll try again with a minimal emacs
and see if it goes away.
More details later...
-Bernt
next prev parent reply other threads:[~2008-11-07 13:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 19:11 BUG - Attachment directories with newlines Bernt Hansen
2008-11-05 22:41 ` Carsten Dominik
2008-11-05 23:04 ` Bernt Hansen
2008-11-05 23:26 ` Bernt Hansen
2008-11-05 23:31 ` Bernt Hansen
2008-11-06 7:11 ` Carsten Dominik
2008-11-07 2:30 ` Bernt Hansen
2008-11-07 5:45 ` Carsten Dominik
2008-11-07 5:49 ` Carsten Dominik
2008-11-07 7:21 ` Nick Dokos
2008-11-07 13:08 ` Bernt Hansen [this message]
2008-11-07 14:27 ` Charles Sebold
2008-11-07 16:14 ` Bernt Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r65nadl8.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).