unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lennart Borgman \(gmail\)'" <lennart.borgman@gmail.com>
Cc: 'Chong Yidong' <cyd@stupidchicken.com>, emacs-devel@gnu.org
Subject: RE: suggestion: add link to Emacs manual node `Bugs' in	report-emacs-bug instructions
Date: Tue, 7 Oct 2008 13:36:01 -0700	[thread overview]
Message-ID: <002701c928bc$50591d70$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <48EBC554.9050501@gmail.com>

> Just insert a text button, try this
> (defun insert-bug-info-link ()
>   (let ((inhibit-read-only t))
>     (insert-text-button "Reporting Bugs"
>                         'action
>                         (lambda (btn)
>                           (info-other-window "(emacs) Bugs")))))
> 
> I think the best would be to install such a change right now. It will
> help getting Emacs 23.1 out of the door.

I didn't try it, but if it works, sounds good - send a patch perhaps?

However, it would be better for the button to say "Bug Report Guidelines" or
some such, to let users know that it will show them information that will help
them fill out a bug report. It is not so much an action button as a button/link
that displays additional information, and its label should let users know that.


[FWIW, I disagree that we should now be getting 23.1 out the door. From what I
see it is far too unstable and still has tremendous bugs. I haven't had much
luck in debugging or tracking down the problems I see, but for my own
one-buffer-per-frame-by-default use it is, well, completely unusable. Not a
complaint, just a judgment that IMO it's nowhere near ready to "get out the
door".]





  reply	other threads:[~2008-10-07 20:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 19:50 suggestion: add link to Emacs manual node `Bugs' in report-emacs-bug instructions Drew Adams
2008-10-07 20:00 ` Chong Yidong
2008-10-07 20:06   ` Drew Adams
2008-10-07 20:23     ` Lennart Borgman (gmail)
2008-10-07 20:36       ` Drew Adams [this message]
2008-10-07 20:48       ` Stefan Monnier
2008-10-10 18:37   ` Reiner Steib

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002701c928bc$50591d70$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).