From: Joost Kremers <joostkremers@yahoo.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Alerts for saves to non-existent files
Date: 29 Aug 2012 17:04:41 GMT [thread overview]
Message-ID: <slrnk3sit9.dkp.joostkremers@j.kremers4.news.arnhem.chello.nl> (raw)
In-Reply-To: k1l1fo$p8k$1@reader1.panix.com
kj wrote:
> Is there a way to tell Emacs that, from now on, it should save all
> changes to this buffer to the new path (and preferably without
> asking for any additional confirmation)?
you can use C-x C-w to save a buffer to another file. that doesn't delete
the original file, but using C-x C-w and then deleting the original file
should cause less vexation than your current scenario. ;-)
--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)
next prev parent reply other threads:[~2012-08-29 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 12:21 Alerts for saves to non-existent files kj
2012-08-29 14:54 ` Peter Dyballa
2012-08-29 17:04 ` Joost Kremers [this message]
2012-08-31 12:35 ` kj
2012-08-31 14:19 ` Raffaele Ricciardi
2012-09-04 13:59 ` Joost Kremers
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=slrnk3sit9.dkp.joostkremers@j.kremers4.news.arnhem.chello.nl \
--to=joostkremers@yahoo.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).