unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: replace-regexp, the byte-compiler, docstrings, and suggestions
Date: Fri, 17 Oct 2014 01:55:25 +0200	[thread overview]
Message-ID: <87tx336042.fsf@debian.uxu> (raw)
In-Reply-To: mailman.11050.1413145964.1147.help-gnu-emacs@gnu.org

John Mastro <john.b.mastro@gmail.com> writes:

> I sent this from my phone. I think the formatting
> should be okay, but apologies in advance if I'm wrong
> about that.

No, looks good.

> Would indent-rigidly (or, less likely,
> indent-code-rigidly) do what you want?

Yeah, indent-rigidly is close only this

    (indent-rigidly (region-beginning) (region-end) 4)

seems to sometimes insert tabs (one tab and one space
in text-mode, but four spaces in message-mode what I
can see). If you can have it not do that (insert tabs,
ever) I'm happy. (I have tabs removed on save but I
still don't like to insert them for the same reason I
have them removed.)

Question is (which I didn't mention in my OP), should
the region be refilled after it gets the new margin,
and, if so, what should the fill-column be?

> To indent by four spaces you would do something like
> C-4 C-x <tab>

Yeah, you mean `C-u 4 C-x TAB'? (`C-x TAB' is
`indent-rigidly'.)

-- 
underground experts united


  parent reply	other threads:[~2014-10-16 23:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12 18:28 replace-regexp, the byte-compiler, docstrings, and suggestions Emanuel Berg
2014-10-12 20:32 ` John Mastro
2014-10-13  0:50 ` Robert Thorpe
     [not found] ` <mailman.11050.1413145964.1147.help-gnu-emacs@gnu.org>
2014-10-16 23:55   ` Emanuel Berg [this message]
2014-10-17  0:07     ` Drew Adams
     [not found]     ` <mailman.11343.1413504497.1147.help-gnu-emacs@gnu.org>
2014-10-17  1:09       ` Emanuel Berg
2014-10-17  2:22         ` Drew Adams
2014-10-18 17:57         ` Robert Thorpe
2014-10-17  2:26     ` John Mastro
2014-10-17  3:05       ` Stefan Monnier
     [not found]       ` <mailman.11351.1413515156.1147.help-gnu-emacs@gnu.org>
2014-10-17 23:21         ` Emanuel Berg
     [not found]     ` <mailman.11350.1413512841.1147.help-gnu-emacs@gnu.org>
2014-10-17 19:11       ` Emanuel Berg
2014-10-17 19:20         ` Stefan Monnier
     [not found]         ` <mailman.11400.1413573661.1147.help-gnu-emacs@gnu.org>
2014-10-17 19:38           ` Emanuel Berg
2014-10-17 20:15             ` Stefan Monnier
     [not found]             ` <mailman.11404.1413576982.1147.help-gnu-emacs@gnu.org>
2014-10-17 22:52               ` Emanuel Berg

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=87tx336042.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).