From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: RE: bug#1346: Window shrinks with each invocation
Date: Sat, 15 Nov 2008 07:44:33 -0800 [thread overview]
Message-ID: <005501c94739$102aacf0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <491EDB9C.5080803@gmail.com>
This message from the bug mailing list makes me think that each bug-list mailing
should include a link at the bottom that takes you directly to the entry for
that message on the bug-list web site.
Users should not need to have memorized the bug web site URL, type it in, and
navigate to the particular bug #. They should be able to just click a link in
the mail to get to the appropriate bug entry and thread.
That is typical behavior for the bug mail communications I'm aware of. It is
typical for web-based applications that notify users by email.
You can see from the last line below that this would also help avoid filing new
bugs for the same problem.
> Subject: bug#1346: Window shrinks with each invocation
>
> > Could this be Bug#58?
>
> Maybe, I did not find a link to the bug tracker, like for all other
> software projects. Emacs only has an e-mail address for bug
> reports, so I could not search existing reports first, like I
> usually do.
next prev parent reply other threads:[~2008-11-15 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87myg0o9bk.fsf@cyd.mit.edu>
2008-11-14 14:25 ` bug#1346: Window shrinks with each invocation Erik
2008-11-15 14:12 ` martin rudalics
2008-11-15 14:24 ` Erik
2008-11-15 15:44 ` Drew Adams [this message]
2008-11-15 16:12 ` martin rudalics
2008-11-15 23:40 ` bug#1346: marked as done (Window shrinks with each invocation) Emacs bug Tracking System
2008-11-15 5:54 bug#1346: Window shrinks with each invocation Chong Yidong
2008-11-15 8:22 ` Erik
2008-11-15 16:10 ` Chong Yidong
2008-11-15 16:20 ` Erik
2008-11-15 17:26 ` Chong Yidong
2008-11-15 17:50 ` Erik
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='005501c94739$102aacf0$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
/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.