From: "Steven M. Scotten" <steve@tourcorp.com>
Subject: Or is it vertically split windows? (Was: Truncate long lines...)
Date: Thu, 05 May 2005 23:08:06 GMT [thread overview]
Message-ID: <BE9FF566.37C4%steve@tourcorp.com> (raw)
In-Reply-To: BE9FEE65.3693%steve@tourcorp.com
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.
Steve
On 5/5/05 3:38 PM, in article BE9FEE65.3693%steve@tourcorp.com, "Steven M.
Scotten" <steve@tourcorp.com> wrote:
> Hello,
>
> I'm coming across strange behavior in 22.0.50.1 (powerpc-apple-darwin7.8.0)
> on OS X 10.3.9. I'm used to "Truncate Long Lines" being disabled in my
> emacses (what is the plural of emacs, anyhow? Nevermind) but no matter how
> many times I enter M-x toggle-truncate-lines I still have the little arrows
> pointing east and west, NOT the little curly arrow I'm used to. Of course,
> no curly arrow means I also don't see the rest of my code that I'd rather
> have in front of me than somewhere else on the screen.
>
> The Messages buffer shows
>
> Truncate long lines enabled
> Truncate long lines disabled
> Truncate long lines enabled
> Truncate long lines disabled
>
> As I expect that it should, but the behavior itself is not changing.
>
> Is this a known problem? Googling yields a ton of instructions of how to
> enter M-x toggle-truncate-lines but I haven't seen any other reports of
> people having this problem.
>
> Thanks,
>
>
> Steve
>
next prev parent reply other threads:[~2005-05-05 23:08 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 ` Steven M. Scotten [this message]
2005-05-05 23:35 ` Or is it vertically split windows? Johan Bockgård
2005-05-06 17:40 ` 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=BE9FF566.37C4%steve@tourcorp.com \
--to=steve@tourcorp.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).