unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: "51041@debbugs.gnu.org" <51041@debbugs.gnu.org>,
	Tyler Grinn <tylergrinn@gmail.com>
Subject: bug#51041: [External] : Re: bug#51041: 28.0.60; toggle-truncate-lines should not print message
Date: Wed, 6 Oct 2021 17:09:16 -0400	[thread overview]
Message-ID: <CADwFkmniXp=kDwW71R5NNruBP5_5tARN-f3cUsAhc2nTait3Ww@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR10MB5488DC1E37AAEA4A8787BB12F3B09@SJ0PR10MB5488.namprd10.prod.outlook.com>

Drew Adams <drew.adams@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?

Drew, it is draining to discuss this way.  I have alredy agreed that
an argument is better than 'called-interactively-p'.  No one is
arguing for that.  Please drop it.  Read the thread.

The argument is that from Lisp you can just set the `truncate-lines'
variable instead of calling `toggle-truncate-lines'.

Does that not work?  If it doesn't, please explain the use-case.





  reply	other threads:[~2021-10-06 21:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 17:39 bug#51041: 28.0.60; toggle-truncate-lines should not print message Tyler Grinn
2021-10-05 18:34 ` bug#51041: [External] : " Drew Adams
2021-10-05 20:01   ` Tyler Grinn
2021-10-05 21:39   ` Stefan Kangas
2021-10-05 23:41     ` bug#51041: [External] : " Drew Adams
2021-10-06  0:28       ` Stefan Kangas
2021-10-06  9:23         ` Lars Ingebrigtsen
2021-10-06 14:28           ` bug#51041: [External] : " Drew Adams
2021-10-06 18:11             ` Stefan Kangas
2021-10-06 20:45               ` Drew Adams
2021-10-06 21:09                 ` Stefan Kangas [this message]
2021-10-06 22:12                   ` Drew Adams
2021-10-07 12:41                     ` Tyler Grinn
2021-10-07 17:42                       ` Lars Ingebrigtsen

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='CADwFkmniXp=kDwW71R5NNruBP5_5tARN-f3cUsAhc2nTait3Ww@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=51041@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=larsi@gnus.org \
    --cc=tylergrinn@gmail.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.
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).