Your message dated Fri, 6 Jul 2012 16:43:19 +0100
with message-id 
<capq4b8n+5zkqc3qpkrfpwhggxuuc9a5az1kgwy54unk0jq3...@mail.gmail.com>
and subject line Closing orphan/obsolete bugs (emacs21 with tag fixed-upstream)
has caused the Debian Bug report #376041,
regarding emacs21: M-x occur with regexp "^[^#]" fails with "Args out of 
range:".
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
376041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=376041
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: emacs21
Version: 21.4a-1
Severity: normal

I wanted to show the non-comment lines in a config file I was editing,
so I tried to use the M-x occur (a.k.a. list-matching-lines) command
with the regexp "^[^#]" (without the quotes).  This failed with "Args
out of range: NUMBER NUMBER".  It turns out that the [^#] fragment
also matches the newline character, which I was not expecting, since
the documentation for the "occur" command says "Display a list showing
each *line* in the buffer that contains a match..." (my emphasis).

The current behaviour is not useful, inconsistent with documentation,
and an nuisance to the use of the command.  I consider it a bug; in my
opinion it should be changed to not match the newline character.

/Teddy

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.16-2-686-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages emacs21 depends on:
ii  emacs21-bin-common 21.4a-1               The GNU Emacs editor's shared, arc
ii  libc6              2.3.2.ds1-22sarge4    GNU C Library: Shared libraries an
ii  libice6            4.3.0.dfsg.1-14sarge1 Inter-Client Exchange library
ii  libjpeg62          6b-10                 The Independent JPEG Group's JPEG 
ii  libncurses5        5.4-4                 Shared libraries for terminal hand
ii  libpng12-0         1.2.8rel-1            PNG library - runtime
ii  libsm6             4.3.0.dfsg.1-14sarge1 X Window System Session Management
ii  libtiff4           3.7.2-5               Tag Image File Format (TIFF) libra
ii  libungif4g         4.1.3-2sarge1         shared library for GIF images (run
ii  libx11-6           4.3.0.dfsg.1-14sarge1 X Window System protocol client li
ii  libxext6           4.3.0.dfsg.1-14sarge1 X Window System miscellaneous exte
ii  libxmu6            4.3.0.dfsg.1-14sarge1 X Window System miscellaneous util
ii  libxpm4            4.3.0.dfsg.1-14sarge1 X pixmap library
ii  libxt6             4.3.0.dfsg.1-14sarge1 X Toolkit Intrinsics
ii  xaw3dg             1.5+E-8               Xaw3d widget set
ii  xlibs              4.3.0.dfsg.1-14sarge1 X Keyboard Extension (XKB) configu
ii  zlib1g             1:1.2.2-4.sarge.2     compression library - runtime

-- no debconf information


--- End Message ---
--- Begin Message ---
Hello,

Thanks for your interest in improving Debian, and sorry that the bugs
were not fully resolved or closed in due time.

emacs21 packages have been removed from testing in 2009 [1], not
present even in the current stable.  Consequently, these bugs are now
orphan (without maintainer assigned) so they probably will not be
attended/noticed further.

[1] http://packages.qa.debian.org/e/emacs21.html

The bugs deemed valid are going to be verified and reassigned, but the
current bugs that I'm closing now are very ancient (more than 10 years
sometimes) and marked as fixed-upstream years ago, with no recent
input, and are supposed to be fixed in emacs22 at the latest.

Please comment if you want think that some of the raised questions are
still pending and need to be addressed differently (e.g., reassigned
to other packages, etc.).

Cheers.


--- End Message ---

Reply via email to