GNU bug report logs -
#7494
24.0.50; Why is `prefix-region' in a library by itself?
Previous Next
Reported by: "Drew Adams" <drew.adams <at> oracle.com>
Date: Fri, 26 Nov 2010 22:44:02 UTC
Severity: normal
Found in version 24.0.50
Done: "Drew Adams" <drew.adams <at> oracle.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 7494 in the body.
You can then email your comments to 7494 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#7494
; Package
emacs
.
(Fri, 26 Nov 2010 22:44:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"Drew Adams" <drew.adams <at> oracle.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Fri, 26 Nov 2010 22:44:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
(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 closed, send any further explanations to "Drew Adams" <drew.adams <at> oracle.com>
Request was from
"Drew Adams" <drew.adams <at> oracle.com>
to
control <at> debbugs.gnu.org
.
(Fri, 26 Nov 2010 22:50:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#7494
; Package
emacs
.
(Sat, 27 Nov 2010 02:05:01 GMT)
Full text and
rfc822 format available.
Message #10 received at 7494 <at> debbugs.gnu.org (full text, mbox):
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
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#7494
; Package
emacs
.
(Sat, 27 Nov 2010 02:15:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 7494 <at> debbugs.gnu.org (full text, mbox):
> 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.
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#7494
; Package
emacs
.
(Sat, 27 Nov 2010 02:35:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 7494 <at> debbugs.gnu.org (full text, mbox):
> (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
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#7494
; Package
emacs
.
(Sat, 27 Nov 2010 02:57:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 7494 <at> debbugs.gnu.org (full text, mbox):
> 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.
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#7494
; Package
emacs
.
(Sat, 27 Nov 2010 06:47:01 GMT)
Full text and
rfc822 format available.
Message #22 received at submit <at> debbugs.gnu.org (full text, mbox):
Stefan Monnier <monnier <at> 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
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#7494
; Package
emacs
.
(Sat, 27 Nov 2010 08:03:01 GMT)
Full text and
rfc822 format available.
Message #25 received at 7494 <at> debbugs.gnu.org (full text, mbox):
> From: "Drew Adams" <drew.adams <at> oracle.com>
> Date: Fri, 26 Nov 2010 19:00:38 -0800
> Cc: 7494 <at> 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.
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#7494
; Package
emacs
.
(Sat, 27 Nov 2010 14:16:02 GMT)
Full text and
rfc822 format available.
Message #28 received at 7494 <at> debbugs.gnu.org (full text, mbox):
>> 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
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#7494
; Package
emacs
.
(Sat, 27 Nov 2010 15:28:02 GMT)
Full text and
rfc822 format available.
Message #31 received at 7494 <at> debbugs.gnu.org (full text, mbox):
> From: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
> Cc: Drew Adams <drew.adams <at> oracle.com>, 7494 <at> 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.
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#7494
; Package
emacs
.
(Sat, 27 Nov 2010 16:06:02 GMT)
Full text and
rfc822 format available.
Message #34 received at 7494 <at> debbugs.gnu.org (full text, mbox):
> > 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.
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#7494
; Package
emacs
.
(Sat, 27 Nov 2010 18:25:02 GMT)
Full text and
rfc822 format available.
Message #37 received at 7494 <at> debbugs.gnu.org (full text, mbox):
Well, thank you all, Drew and Eli, for this fun discussion.
Are those little mishaps entertaining or what?
Stefan
>>>>> "Drew" == Drew Adams <drew.adams <at> 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.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 26 Dec 2010 12:24:03 GMT)
Full text and
rfc822 format available.
This bug report was last modified 14 years and 237 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.