unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: michael.cadilhac@lrde.org (Michaël Cadilhac)
Subject: Local values of PC-word-delimiters.
Date: Sat, 15 Apr 2006 16:05:44 +0200	[thread overview]
Message-ID: <87lku753yf.fsf@lrde.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1115 bytes --]


  Hi !

  I've a problem I can't solve in a clean way, here.

  I   want  that  when   `gnus-group-jump-to-group'  is   called,  its
  completing-read (PC enabled) uses `:' as PC-word-delimiters.

  Easy you say ? Thought so ;-)

  I first tried

  (add-hook 'gnus-group-mode
            (lambda ()
              (set (make-local-variable 'PC-word-delimiters) ":")))

  But it was no use since we're in the minibuffer when
  PC-word-delimiters is read.

  I then tried

  (defadvice gnus-group-jump-to-group (around dummy-name activate)
    (let ((PC-word-delimiters ":"))
      ad-do-it))

  But since `gnus-group-jump-to-group' uses completing-read in its
  `interactive' part, the advice is executed AFTER it.

  Do you have any clean solution ?

  Thanks.

-- 
 |      Michaël `Micha' Cadilhac   |   Mieux vaut se taire                  |
 |         Epita/LRDE Promo 2007   |    Que de parler trop fort.            |
 | http://www.lrde.org/~cadilh_m   |            -- As de trèfle             |
 `--  -   JID: micha@amessage.be --'                                   -  --'

[-- Attachment #1.2: Type: application/pgp-signature, Size: 188 bytes --]

[-- Attachment #2: Type: text/plain, Size: 152 bytes --]

_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs

             reply	other threads:[~2006-04-15 14:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-15 14:05 Michaël Cadilhac [this message]
2006-04-17 16:22 ` Local values of PC-word-delimiters Kevin Rodgers
2006-04-17 17:03   ` Michaël Cadilhac
2006-04-18 10:05     ` Michaël Cadilhac
2006-04-19 16:14       ` Kevin Rodgers

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=87lku753yf.fsf@lrde.org \
    --to=michael.cadilhac@lrde.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.
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).