From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: org-mode + icicles, avoid key binding redefinitions? Date: Thu, 23 Jan 2014 23:24:43 +0100 Message-ID: <87lhy6l4k4.fsf@bzg.ath.cx> References: <87ob33nnwi.fsf@bzg.ath.cx> <87eh3yvgyg.fsf@bzg.ath.cx> <3bc3c5a1-1c3f-4975-9dd6-3428aabb69be@default> <87ppniu06o.fsf@bzg.ath.cx> <1c11f795-ca4a-45bf-9701-7645a0609ed1@default> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55618) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6Shf-0005hw-HR for emacs-orgmode@gnu.org; Thu, 23 Jan 2014 17:24:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W6Sha-0004QG-Np for emacs-orgmode@gnu.org; Thu, 23 Jan 2014 17:24:51 -0500 Received: from mail-we0-x235.google.com ([2a00:1450:400c:c03::235]:50768) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6Sha-0004QB-Gk for emacs-orgmode@gnu.org; Thu, 23 Jan 2014 17:24:46 -0500 Received: by mail-we0-f181.google.com with SMTP id u56so1845786wes.26 for ; Thu, 23 Jan 2014 14:24:45 -0800 (PST) In-Reply-To: <1c11f795-ca4a-45bf-9701-7645a0609ed1@default> (Drew Adams's message of "Thu, 23 Jan 2014 09:01:53 -0800 (PST)") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Drew Adams Cc: emacs-orgmode@gnu.org Drew Adams writes: > Dunno what that means. It's not a criminal offense, no. Let me quote the manual again: * Sequences consisting of `C-c' followed by any other punctuation character are allocated for minor modes. Using them in a major mode is not absolutely prohibited, but if you do that, the major mode binding may be shadowed from time to time by minor modes. That's pretty clear to me. > _You_ suggested (above) that this should be reported as an > Emacs bug. But you also don't want to push for it to be > fixed or report it, yourself. So be it. I suggested that *you* report it as a bug if you think it's a bug. I don't think it is, it's that simple. -- Bastien