unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Cycle Auto-Fill
Date: Mon, 7 Dec 2020 00:43:34 +0100	[thread overview]
Message-ID: <trinity-05bfdf95-ac76-4a8e-b1e8-29d26e2d9408-1607298214859@3c-app-mailcom-bs11> (raw)
In-Reply-To: <87y2iabkuo.fsf@web.de>

> Sent: Monday, December 07, 2020 at 12:01 AM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Cycle Auto-Fill
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > Unbound? What is that?
>
> (info "(elisp) Void Variables")

What is the relevance of having the value cell of symbol auto-fill-mode
void? Why do you recommend auto-fill-function instead?

Looks like auto-fill-function is a variable called in auto-fill-mode.
You seem to imply that setting the variable auto-fill-function breaks
the line without needing to utilise auto-fill-mode.

> > For what things should a key-cycle be global?
>
> Things that make emacs look different, for example: menu-bar-mode and
> such, display-time-mode and things that change the mode-line.  Changing
> frame backgrounds because it got dark, or changing how Emacs looks like
> because you want to use it for a presentation?

Very clear, thank you.  This got us back to what Daniela was doing with
mode-line.  Quite many things can be linked together.  She has not managed
to revert mode-line to its original value, last time we talked about that.

> Things that toggle features for a frame or window instead of a buffer
> (e.g. scroll-bars).  Toggling debugger flags.  Things where you want a
> toggle but can't remember all the values in all of the buffers,
> e.g. `case-fold-search' or such things.
>
>
> Regards,
>
> Michael.
>
>
>



  reply	other threads:[~2020-12-06 23:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05 13:25 Cycle Auto-Fill Christopher Dimech
2020-12-05 13:59 ` Pankaj Jangid
2020-12-05 14:16   ` Christopher Dimech
2020-12-05 16:57     ` Pankaj Jangid
2020-12-05 14:39 ` Ergus
2020-12-05 22:00 ` Michael Heerdegen
2020-12-05 22:06   ` Drew Adams
2020-12-05 22:38   ` Christopher Dimech
2020-12-05 23:53     ` Michael Heerdegen
     [not found]       ` <trinity-3598b15c-19a1-41d1-92ed-96e7f10f1fd9-1607213433613@3c-app-mailcom-bs06>
     [not found]         ` <87v9dfhj2e.fsf@web.de>
2020-12-06  0:49           ` Christopher Dimech
2020-12-06  2:33             ` Michael Heerdegen
2020-12-06  3:35               ` Christopher Dimech
2020-12-06  5:23                 ` Robert Thorpe
2020-12-06 23:01                 ` Michael Heerdegen
2020-12-06 23:43                   ` Christopher Dimech [this message]
2020-12-07  0:36                     ` Michael Heerdegen

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=trinity-05bfdf95-ac76-4a8e-b1e8-29d26e2d9408-1607298214859@3c-app-mailcom-bs11 \
    --to=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).