all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: 29599@debbugs.gnu.org
Subject: bug#29599: 26.0; `dframe.el' binds keys unconditionally when loaded
Date: Tue, 19 Dec 2017 08:15:11 -0500	[thread overview]
Message-ID: <873746c10g.fsf@users.sourceforge.net> (raw)
In-Reply-To: <afabe25c-0360-489b-9c5a-d9d38da1fd24@default> (Drew Adams's message of "Mon, 18 Dec 2017 21:21:25 -0800 (PST)")

Drew Adams <drew.adams@oracle.com> writes:

> That's quite a bug report - no report at all (?).
>
> Perhaps it was because all of the actual report was
> in another bug report that was closed, and that now
> redirects to this (vacuous) report?
>
> The only thing in #28607 is a link to an emacs-devel
> thread.  No description of the problem (?).
>
> Anyway, it's not clear to me how that bug relates to this one.
>
> This one is about explicitly binding keys when the
> source code loads.  I don't get the impression that
> that one is about this at all.  (What am I missing?)

Oh, yeah, I probably should have pointed to the linked stuff.  Bug#28048
has more info.

Anyway, the relation is just that it probably explains how you got
dframe loaded (I have got dframe loaded in my session as well, even
though I don't use it).





  reply	other threads:[~2017-12-19 13:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07  6:10 bug#29599: 26.0; `dframe.el' binds keys unconditionally when loaded Drew Adams
2017-12-19  1:40 ` Noam Postavsky
2017-12-19  2:15   ` Drew Adams
2017-12-19  3:51     ` Noam Postavsky
2017-12-19  5:21       ` Drew Adams
2017-12-19 13:15         ` Noam Postavsky [this message]
2017-12-19 15:22           ` Drew Adams
2018-01-03  1:59       ` Noam Postavsky

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=873746c10g.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=29599@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 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.