From: B. T. Raven <btraven@nihil.net>
To: info-gnus-english@gnu.org
Subject: Oops, sorry was Re: how to get around deprecated function
Date: 28 Apr 2015 15:57:26 -0700 [thread overview]
Message-ID: <mhp38m01fet@drn.newsguy.com> (raw)
In-Reply-To: <mhp1ol01cjq@drn.newsguy.com>
<mhp1ol01cjq@drn.newsguy.com>B. T. Raven28 Apr 2015 15:31:49 -0700
>
>Hello:
>
>I am constantly losing short pieces of text left in *scratch* and I wrote this
>interactive function:
>
>(defun save-scratchtemp ();; M-x scr
> (interactive)
> (switch-to-buffer "*scratch*")
> (mark-whole-buffer)
> (setq start (point) end (mark))
> (append-to-file start end "c:/mydocu~1/scratchtemp.txt")
>)
>
>It "works" but according to the docs mark-whole-buffer shouldn't be used this
>way.Is there an understandable (to me) right way of doing this or doing
>something else that can be invoked as easily?
>
>Thanks,
>
>Ed
>
This was supposed to go to gnu.emacs.help
Ed
prev parent reply other threads:[~2015-04-28 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 22:31 B. T. Raven
2015-04-28 22:57 ` B. T. Raven [this message]
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=mhp38m01fet@drn.newsguy.com \
--to=btraven@nihil.net \
--cc=info-gnus-english@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 NNTP newsgroup(s).