From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Francesc Rocher <francesc.rocher@gmail.com>
Cc: Juri Linkov <juri@jurta.org>, emacs-devel@gnu.org
Subject: Re: Ignoring entries starting with space
Date: Thu, 25 Jun 2009 14:44:11 +0200 [thread overview]
Message-ID: <jwv4ou4o5a4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <ade856a30906250058p2d7d851bl39887f2f4c55b54b@mail.gmail.com> (Francesc Rocher's message of "Thu, 25 Jun 2009 09:58:57 +0200")
>> In http://thread.gmane.org/gmane.emacs.devel/91359/focus=92106
>> I suggested a piece of code for .emacs that removes potentially
>> dangerous commands from the minibuffer history.
There are many minibuffer history variables.
> Yes, that's the point. In general, any potentially dangerous command
> won't be stored into the history by simply pre-pending an space.
> Its the same as in Bash, the source of inspiration of this patch,
> especially when you are typing dangerous commands as root.
> It's better not to store them into the history.
Most minibuffer input is not commands but just "data" (e.g. file names).
So maybe, you should write something more specific that only applies to
those cases where the input takes the form of a (shell) command.
Having a blanket "throw away anything startign with a space for any
minibufffer input" sounds a bit too radical to me. After all, bash only
applies this rule to the history of commands, doesn't it?
Stefan
next prev parent reply other threads:[~2009-06-25 12:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 21:20 Ignoring entries starting with space Francesc Rocher
2009-06-21 23:00 ` Juri Linkov
2009-06-24 21:21 ` Stefan Monnier
2009-06-24 22:08 ` Juri Linkov
2009-06-25 7:58 ` Francesc Rocher
2009-06-25 12:44 ` Stefan Monnier [this message]
2009-06-25 20:45 ` Juri Linkov
2009-06-25 22:57 ` Stefan Monnier
2009-06-25 23:03 ` Lennart Borgman
2009-06-26 18:25 ` Francesc Rocher
2009-06-26 19:02 ` Drew Adams
2009-06-26 22:54 ` Juri Linkov
2009-06-26 23:42 ` Stefan Monnier
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=jwv4ou4o5a4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=francesc.rocher@gmail.com \
--cc=juri@jurta.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 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.