unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: [elpa] 01/01: [xpm int] Use cl-* names; drop ‘cl’ requirement.
Date: Wed, 23 Jul 2014 17:31:05 +0200	[thread overview]
Message-ID: <87fvhsytvq.fsf@zigzag.favinet> (raw)
In-Reply-To: <jwvvbry3vu9.fsf-monnier+emacsdiffs@gnu.org> (Stefan Monnier's message of "Wed, 18 Jun 2014 14:43:14 -0400")

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

() Stefan Monnier <monnier@iro.umontreal.ca>
() Wed, 18 Jun 2014 14:43:14 -0400

   You might want to check revision 115224 where I changed
   gomoku.el to avoid `intangible' properties.

   You'll see there's no special support for it, so it's no
   simpler than using `intangible' properties.

   But `intangible' properties operate at a very low-level
   so they tend to cause surprising problems because they
   affect a lot more code than intended.

Thanks for the tip.  I will explore dropping use of
‘intangible’ in gnugo.el (et al) in the future.

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2014-07-23 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140613120120.13821.79283@vcs.savannah.gnu.org>
     [not found] ` <E1WvQAa-0003bv-OE@vcs.savannah.gnu.org>
2014-06-13 14:16   ` [elpa] 01/01: [xpm int] Use cl-* names; drop ‘cl’ requirement Stefan Monnier
2014-06-18 16:42     ` Thien-Thi Nguyen
2014-06-18 18:43       ` Stefan Monnier
2014-07-23 15:31         ` Thien-Thi Nguyen [this message]

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=87fvhsytvq.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --cc=emacs-devel@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).