From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Slightly annoying helm behavior
Date: Mon, 12 Oct 2015 12:30:18 +0200 [thread overview]
Message-ID: <87wpusqszp.fsf@web.de> (raw)
In-Reply-To: 1444603687.30245.280.camel@kendallshaw.com
Hello Kendall,
> If I have 2 files in a directory:
>
> something.cfg
> another-something.config
>
> and I attempt to rename something.cfg to something.config, helm
> suggests the existing file another-something.config as the target name.
(there is a Helm mailing list for Helm related questions btw)
Please specify "attempt to rename".
If you speak about dired: This is an issue that once had been fixed, but
it seems the fix doesn't work anymore. Please see
https://github.com/emacs-helm/helm/issues/910
I've just reopened it.
If you don't have a github account, let's continue the discussion on the
Helm list.
Thanks,
Michael.
next prev parent reply other threads:[~2015-10-12 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 22:48 Slightly annoying helm behavior Kendall Shaw
2015-10-12 10:30 ` Michael Heerdegen [this message]
2015-10-13 10:03 ` Michael Heerdegen
2015-10-14 16:50 ` Kendall Shaw
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=87wpusqszp.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@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.
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).