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 17:19:15 -0400 [thread overview]
Message-ID: <m3fxzw9rxo.fsf@ieee.org> (raw)
In-Reply-To: <v9fxzw48cq.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Sat, Oct 27 2007, Randy Yates wrote:
>
>> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>>> 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.
>
> Nevertheless you can describe your problem/question/whatever in
> annoying, painstaking detail.
I could, yes. However, I won't. I will describe it with "sufficient"
detail. If there is something you don't understand, ask for
clarification.
>> By syntax-completion, I mean things such as automatic indentation
>> after a <RET> that occurs when in certain programming language major
>> modes.
>
> I.e. you didn't observe this in message mode?
The truth is, I *thought* I observed some sort of "syntax-completion"
action (that wasn't just auto-filling) in message mode once, but I
accidently deleted it so quickly I didn't get a chance to see what it
was.
>> 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.
>
> I have enabled it by default because overlong lines are bad netiquette
> and most people like to have it on by default. Cf. the FAQ (info
> "(gnus)[5.2]"): "How to enable automatic word-wrap when composing
> messages?".
I'm not questioning the validity of the default value, just asking
how to turn it off.
>>> When upgrading you should always read GNUS-NEWS aka...
>>
>> Unless someone told me to read it, how would I know?
>
> As you already guessed, the behavior changed since 5.10.*, so it's
> quite plausible to look under "New Features" in the manual or
> something names "*-NEWS" in the distribution tar-ball. Isn't it?
A hell of a lot of things are plausible, if you have the time.
>> By the way, is there a PDF of the updated manual for the gnus
>> development version?
>
> In the source distribution, do...
>
> cd texi; make pdf
A straightforward response to a simple question. Thanks.
--
% Randy Yates % "How's life on earth?
%% Fuquay-Varina, NC % ... What is it worth?"
%%% 919-577-9882 % 'Mission (A World Record)',
%%%% <yates@ieee.org> % *A New World Record*, ELO
http://www.digitalsignallabs.com
next prev parent reply other threads:[~2007-10-27 21:19 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
2007-10-27 20:21 ` Reiner Steib
2007-10-27 21:19 ` Randy Yates [this message]
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=m3fxzw9rxo.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).