From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Is there a way to get the last message?
Date: Sun, 28 May 2017 13:51:39 +0200 [thread overview]
Message-ID: <20170528115139.GA31293@tuxteam.de> (raw)
In-Reply-To: <87r2z92r2z.fsf@jane>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, May 28, 2017 at 12:50:12PM +0200, Marcin Borkowski wrote:
> Hi all,
>
> I know about (current-message). However, this won't work:
>
> (defun get-last-message ()
> "Try to get the last message."
> (interactive)
> (with-temp-buffer
> (insert (or (current-message) ""))
> (clipboard-kill-ring-save (point-min) (point-max))))
>
> M-x get-last-message puts the empty string into the clipboard and kill
> ring.
This might get you started:
(defun parrot ()
(interactive)
(save-excursion
(with-current-buffer (messages-buffer)
;; *Messages* seems to have a newline at end
(goto-char (- (point-max) 1))
(message "last message was '%S'"
(buffer-substring-no-properties
(line-beginning-position)
(line-end-position))))))
A couple of notes:
- it seems that messages not always end up in the *Messages* buffer
- the function (messages-buffer) is the recommended was to retrieve
the messages buffer, which (most of the time? always?) is called
*Messages*
- you might want to double check the strategy for fetching the last
line (i.e. going to point-max - 1
- I put the thing into a message with (buffer-substring ...), you
might want to dump it directly into the kill ring, of course
In the meantime, Stephen's reply seems to have addressed most of the
above points, anyway; but the recommended way to access *Messages*
might still be helpful.
Cheers
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlkqucsACgkQBcgs9XrR2kaxRQCcD6/D1RasdLi1xPNaqb3GI8TU
1CoAn3ieUdT4cRp8gXOVzyYxZXUYJJr3
=pAqo
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-05-28 11:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 10:50 Is there a way to get the last message? Marcin Borkowski
2017-05-28 11:18 ` Stephen Berman
2017-05-28 11:41 ` John Ankarström
2017-05-29 18:51 ` Emanuel Berg
2017-05-28 14:12 ` Marcin Borkowski
2017-05-28 22:11 ` Emanuel Berg
2017-05-28 11:51 ` tomas [this message]
2017-05-28 18:24 ` Emanuel Berg
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=20170528115139.GA31293@tuxteam.de \
--to=tomas@tuxteam.de \
--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).