From: davidk@lysator.liu.se (David K}gedal)
Subject: Re: Long subjects
Date: 30 Nov 1995 12:29:07 +0100 [thread overview]
Message-ID: <jp3fb6fiik.fsf@tina.lysator.liu.se> (raw)
In-Reply-To: steve@miranova.com's message of 29 Nov 1995 22:39:21 -0800
steve@miranova.com (Steven L. Baur) writes:
>How do you all on Emacs see the right side of long subjects without a
>horizontal scrollbar?
>
>(Hoping I've found a true superiority in XEmacs Gnus)
In the summary we don't want to see it, and in the article buffer the
line wraps so all of it is visible.
And you can scroll the summary buffer horizontaly if you really want
to, but maybe you'd rather toggle truncation instead.
--
David Kågedal Lysator Academic Computer Society davidk@lysator.liu.se
http://www.lysator.liu.se/~davidk/ +46-13 17 65 89
next prev parent reply other threads:[~1995-11-30 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-30 6:39 Steven L. Baur
1995-11-30 11:29 ` David K}gedal [this message]
1995-11-30 11:33 ` Per Abrahamsen
1995-11-30 14:05 ` Jack Vinson
1995-11-30 17:49 ` Luis Fernandes
1995-11-30 15:17 Re2: " Jari Aalto
1995-11-30 20:01 ` Steven L. Baur
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=jp3fb6fiik.fsf@tina.lysator.liu.se \
--to=davidk@lysator.liu.se \
/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).