From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: capture buffer to a logfile?
Date: Fri, 12 Nov 2004 12:43:31 -0700 [thread overview]
Message-ID: <2vki39F2mkmlpU1@uni-berlin.de> (raw)
In-Reply-To: <10p9sfqllhlkoee@corp.supernews.com>
Mike wrote:
> I'm trying to convert some people to emacs and one of the features
> they currently use is 'screen captures' to powerpoint. These screen
> captures are 99% text. What I'm thinking of is a small bit of code to
> capture the current buffer from the first line on the screen
> (displayed) to the last line on the screen (displayed, so it's not the
> whole buffer, just what's visible), then copy that hunk to another
> buffer that is their predefined (in .emacs?) log file. First put a
> timestamp, then the copied lines, then a few blank lines, then save
> and let the user continue editing.
>
> Anyone have this bit of code?
(copy-region-as-kill (window-start) (window-end))
--
Kevin Rodgers
next prev parent reply other threads:[~2004-11-12 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 17:25 capture buffer to a logfile? Mike
2004-11-12 19:43 ` Kevin Rodgers [this message]
2004-11-14 17:16 ` Mike
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=2vki39F2mkmlpU1@uni-berlin.de \
--to=ihs_4664@yahoo.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).