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: Sun, 6 Dec 2020 04:35:10 +0100 [thread overview]
Message-ID: <trinity-6d15c28b-3f0d-46d8-ae60-165d6043d68c-1607225710449@3c-app-mailcom-bs06> (raw)
In-Reply-To: <87ft4jslxp.fsf@web.de>
> Sent: Sunday, December 06, 2020 at 3:33 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:
>
> > So, only comment-auto-fill-only-comments need to be set to buffer
> > local. Right?
>
> I think so, yes. BTW, in my Emacs, the variable corresponding to
> auto-fill-mode is auto-fill-function; `auto-fill-mode' is unbound.
Unbound? What is that?
> > Returning back to taking the property "state". If it is global. that
> > would only mean that in a different buffer the cycle would begin from
> > a a different starting point. But then, the auto-fill settings would
> > still be buffer local.
>
> Yes, that, and cycling in the first buffer may bring you from 2 to 1 or
> from 2 to 2 afterwards. Might be confusing, once you got used to it.
Can see what you mean. That although what happens in the actual buffer
is local to the buffer, how the cycle performs, would depend on what
was done on other buffers, creating confusion. Actually, it is not very
confusing as I write what option was selected in the mini buffer.
I have now started to understand buffer local quite well. It has been
occurring to me that most things really got to be buffer local.
Continuing with the keybinding cycle (pressing repeatedly a key-sequence
to switch configuration, e.g. auto-fill in my case).
I am really getting into some difficulty figuring out what commands
would one want to have a Keybinding Cycle that would not be buffer-local.
For what things should a key-cycle be global?
> > Does the order of the two commands matter?
> >
> > (set (make-local-variable 'comment-auto-fill-only-comments) t)
> > (auto-fill-mode 1)
> >
> > versus
> >
> > (auto-fill-mode 1)
> > (set (make-local-variable 'comment-auto-fill-only-comments) t)
>
> No, should not matter. These things are called expressions, btw.
>
> [And you might prefer `setq-local'.]
>
>
> Regards,
>
> Michael.
>
>
>
next prev parent reply other threads:[~2020-12-06 3:35 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 [this message]
2020-12-06 5:23 ` Robert Thorpe
2020-12-06 23:01 ` Michael Heerdegen
2020-12-06 23:43 ` Christopher Dimech
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-6d15c28b-3f0d-46d8-ae60-165d6043d68c-1607225710449@3c-app-mailcom-bs06 \
--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).