From: Dan Nicolaescu <dann@ics.uci.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: the menu Options / Truncate Long Lines in This Buffer not working correctly
Date: Thu, 10 Apr 2008 21:26:00 -0700 [thread overview]
Message-ID: <200804110426.m3B4Q0Lk017273@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <trr6ddwq01.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 10 Apr 2008 13:58:54 -0400")
Glenn Morris <rgm@gnu.org> writes:
> Dan Nicolaescu wrote:
>
> > > I'm not sure whether one should go further and define a new command
> > > linked to the toggle, that if needed makes
> > > truncate-partial-width-windows buffer-local and sets it to nil, before
> > > setting truncate-lines appropriately.
> >
> > IMO, that would be TRTD, it would make the menu keep its promise to
> > toggle truncating long lines in the buffer.
>
> I don't think a menu toggle can ever work right. The problem is
> controlled by two variables, and you would never be able to get back
> to the initial state, unless you made it rather complex.
Is getting back to the initial state important? Just toggling correctly
seems more important, as long as the menu entry is a toggle. From the
user point of view there are 2 visible states: lines are / are not
truncated. The fact that emacs has more complexity than that underneath
is just an unfortunate detail... (Obviously this is all IMO)
next prev parent reply other threads:[~2008-04-11 4:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18495.14102.57759.187120@fencepost.gnu.org>
2008-04-07 5:11 ` the menu Options / Truncate Long Lines in This Buffer not working correctly Dan Nicolaescu
2008-04-10 7:57 ` Glenn Morris
2008-04-10 13:58 ` Dan Nicolaescu
2008-04-10 17:58 ` Glenn Morris
2008-04-11 4:26 ` Dan Nicolaescu [this message]
2008-05-29 23:15 ` bug#123: marked as done (the menu Options / Truncate Long Lines in This Buffer not working correctly) Emacs bug Tracking System
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=200804110426.m3B4Q0Lk017273@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=bug-gnu-emacs@gnu.org \
--cc=rgm@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).