From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Gregor Zattler <telegraph@gmx.net>, emacs-devel@gnu.org
Subject: Re: bug#7419: 24.0.50; emacs -Q -nw positions cursor in empty lines on the second column
Date: Wed, 17 Nov 2010 14:41:28 -0500 [thread overview]
Message-ID: <l9y68r68lz.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <8362vvda2j.fsf@gnu.org> (Eli Zaretskii's message of "Wed\, 17 Nov 2010 21\:28\:04 +0200")
(There is a help-debbugs mailing list.)
>> http://debbugs.gnu.org/cgi/pkgreport.cgi?ordering=age;package=Emacs
>>
>> Tassilo's bug report does not show up. Do you know why?
Well, it's merged now, and the merged bug shows up, so who knows.
I'd guess any issues are due to the hack I put in to limit the max
number of displayed bugs. There are too many Emacs bugs for them all
to be listed on a single page.
May I suggest searching for subject keywords before filing a bug?
Or looking at the N newest bugs.
next prev parent reply other threads:[~2010-11-17 19:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 10:59 bug#7419: 24.0.50; emacs -Q -nw positions cursor in empty lines on the second column Gregor Zattler
2010-11-17 12:17 ` Eli Zaretskii
2010-11-17 16:35 ` Gregor Zattler
2010-11-17 19:28 ` Eli Zaretskii
2010-11-17 19:41 ` Glenn Morris [this message]
2010-11-18 7:48 ` Searching bugs before filing new ones (was: Re: bug#7419: 24.0.50; emacs -Q -nw positions cursor in empty lines on the second column) Tassilo Horn
2010-11-18 8:19 ` Searching bugs before filing new ones Glenn Morris
2010-11-18 10:14 ` Searching bugs before filing new ones (was: Re: bug#7419: 24.0.50; emacs -Q -nw positions cursor in empty lines on the second column) Eli Zaretskii
2010-11-18 16:40 ` Andrew W. Nosenko
2010-11-18 18:19 ` Stephen J. Turnbull
2010-11-18 21:22 ` Searching bugs before filing new ones Glenn Morris
2010-11-18 22:20 ` Stefan Monnier
2010-11-19 11:51 ` tomas
2010-11-19 20:29 ` Glenn Morris
2010-11-21 20:10 ` tomas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=l9y68r68lz.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=telegraph@gmx.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.