From: Juanma Barranquero <lekktu@gmail.com>
To: Nathaniel Flath <flat0103@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Ido requests confirmation
Date: Thu, 8 Oct 2009 09:42:47 +0200 [thread overview]
Message-ID: <f7ccd24b0910080042u43c95071od4a488d97f89571e@mail.gmail.com> (raw)
In-Reply-To: <5e3a506e0910062043o6639ae3aw884544e0168629b5@mail.gmail.com>
On Wed, Oct 7, 2009 at 05:43, Nathaniel Flath <flat0103@gmail.com> wrote:
> I upgraded from 23.0.6 to 23.1.5 recently, and ido now asks for confirmation
> when I switch to a non-existent buffer or attempt to open a non-existent
> file, despite ido-create-new-buffer being set to 'always. Is there any way
> to auto-create the buffers?
Likely is not Ido, but switch-to-buffer or find-file. See variable
`confirm-nonexistent-file-or-buffer'.
Juanma
next prev parent reply other threads:[~2009-10-08 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 3:43 Ido requests confirmation Nathaniel Flath
2009-10-08 7:42 ` Juanma Barranquero [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-07 17:54 nflath
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=f7ccd24b0910080042u43c95071od4a488d97f89571e@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=flat0103@gmail.com \
--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).