From: PJ Weisberg <pjweisberg@gmail.com>
To: "wbparsons@cshore.com" <wbparsons@cshore.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: how to handle buffer modifications that are not to be saved
Date: Sat, 31 Mar 2012 13:14:46 -0700 [thread overview]
Message-ID: <CAJsNXTnFsi7SRRiuXi1tfYCKUFCnM6X58GYhcUVvxt=QLuU38g@mail.gmail.com> (raw)
In-Reply-To: <9tp2tuFo64U1@mid.individual.net>
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
On Saturday, March 31, 2012, Will Parsons <oudeis@nodomain.invalid> wrote:
> buffer. What would be the recommended way of simply making the
> converted .docx buffer temporary, so I don't have to worry about
> saving it accidentally, or answering any questions about saving it
> when exiting?
Off the top of my head, try setting buffer-file-name to nil.
--
-PJ
Gehm's Corollary to Clark's Law: Any technology distinguishable from
magic is insufficiently advanced.
[-- Attachment #2: Type: text/html, Size: 547 bytes --]
next prev parent reply other threads:[~2012-03-31 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 19:06 how to handle buffer modifications that are not to be saved Will Parsons
2012-03-31 20:14 ` PJ Weisberg [this message]
[not found] ` <mailman.231.1333224894.20052.help-gnu-emacs@gnu.org>
2012-04-01 18:27 ` Will Parsons
2012-04-03 5:13 ` Kevin Rodgers
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='CAJsNXTnFsi7SRRiuXi1tfYCKUFCnM6X58GYhcUVvxt=QLuU38g@mail.gmail.com' \
--to=pjweisberg@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=wbparsons@cshore.com \
/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).