all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Glenn Morris <rgm@gnu.org>, 20056@debbugs.gnu.org
Subject: bug#20056: 25.0.50; Remove non Common Lisp stuff from cl*.el libraries
Date: Mon, 29 Feb 2016 12:57:17 -0800 (PST)	[thread overview]
Message-ID: <b0e72726-7002-44ce-a3fa-c85e8b7f2d12@default> (raw)
In-Reply-To: <85io178el2.fsf@fencepost.gnu.org>

> >>> In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
> >>>  of 2015-02-27 on LEG570
> >>> Bzr revision: b2a590d4e3dc692a97c1b53e015b945d84b4b4c7
> >>  ^^^^^^^^^^^^^
> >>
> >> Dani, what's this "bzr revision" thing about?
> >
> > I don't know.
> 
> For the record, it's a bug in Someone's custom Emacs bug reporting
> package.

Yes, it came fom my library `emacsbug+.el'.
http://www.emacswiki.org/emacs/download/emacsbug%2b.el

It does this:

  (insert "\n\nIn " (emacs-version) "\n")
  (when (and (boundp 'emacs-bzr-version)  (stringp emacs-bzr-version))
    (insert "Bzr revision: " emacs-bzr-version "\n"))

Which is exactly what vanilla Emacs did too, a couple of years
ago.  I just had not updated my library to use the renamed label,
`Repository version:'.  I've done that now, so this scandalous
problem should no longer plague you.

In any case, my code does not define or set `emacs-bzr-version'.

,----
| emacs-bzr-version is a variable defined in `emacsbug+.el'.
| Its value is nil
| 
|   This variable is an alias for `emacs-repository-version'.
|   This variable is obsolete since 24.4;
|   use `emacs-repository-version' instead.
| 
| Documentation:
| String giving the repository revision from which this Emacs was built.
| Value is nil if Emacs was not built from a repository checkout,
| or if we could not determine the revision.
`----

My code uses the old name of this variable because it works,
including across multiple Emacs versions.

Naturally, I proposed the little that `emacsbugs+.el' does to
Emacs Dev for `emacsbug.el'.  Naturally, there was no interest.

What does it do?  It just lets users choose which fields to
include by default in a bug report.  What Emacs does with a
monolithic `report-emacs-bug', this library does with a modular
`report-emacs-bug'.  That's all.  Not a biggee.

User option `ebp-report-emacs-bug-included-fields':

(defcustom ebp-report-emacs-bug-included-fields
  '(version settings major-mode minor-modes recent-input
    recent-messages load-shadows features)
  "Fields to include by default for command `report-emacs-bug'.
The fields are included automatically in the buffer where you edit
your bug report."
  :type '(set
          (const :tag "Emacs version info" version)
          (const :tag "Important settings" settings)
          (const :tag "Major mode"         major-mode)
          (const :tag "Minor modes"        minor-modes)
          (const :tag "Recent input"       recent-input)
          (const :tag "Recent messages"    recent-messages)
          (const :tag "Load-path shadows"  load-shadows)
          (const :tag "Features"           features))
  :group 'emacsbug-plus :group 'convenience)

For my own purposes, I use the value `(version)': report just
the version info, by default.

There are also commands to insert all or any of the fields.
To insert recent input, for example, you can use command
`edp-insert-recent-input'.





  reply	other threads:[~2016-02-29 20:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08 18:02 bug#20056: 25.0.50; Remove non Common Lisp stuff from cl*.el libraries Drew Adams
2015-03-08 18:12 ` Eli Zaretskii
2015-03-08 19:06   ` Dani Moncayo
2015-03-08 20:10     ` Eli Zaretskii
2016-02-29 20:08     ` Glenn Morris
2016-02-29 20:57       ` Drew Adams [this message]
2015-03-08 18:21 ` Daniel Colascione
2015-03-08 18:46   ` Drew Adams
2015-03-08 19:11     ` Daniel Colascione
2015-03-08 21:12       ` Drew Adams
2015-03-08 21:19         ` Daniel Colascione
2015-03-08 21:31           ` Drew Adams
2015-03-09  4:52           ` Stefan Monnier
2019-08-02 12:50             ` Lars Ingebrigtsen
2019-08-03  2:49               ` Noam Postavsky
2019-08-03  7:49                 ` Štěpán Němec
2019-08-03 10:30                   ` Lars Ingebrigtsen
2019-08-03 12:58                     ` Noam Postavsky
2019-08-03 13:16                       ` Štěpán Němec
2019-08-03 21:10                 ` Stefan Monnier

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=b0e72726-7002-44ce-a3fa-c85e8b7f2d12@default \
    --to=drew.adams@oracle.com \
    --cc=20056@debbugs.gnu.org \
    --cc=rgm@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.