bug#7494: 24.0.50; Why is `prefix-region' in a library by itself?

bug#7494: 24.0.50; Why is `prefix-region' in a library by itself?

[Drew Adams]

(defun prefix-region (prefix)
  "Insert PREFIX at the beginning of each line between mark and point."
  (interactive "sPrefix string: ")
  (let ((end (region-end)))
    (save-excursion
      (goto-char (region-beginning))
      (beginning-of-line)
      (save-restriction
	(narrow-to-region (point) end)
	(while (not (eobp))
	  (insert prefix)
	  (forward-line 1))))))

(provide 'prefix-region)

What's that about?

bug#7494: 24.0.50; Why is `prefix-region' in a library by itself?

[Leo]

On 2010-11-26 22:48 +0000, Drew Adams wrote:
> (defun prefix-region (prefix)
>   "Insert PREFIX at the beginning of each line between mark and point."
>   (interactive "sPrefix string: ")
>   (let ((end (region-end)))
>     (save-excursion
>       (goto-char (region-beginning))
>       (beginning-of-line)
>       (save-restriction
> 	(narrow-to-region (point) end)
> 	(while (not (eobp))
> 	  (insert prefix)
> 	  (forward-line 1))))))
>
> (provide 'prefix-region)
>
> What's that about?

There seems to be a few of those files. Maybe move them to the online
packages.

Leo

bug#7494: 24.0.50; Why is `prefix-region' in a library by itself?

[Drew Adams]

> There seems to be a few of those files. Maybe move them to the online
> packages.

No, this was my bad.
This is not a (distributed) Emacs library.

bug#7494: 24.0.50; Why is `prefix-region' in a library by itself?

[Stefan Monnier]

> (defun prefix-region (prefix)
[...]
> What's that about?

My words exactly: what's that about?
I can't find this code in Emacs, so I wonder what your bug report
is about.  Are you suggesting we include this command in Emacs (I can't
see why that would be useful since the rectangle-insert function works
about as well for that).


        Stefan

bug#7494: 24.0.50; Why is `prefix-region' in a library by itself?

[Drew Adams]

> I can't find this code in Emacs, so I wonder what your bug report
> is about.  Are you suggesting we include this command in 
> Emacs (I can't see why that would be useful since the
> rectangle-insert function works about as well for that).

You are certainly very quick when it doesn't count. ;-)

I mistakenly created this bug report and within 6 minutes I had closed it.

bug#7494: 24.0.50; Why is `prefix-region' in a library by itself?

[Thierry Volpiatto]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> (defun prefix-region (prefix)
> [...]
>> What's that about?
>
> My words exactly: what's that about?
> I can't find this code in Emacs, so I wonder what your bug report
> is about.  Are you suggesting we include this command in Emacs (I can't
> see why that would be useful since the rectangle-insert function works
> about as well for that).
BTW it seem emacs doesn't have the contrary, i.e insert at end of rectangle,
what is sometime useful:

> My words exactly: what's that about?                                   >>>HERE
> I can't find this code in Emacs, so I wonder what your bug report      >>>HERE
> is about.  Are you suggesting we include this command in Emacs (I can't>>>HERE
> see why that would be useful since the rectangle-insert function works >>>HERE
> about as well for that).                                               >>>HERE

I use here C-x r <right>
I have code if interested, if not ignore message.

-- 
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 

bug#7494: 24.0.50; Why is `prefix-region' in a library by itself?

[Eli Zaretskii]

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Fri, 26 Nov 2010 19:00:38 -0800
> Cc: 7494@debbugs.gnu.org
> 
> You are certainly very quick when it doesn't count. ;-)

It's unfair to post such comments.

The time it takes to respond to a bug report depends on any number of
factors, including (but not limited to) the maintainer's understanding
of the Emacs area where the bug happens, the time it takes to
reproduce the problem, the amount of free time (holidays etc.), you
name it.  In this case, I'm guessing that it took about a few seconds
to find out that there's no such code anywhere in Emacs.

bug#7494: 24.0.50; Why is `prefix-region' in a library by itself?

[Stefan Monnier]

>> You are certainly very quick when it doesn't count. ;-)
> It's unfair to post such comments.

Well, when compared to some of my backlog where I still have posts more
than 2 years old, it's probably not that unfair.

> The time it takes to respond to a bug report depends on any number of
> factors, including (but not limited to) the maintainer's understanding
> of the Emacs area where the bug happens, the time it takes to
> reproduce the problem, the amount of free time (holidays etc.), you
> name it.  In this case, I'm guessing that it took about a few seconds
> to find out that there's no such code anywhere in Emacs.

Indeed, it was an easy one.


        Stefan

bug#7494: 24.0.50; Why is `prefix-region' in a library by itself?

[Eli Zaretskii]

> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: Drew Adams <drew.adams@oracle.com>, 7494@debbugs.gnu.org
> Date: Sat, 27 Nov 2010 09:20:54 -0500
> 
> >> You are certainly very quick when it doesn't count. ;-)
> > It's unfair to post such comments.
> 
> Well, when compared to some of my backlog where I still have posts more
> than 2 years old, it's probably not that unfair.

It's unfair to assume that you handle quickly bugs that are
unimportant, but leave alone the important ones.

bug#7494: 24.0.50; Why is `prefix-region' in a library by itself?

[Drew Adams]

> > You are certainly very quick when it doesn't count. ;-)
> 
> It's unfair to post such comments.

You are silly to jump on such a comment (with a kidding smily yet!) as if it
were a nasty complaint or criticism.  For the record, I do not consider Stefan
to act quickly only on bug reports that are unimportant.

> The time it takes to respond to a bug report depends on any number of
> factors, including (but not limited to) the maintainer's understanding
> of the Emacs area where the bug happens, the time it takes to
> reproduce the problem, the amount of free time (holidays etc.), you
> name it.  In this case, I'm guessing that it took about a few seconds
> to find out that there's no such code anywhere in Emacs.

And I, for my part, would have closed the mistaken report sooner than within 6
minutes, if I had had a bug number to close.

As soon as I posted the bug report I realized my mistake, but I had to wait
until the bug showed up at http://debbugs.gnu.org/ to get the number. I
specifically went to that site instead of waiting for the confirmation mail with
the bug number (which takes even longer), in order to shorten the time before
closing.  IOW, I closed the bug as quickly as I knew how.

bug#7494: 24.0.50; Why is `prefix-region' in a library by itself?

[Stefan Monnier]

Well, thank you all, Drew and Eli, for this fun discussion.
Are those little mishaps entertaining or what?


        Stefan


>>>>> "Drew" == Drew Adams <drew.adams@oracle.com> writes:

>> > You are certainly very quick when it doesn't count. ;-)
>> 
>> It's unfair to post such comments.

> You are silly to jump on such a comment (with a kidding smily yet!) as if it
> were a nasty complaint or criticism.  For the record, I do not consider Stefan
> to act quickly only on bug reports that are unimportant.

>> The time it takes to respond to a bug report depends on any number of
>> factors, including (but not limited to) the maintainer's understanding
>> of the Emacs area where the bug happens, the time it takes to
>> reproduce the problem, the amount of free time (holidays etc.), you
>> name it.  In this case, I'm guessing that it took about a few seconds
>> to find out that there's no such code anywhere in Emacs.

> And I, for my part, would have closed the mistaken report sooner than within 6
> minutes, if I had had a bug number to close.

> As soon as I posted the bug report I realized my mistake, but I had to wait
> until the bug showed up at http://debbugs.gnu.org/ to get the number. I
> specifically went to that site instead of waiting for the confirmation mail with
> the bug number (which takes even longer), in order to shorten the time before
> closing.  IOW, I closed the bug as quickly as I knew how.