unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: michael_heerdegen@web.de, 22613@debbugs.gnu.org,
	monnier@iro.umontreal.ca
Subject: bug#22613: 25.1.50; dired-aux missing require 'cl-lib
Date: Tue, 16 Feb 2016 17:57:20 +0200	[thread overview]
Message-ID: <83lh6kwsv3.fsf@gnu.org> (raw)
In-Reply-To: <4fegcd5e1m.fsf@fencepost.gnu.org> (message from Glenn Morris on Tue, 16 Feb 2016 02:07:17 -0500)

> From: Glenn Morris <rgm@gnu.org>
> Date: Tue, 16 Feb 2016 02:07:17 -0500
> Cc: Michael Heerdegen <michael_heerdegen@web.de>, 22613@debbugs.gnu.org
> 
> --- a/lisp/emacs-lisp/cl-generic.el
> +++ b/lisp/emacs-lisp/cl-generic.el
> @@ -1019,6 +1019,10 @@ cl--generic-eql-used
 
>  (cl--generic-prefill-dispatchers 0 (eql nil))
>  (cl--generic-prefill-dispatchers window-system (eql nil))
> +(cl--generic-prefill-dispatchers (terminal-parameter nil 'xterm--get-selection)
> +                                 (eql nil))
> +(cl--generic-prefill-dispatchers (terminal-parameter nil 'xterm--set-selection)
> +                                 (eql nil))

Is the problem really worth putting such "magic" into our sources?  If
it does, I think we should document this somewhere, at least.

Thanks.





  parent reply	other threads:[~2016-02-16 15:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 13:37 bug#22613: 25.1.50; dired-aux missing require 'cl-lib Tino Calancha
2016-02-13 14:24 ` Eli Zaretskii
2016-02-13 14:32   ` Michael Heerdegen
2016-02-13 15:09     ` Eli Zaretskii
2016-02-13 16:17       ` Michael Heerdegen
2016-02-13 16:44         ` Eli Zaretskii
2016-02-13 17:43           ` Michael Heerdegen
2016-02-13 18:00             ` Eli Zaretskii
2016-02-13 17:58       ` Glenn Morris
2016-02-13 18:13         ` Eli Zaretskii
2016-02-13 18:20           ` Glenn Morris
2016-02-13 18:45             ` Glenn Morris
2016-02-13 18:52               ` Stefan Monnier
2016-02-13 19:05                 ` Stefan Monnier
2016-02-13 19:57                 ` Michael Heerdegen
2016-02-13 22:09                   ` Stefan Monnier
2016-02-16  7:07                     ` Glenn Morris
2016-02-16 13:16                       ` Stefan Monnier
2016-02-16 15:57                       ` Eli Zaretskii [this message]
2016-02-16 19:41                         ` Stefan Monnier
2016-02-13 21:11             ` Eli Zaretskii
2016-02-13 21:23               ` Glenn Morris
2016-02-13 21:33                 ` Eli Zaretskii
2016-02-14 22:47                   ` Glenn Morris
2016-02-15  3:36                     ` Eli Zaretskii
2016-02-15  8:14                       ` Stephen Berman
2016-02-15 11:36                         ` Michael Heerdegen
2016-02-15 12:58                           ` Andreas Schwab

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=83lh6kwsv3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22613@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=monnier@iro.umontreal.ca \
    --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 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).