From: Lennart Borgman <lennart.borgman@gmail.com>
To: Mosur Mohan <mognush@gmail.com>, 4592@emacsbugs.donarmstrong.com
Subject: bug#4592: Bug in built-in function substitute-in-file-name
Date: Sat, 3 Oct 2009 21:18:50 +0200 [thread overview]
Message-ID: <e01d8a50910031218p544f9b22jf705f7aeaba31613@mail.gmail.com> (raw)
In-Reply-To: <7f5ab920910030013n1b4b88f8he564ae610cb90236@mail.gmail.com>
Why do you do that instead of upgrade to Emacs 23?
On Sat, Oct 3, 2009 at 9:13 AM, Mosur Mohan <mognush@gmail.com> wrote:
> I was afraid you were gonna say that... :-) Unfortunately I haven't
> been able to pin down the exact recipe; in the "good" session, I'm
> still chugging along and the error hasn't occurred yet.
>
> Thanks for your help anyway! If I figure out the recipe to trigger
> this behavior, I will get in touch with you again.
> --
> Mohan
>
> On Fri, Oct 2, 2009 at 5:15 PM, Glenn Morris <rgm@gnu.org> wrote:
>> Mosur Mohan wrote:
>>
>>> I am running Emacs version 21.3 on a Linux x86_64 machine.
>> [...]
>>> After running for a while, I notice that filename completion starts
>>> giving errors. At this point, I re-try the above experiment:
>>> (substitute-in-file-name "/~/")
>>> But now, I get:
>>> "/~/"
>>
>> Unfortunately, this seems a rather obscure problem, and Emacs 21 is
>> quite old, so you are unlikely to get much help unless you can give a
>> simple recipe showing how to get into this state (starting from emacs
>> -q --no-site-file). In any case, I would recommend upgrading to Emacs 23.
>>
>
>
>
>
next prev parent reply other threads:[~2009-10-03 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 0:37 bug#4592: Bug in built-in function substitute-in-file-name Mosur Mohan
2009-09-30 9:07 ` Andreas Schwab
2009-09-30 15:02 ` Mosur Mohan
2009-10-03 0:15 ` Glenn Morris
2009-10-03 7:13 ` Mosur Mohan
2009-10-03 19:18 ` Lennart Borgman [this message]
2009-10-06 22:58 ` Mosur Mohan
2011-03-10 7:00 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e01d8a50910031218p544f9b22jf705f7aeaba31613@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=4592@emacsbugs.donarmstrong.com \
--cc=mognush@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.