unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gian Fontanilla <prvteprts@yahoo.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Patch for delete-indentation in simple.el
Date: Fri, 23 Aug 2013 06:31:11 -0700 (PDT)	[thread overview]
Message-ID: <1377264671.59291.YahooMailBasic@web163405.mail.gq1.yahoo.com> (raw)
In-Reply-To: <jwvppt5bg2k.fsf-monnier+emacs@gnu.org>

Just some clarifications:

1) Should I create a separate function which does `delete-indentation' on a region, and not change `delete-indentation' itself?

2) If the answer to 1 is yes, what name should I give it? The feature I'm proposing is semantically closer to "join lines", rather than the inverse of `fill-region' or `fill-paragraph', so I don't think it is correct to call it "unfill". To further explain this, I envision this to be the inverse of a "split" function (not `split-line') , which will split the line into several lines based on a delimiter (whitespace by default or user specified, or can also be fill-prefix). So a line such as

one-two-three-four

when split given the delimiter (or prefix) "-", will turn into:

one
two
three
four

Then, running "join lines" on the region should get it back to the original line, granted that the prefix is "-"; otherwise the words will be separated by a single whitespace when prefix is nil.

3) > please use  `use-region-p' and make the test from within the `interactive' spec rather than inside the function itself

I can't say I understand this completely. This is assuming I am to change the body of `delete-indentation'?

Regards,
Gian

--------------------------------------------
On Fri, 8/23/13, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

 Subject: Re: Patch for delete-indentation in simple.el
 To: "Gian Fontanilla" <prvteprts@yahoo.com>
 Cc: emacs-devel@gnu.org
 Date: Friday, August 23, 2013, 5:03 AM
 
 > I'm sending this improvement for
 delete-indentation in simple.el. Please see
 > attached files Description, ChangeLog, and Patch.
 
 IIUC your suggestion is to make delete-indentation work on
 the region
 if active.  That doesn't sound bad.  Of course,
 another name for it
 is unfill-region, which has also been requested.
 
 Could you provide a patch which does that (but please use
 `use-region-p'
 and make the test from within the `interactive' spec rather
 than
 inside the function itself)?
 
 
         Stefan
 
 
 PS: Just include your own ChangeLog comment rather than the
 whole
 ChangeLog file.




  reply	other threads:[~2013-08-23 13:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22  8:59 Patch for delete-indentation in simple.el Gian Fontanilla
2013-08-22 21:03 ` Stefan Monnier
2013-08-23 13:31   ` Gian Fontanilla [this message]
2013-08-23 15:50     ` Stefan Monnier
2013-08-23 16:16     ` Josh
  -- strict thread matches above, loose matches on Subject: below --
2013-08-24  3:27 Gian Fontanilla

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=1377264671.59291.YahooMailBasic@web163405.mail.gq1.yahoo.com \
    --to=prvteprts@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).