unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Bastien <bzg@altern.org>, Tim Cross <theophilusx@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: [emacs-w3m:11603] Re: interactive-p obsolete
Date: Thu, 7 Jul 2011 01:16:34 +0200	[thread overview]
Message-ID: <CANbX365pkXDC6X4VGpY_WN6-K=sE5wSPkXdtjMy=SsC6LXk_cg@mail.gmail.com> (raw)
In-Reply-To: <CAAeL0SSPrexoBTsfLCz1X4KmgecBmvxN4YLbFdPeR3R4FWAy+w@mail.gmail.com>

On Thu, Jul 7, 2011 at 01:10, Juanma Barranquero <lekktu@gmail.com> wrote:
> On Thu, Jul 7, 2011 at 01:08, Lennart Borgman <lennart.borgman@gmail.com> wrote:
>
>> For things outside Emacs trunk.
>
> Either I don't understand you, or you didn't understand me. Such a
> compatibility macro would only be useful for "things outside Emacs
> trunk" if they are *only* to be used *with* the Emacs trunk. Else,
> they have to define their own compatibility macro for the cases when
> they are used with older Emacsen, XEmacs, etc.

;-) -- Yes, you are right. But it could be defined in a separate
compatibility elisp file that could be copied to Xemacs and copied
"privately" for those using it with older emacsen.



  reply	other threads:[~2011-07-06 23:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06  6:12 Fwd: [emacs-w3m:11603] Re: interactive-p obsolete Andreas Röhler
2011-07-06  7:09 ` Tim Cross
2011-07-06  8:54   ` Bastien
2011-07-06 18:16     ` Lennart Borgman
2011-07-06 18:33       ` Bastien
2011-07-06 22:51       ` Juanma Barranquero
2011-07-06 23:08         ` Lennart Borgman
2011-07-06 23:10           ` Juanma Barranquero
2011-07-06 23:16             ` Lennart Borgman [this message]
2011-07-06 23:32               ` Juanma Barranquero
2011-07-06 23:44                 ` Lennart Borgman
2011-07-06 23:47                   ` Juanma Barranquero
2011-07-06 23:57                     ` Lennart Borgman
2011-07-07  0:01                       ` Juanma Barranquero
2011-07-07  0:12                         ` Lennart Borgman
2011-07-07  0:32                           ` Juanma Barranquero
2011-07-07  0:44                             ` Lennart Borgman
2011-07-07  0:54                               ` Juanma Barranquero
2011-07-07 11:38                                 ` Bastien
2011-07-07 11:50                                   ` Lennart Borgman
2011-07-07 15:37                                     ` Stephen J. Turnbull
2011-07-06 11:22   ` Andreas Röhler
2011-07-07  0:06     ` Tim Cross
2011-07-07  6:52       ` Andreas Röhler
2011-07-07 11:36         ` Bastien
2011-07-07 12:55           ` Andreas Röhler
2011-07-07 13:41             ` Juanma Barranquero
2011-07-08  9:57             ` Bastien
2011-07-07 20:10 ` Fwd: " Stefan Monnier
2011-07-09  2:52   ` Tim Cross

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='CANbX365pkXDC6X4VGpY_WN6-K=sE5wSPkXdtjMy=SsC6LXk_cg@mail.gmail.com' \
    --to=lennart.borgman@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=theophilusx@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).