From: Tassilo Horn <heimdall@uni-koblenz.de>
Subject: Re: a couple of newbie questions with gnus
Date: Sun, 28 May 2006 11:19:34 +0200 [thread overview]
Message-ID: <87ac92qzfd.fsf@baldur.nicundtas.de> (raw)
In-Reply-To: <uslkk3-km2.ln1@news.tdc.dk>
unoder.spam@spam.jay.net (Martin Jørgensen) writes:
Hi Martin,
> Thanks a lot! Everything seem to work now - this message is from
> gnus...
Congratulations!
> But I still think I should follow this group for a while and perhaps
> google for some gnus tutorials
The tutorial is here: http://my.gnus.org/tutorial/
> or something... There are still a lot of small "problems" that annoys
> me a bit...
One of which is that you poste too long lines, right?
To automatically wrap lines at 72 chars, put something like that into
your ~/.emacs (or ~/.gnus.el, but message-mode belongs to emacs, so I
have it in its init file):
(add-hook 'message-mode-hook
(lambda ()
(setq fill-column 72)
(turn-on-auto-fill)))
To reformat a paragraph simply hit `M-q'.
,----[ C-h k M-q ]
| M-q runs the command fill-paragraph
| which is an interactive compiled Lisp function in `fill.el'.
| It is bound to M-q.
| (fill-paragraph ARG)
|
| Fill paragraph at or after point. Prefix ARG means justify as well.
| If `sentence-end-double-space' is non-nil, then period followed by one
| space does not end a sentence, so don't break a line there. the
| variable `fill-column' controls the width for filling.
|
| If `fill-paragraph-function' is non-nil, we call it (passing our
| argument to it), and if it returns non-nil, we simply return its
| value.
|
| If `fill-paragraph-function' is nil, return the `fill-prefix' used for
| filling.
`----
Bye,
Tassilo
--
"Emacs is not a development tool but a way of life."
- David Kastrup in alt.religion.emacs -
next prev parent reply other threads:[~2006-05-28 9:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 16:28 Martin Jørgensen
2006-05-23 16:57 ` David Z Maze
2006-05-24 23:05 ` Martin Jørgensen
2006-05-25 8:46 ` Alexander Ponomarenko
2006-05-25 15:03 ` Martin Jørgensen
2006-05-25 15:38 ` Malte Spiess
2006-05-25 23:06 ` Martin Jørgensen
2006-05-26 6:24 ` Malte Spiess
2006-05-26 15:20 ` Martin Jørgensen
2006-05-26 17:47 ` Tassilo Horn
[not found] ` <mailman.2324.1148665716.9609.info-gnus-english@gnu.org>
2006-05-26 18:29 ` Karl Kleinpaste
2006-05-26 19:28 ` Martin Jørgensen
2006-05-26 20:32 ` Reiner Steib
2006-05-27 1:16 ` Martin Jørgensen
2006-05-28 9:19 ` Tassilo Horn [this message]
[not found] ` <mailman.2366.1148808000.9609.info-gnus-english@gnu.org>
2006-05-28 15:22 ` Martin Jørgensen
2006-05-28 16:16 ` Tassilo Horn
2006-05-28 16:38 ` Reiner Steib
2006-05-28 17:05 ` David Kastrup
2006-05-30 14:01 ` Reiner Steib
2006-05-30 15:33 ` David Kastrup
2006-05-31 22:35 ` Martin Jørgensen
2006-06-01 8:02 ` David Kastrup
2006-06-05 13:15 ` david.reitter
2006-06-15 13:55 ` Aking TIAN
2006-05-29 9:23 ` Reiner Steib
[not found] ` <mailman.2368.1148833009.9609.info-gnus-english@gnu.org>
2006-05-29 18:13 ` Martin Jørgensen
2006-05-29 22:22 ` Reiner Steib
2006-05-31 2:18 ` Martin Jørgensen
2006-05-31 8:13 ` Reiner Steib
2006-05-31 22:56 ` Martin Jørgensen
2006-05-30 17:45 ` Tassilo Horn
[not found] ` <mailman.2439.1149011220.9609.info-gnus-english@gnu.org>
2006-05-31 3:10 ` Martin Jørgensen
2006-05-23 22:02 ` Johan Bockgård
2006-05-24 23:08 ` Martin Jørgensen
2006-05-24 11:12 ` Alexander Ponomarenko
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=87ac92qzfd.fsf@baldur.nicundtas.de \
--to=heimdall@uni-koblenz.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 NNTP newsgroup(s).