From: Bernt Hansen <bernt@norang.ca>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG - Attachment directories with newlines
Date: Wed, 05 Nov 2008 18:26:50 -0500 [thread overview]
Message-ID: <87k5bhpxdx.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <87od0tpyfx.fsf@gollum.intra.norang.ca> (Bernt Hansen's message of "Wed\, 05 Nov 2008 18\:04\:02 -0500")
Attachments work fine today. They also worked fine on Oct 15th. But
all of the attachments I made on Oct 24 have a newline embedded as the
last character of the directory name.
I'll try to see if I can duplicate this error. Your time is better
spent on other things I think.
I'll let you know what I find out.
Regards,
Bernt
Bernt Hansen <bernt@norang.ca> writes:
> I've only every created files in my data directory with the C-c a a
> command.
>
> I'll try to get more useful information about this tonight
>
> -Bernt
>
>
> Carsten Dominik <dominik@science.uva.nl> writes:
>
>> Hi Bernt,
>>
>> it would be useful to know if the files in the directory with the \n
>> where attached there or created there by a different method than the
>> files in the directory without.
>>
>> Thanks.
>>
>> - Carsten
>>
>> On Nov 5, 2008, at 8:11 PM, Bernt Hansen wrote:
>>
>>> Hi Carsten,
>>>
>>> I've run into a problem with attachments. I tried opening an
>>> attachment
>>> for one of my tasks and it can't find it.
>>>
>>> As it turns out the attachment directory has an embedded newline in it
>>> like this:
>>>
>>> ,----
>>> | bernt@gollum:~/git/org/data/c6$ find . -type d -ls
>>> | 5581153 4 drwxr-xr-x 4 bernt bernt 4096 Oct 24
>>> 15:59 .
>>> | 5581154 4 drwxr-xr-x 2 bernt bernt 4096 Oct 24
>>> 15:59 ./47cbe-2158-46ce-bd93-8faf5ca95725
>>> | 5581156 4 drwxr-xr-x 2 bernt bernt 4096 Oct 24
>>> 17:05 ./47cbe-2158-46ce-bd93-8faf5ca95725\n
>>> | bernt@gollum:~/git/org/data/c6$
>>> `----
>>>
>>> and any files that were stored in the directory with the newline can't
>>> be found.
>>>
>>> The files are still there - just not retrievable from the org
>>> attachment
>>> system.
>>>
>>> I haven't bisected to find out where the problem was introduced.
>>>
>>> -Bernt
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
next prev parent reply other threads:[~2008-11-05 23:27 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 [this message]
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
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=87k5bhpxdx.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
/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).