From: bojohan+news@dd.chalmers.se (Johan Bockgård)
Subject: Re: Or is it vertically split windows?
Date: Fri, 06 May 2005 01:35:57 +0200 [thread overview]
Message-ID: <yoijfyx1jleq.fsf@linus011.dd.chalmers.se> (raw)
In-Reply-To: BE9FF566.37C4%steve@tourcorp.com
"Steven M. Scotten" <steve@tourcorp.com> writes:
> OK, more information here: this only happens when I have the window
> split vertically. For the moment I can work around this by opening a
> second frame, but is this correct behavior or should I report this
> as a bug? I haven't seen any mention that truncate-long-lines should
> be forced on when the window is split vertically.
This is in fact so; see the variable `truncate-partial-width-windows'.
--
Johan Bockgård
next prev parent reply other threads:[~2005-05-05 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 22:38 Truncate long lines on 22.0.50.1 (powerpc-apple-darwin7.8.0) Steven M. Scotten
2005-05-05 23:08 ` Or is it vertically split windows? (Was: Truncate long lines...) Steven M. Scotten
2005-05-05 23:35 ` Johan Bockgård [this message]
2005-05-06 17:40 ` Or is it vertically split windows? Steven M. Scotten
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=yoijfyx1jleq.fsf@linus011.dd.chalmers.se \
--to=bojohan+news@dd.chalmers.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 read-only IMAP folder(s) and NNTP newsgroup(s).