From: Tamas Papp <tkpapp@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: how to capture output too long to fit
Date: Wed, 15 Aug 2007 21:21:04 +0200 [thread overview]
Message-ID: <87fy2kfvtr.fsf@pu100877.student.princeton.edu> (raw)
When I do M-: (frame-parameters) RET, the value appears in the
minibuffer, but it is too long to fit there and ends with ... How
could I see the whole thing?
Thanks,
Tamas
next reply other threads:[~2007-08-15 19:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 19:21 Tamas Papp [this message]
2007-08-15 19:28 ` how to capture output too long to fit weber
2007-08-16 1:16 ` Barry Margolin
2007-08-16 6:55 ` Dmitri Minaev
-- strict thread matches above, loose matches on Subject: below --
2007-08-16 9:33 martin rudalics
[not found] <mailman.4853.1187256810.32220.help-gnu-emacs@gnu.org>
2007-08-16 9:57 ` Tamas Papp
2007-08-16 13:25 ` weber
2007-08-16 13:27 ` weber
2007-08-16 14:51 ` Drew Adams
2007-08-16 13:31 martin rudalics
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=87fy2kfvtr.fsf@pu100877.student.princeton.edu \
--to=tkpapp@gmail.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).