Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <asjo@koldfront.dk>
To: info-gnus-english@gnu.org
Subject: How to turn off auto-fill-mode from Topic Parameters?
Date: Sat, 10 Jun 2023 14:12:42 +0200	[thread overview]
Message-ID: <87sfaza539.fsf@tullinup.koldfront.dk> (raw)

I would like to have auto-fill-mode turned off for all groups in a
specific topic in Gnus.

I tried adding this to my Topic Parameters:

  (message-fill-column nil)

after reading the documentation:

,----[ C-h v message-fill-column RET ]
| message-fill-column is a variable defined in ‘message.el’.
| 
| Its value is 72
| 
| Column beyond which automatic line-wrapping should happen.
| Local value for message buffers.  If non-nil, also turn on
| auto-fill in message buffers.
`----

I then read this in the (variable form) part of the manual on Group
Parameters:

,----[ https://www.gnus.org/manual/gnus_21.html ]
| But some variables are evaluated in the article buffer, or in the
| message buffer (of a reply or followup or otherwise newly created
| message). As a workaround, it might help to add the variable in
| question to gnus-newsgroup-variables.
`----

and added this to my .gnus:

  (add-to-list 'gnus-newsgroup-variables 'message-fill-column)

However auto-fill-mode is still on when I compose a new article in a
group in the topic.

Is The Right Way™ to add a function to a hook instead?

I just really like configuring behavior using the Topic/Group
Parameters...


  :-),

   Adam

-- 
 "LUFTVAFFEL!"                                              Adam Sjøgren
                                                       asjo@koldfront.dk



             reply	other threads:[~2023-06-10 12:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10 12:12 Adam Sjøgren [this message]
2023-06-10 13:02 ` Adam Sjøgren
2023-06-10 21:51 ` yeti
2023-06-10 22:11   ` Adam Sjøgren
2023-06-10 22:48     ` yeti
2023-06-10 23:01       ` Adam Sjøgren
2023-06-10 23:07         ` yeti

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfaza539.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --cc=info-gnus-english@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.
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 NNTP newsgroup(s).