Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Randy Yates <yates@ieee.org>
To: info-gnus-english@gnu.org
Subject: Re: how to disable auto-filling and other syntax-completion actions in article editing mode?
Date: Sat, 27 Oct 2007 13:33:20 -0400	[thread overview]
Message-ID: <m3tzocbgyn.fsf@ieee.org> (raw)
In-Reply-To: <v9640twr4x.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> On Fri, Oct 26 2007, Randy Yates wrote:
>
>>>>> I think the subject says it all. 
>
> No, I don't understand the syntax-completion part.  Please describe
> exactly what you mean.  As `M-x gnus-bug RET' says: "Please describe
> the bug in annoying, painstaking detail."

Well I didn't consider it a bug so I didn't think I needed to make a
bug report. 

By syntax-completion, I mean things such as automatic indentation
after a <RET> that occurs when in certain programming language major
modes.

I thought that auto-filling may be part of a general syntax-completion
methodology for the major/minor mode used by gnus for message editing.
Since, as I stated, I don't like any editor I use to insert text
"automagically" for me at any time, I would want this behavior disabled
as well as auto-fill.


> WRT auto-fill, `C-h i d m Message RET' (Message manual), `i auto-fill'
> leads directly to...

> ,----[ (info "(message)Various Message Variables") ]
> | `message-fill-column'
> |      Local value for the column beyond which automatic line-wrapping
> |      should happen for message buffers.  If non-nil (the default), also
> |      turn on auto-fill in message buffers.
> `----
>
>> I guess the development version of gnus pays attention to this while the
>> older version did not.
>
> When upgrading you should always read GNUS-NEWS aka...

Unless someone told me to read it, how would I know? 

By the way, is there a PDF of the updated manual for the gnus
development version?
-- 
%  Randy Yates                  % "Maybe one day I'll feel her cold embrace,
%% Fuquay-Varina, NC            %                    and kiss her interface, 
%%% 919-577-9882                %            til then, I'll leave her alone."
%%%% <yates@ieee.org>           %        'Yours Truly, 2095', *Time*, ELO   
http://www.digitalsignallabs.com

  reply	other threads:[~2007-10-27 17:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 19:13 Randy Yates
2007-10-25 11:40 ` Randy Yates
2007-10-26  7:49   ` Torben Knudsen
2007-10-26 19:07     ` Randy Yates
2007-10-26 20:35       ` Reiner Steib
2007-10-27 17:33         ` Randy Yates [this message]
2007-10-27 20:21           ` Reiner Steib
2007-10-27 21:19             ` Randy Yates
2007-12-28  0:10     ` Randy Yates

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=m3tzocbgyn.fsf@ieee.org \
    --to=yates@ieee.org \
    --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).