GNU bug report logs - #51041
28.0.60; toggle-truncate-lines should not print message

Previous Next

Full log

Message #43 received at 51041 <at> debbugs.gnu.org (full text, mbox):

From: Tyler Grinn <tylergrinn <at> gmail.com>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: "51041 <at> debbugs.gnu.org" <51041 <at> debbugs.gnu.org>,
 Lars Ingebrigtsen <larsi <at> gnus.org>, Stefan Kangas <stefan <at> marxist.se>
Subject: Re: [External] : Re: bug#51041: 28.0.60; toggle-truncate-lines
 should not print message
Date: Thu, 07 Oct 2021 08:41:03 -0400

Drew Adams <drew.adams <at> oracle.com> writes:

>> >> What is the use-case for calling it from Lisp?
>> >
>> > What is the use case for hard-coding behavior
>> > based on called-interactively?
>> 
>> Does that not work?  If it doesn't, please explain the use-case.
>
> Stefan - it's draining to discuss this way.
>
> You're free to close the bug as not-a-bug or
> whatever.  The bug report asks _how to invoke
> the command from Lisp_ without printing a msg.
> You're free to tell the OP to just not do that.
>
> (Oh, BTW: `toggle-truncate-lines' does more
> than change the variable value and print a msg,
> in particular when turning off truncation.)

Yeah, I would like some direction on this.

My understanding is that if some functionality or minor mode provides a
function to toggle it, it is a best practice to use that function rather
than re-implement it, such that if the behavior of the toggle function
changes my code doesn't have to change.

-- 

Best,

Tyler

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.