From: Ari Roponen <ari.roponen@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: emacs-devel@gnu.org
Subject: Re: File name completion problem with non-ascii file names
Date: Tue, 29 Apr 2008 13:17:20 +0300 [thread overview]
Message-ID: <m3y76x9d8v.fsf@gmail.com> (raw)
In-Reply-To: <jeabjd9608.fsf@sykes.suse.de> (Andreas Schwab's message of "Mon, 28 Apr 2008 20:41:27 +0200")
Andreas Schwab <schwab@suse.de> writes:
> Ari Roponen <ari.roponen@gmail.com> writes:
>
>> According to documentation, file-name-completion should return t,
>> because there is only one possible completion:
>
> Fixed.
Yes, this works now. Thank you.
>
> Andreas.
--
Ari Roponen
prev parent reply other threads:[~2008-04-29 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 10:36 File name completion problem with non-ascii file names Ari Roponen
2008-04-27 16:16 ` Drew Adams
2008-04-27 18:07 ` Andreas Schwab
2008-04-28 12:16 ` Ari Roponen
2008-04-28 18:41 ` Andreas Schwab
2008-04-29 10:17 ` Ari Roponen [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3y76x9d8v.fsf@gmail.com \
--to=ari.roponen@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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.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).