From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: M-x indent-region
Date: Mon, 05 May 2003 20:49:54 +0200 [thread overview]
Message-ID: <84k7d5kz3h.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: see-message-456731.10143205052003@corp.newsfeeds.com
Sanford Selznick <see-message@for.real.address.com> writes:
> Well, for starters, it doesn't indent C++. ;-) Beyond that, it's more
> of a reformatter than a pure indenter, like emacs. The emacs indent
> doesn't change the line number of any given token... all it does is
> change the indent of a given line.
I'm sure you can tell GNU indent to abstain from adding or removing
newlines. But then, I haven't used it.
--
file-error; Data: (Opening input file no such file or directory ~/.signature)
next prev parent reply other threads:[~2003-05-05 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 0:36 M-x indent-region Sanford Selznick
2003-05-05 6:12 ` Kai Großjohann
2003-05-05 8:03 ` Alfred M. Szmidt
[not found] ` <mailman.5568.1052122245.21513.help-gnu-emacs@gnu.org>
2003-05-05 17:14 ` Sanford Selznick
2003-05-05 18:49 ` Kai Großjohann [this message]
2003-05-05 22:38 ` Sanford Selznick
2003-05-06 16:45 ` Kai Großjohann
2003-05-07 3:47 ` Sanford Selznick
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=84k7d5kz3h.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).