unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: rfflrccrd@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: mic-paren.el 3.10 available
Date: Thu, 26 Jul 2012 06:19:28 +0200	[thread overview]
Message-ID: <87txwv6tnz.fsf@zigzag.favinet> (raw)
In-Reply-To: <2b42c9ad-dbde-41ce-90c5-caef9568a18e@googlegroups.com> (rfflrccrd@gmail.com's message of "Wed, 25 Jul 2012 14:54:57 -0700 (PDT)")

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

[NB: CC updated; we use the "sources" list to post/announce source code.]

() rfflrccrd@gmail.com
() Wed, 25 Jul 2012 14:54:57 -0700 (PDT)

   As I use Viper, a Vim-emulation mode, I looked into the customization
   group mic-paren-matching, hoping to find a way to emulate the way Vim
   uses to highlight parentheses.  I found nothing.  Do you confirm it
   is so?

No, but that's not saying much -- i don't use Vim.  FWIW, my mic-paren
usage is very simple:

http://www.gnuvola.org/software/personal-elisp/dist/lisp/low-stress/turn-on-mic-paren.el

   Basically, since Vim uses both a bar cursor and a block cursor,
   depending on context it highilights sometimes the parenthesis before
   the cursor and sometimes the one after the cursor.

Could you please give an example or point to one on the net?

-- 
Thien-Thi Nguyen                                       GPG key: 4C807502

........... please send technical questions to mailing lists ...........
.                                 ....                                 .
.                  NB: ttn at glug dot org is not me                   .
.                 (and has not been since 2007 or so)                  .
.                      ACCEPT NO SUBSTITUTES :-D                       .

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

       reply	other threads:[~2012-07-26  4:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.4875.1342444601.855.gnu-emacs-sources@gnu.org>
     [not found] ` <2b42c9ad-dbde-41ce-90c5-caef9568a18e@googlegroups.com>
2012-07-26  4:19   ` Thien-Thi Nguyen [this message]
     [not found]   ` <mailman.5631.1343276384.855.help-gnu-emacs@gnu.org>
2012-07-26 15:22     ` mic-paren.el 3.10 available rfflrccrd
2012-07-26 15:38     ` rfflrccrd
     [not found]     ` <mailman.5668.1343316187.855.help-gnu-emacs@gnu.org>
2012-07-26 16:34       ` Raffaele Ricciardi
2012-07-26 16:34       ` Raffaele Ricciardi
2012-07-26 16:35       ` Raffaele Ricciardi
     [not found] <87d33vc0cq.fsf@zigzag.favinet>
     [not found] ` <m2k3reyhl1.fsf@gmail.com>
     [not found]   ` <87wqvesrq5.fsf@zigzag.favinet>
     [not found]     ` <m2k3rcmuci.fsf@gmail.com>
     [not found]       ` <87bocosf6d.fsf@zigzag.favinet>
     [not found]         ` <m2d2x4mdct.fsf@gmail.com>
     [not found]           ` <jwv1udjdfqc.fsf-monnier+emacs@gnu.org>
     [not found]             ` <m1y5frahyj.fsf@gmail.com>
     [not found]               ` <jwvfw1zbte6.fsf-monnier+emacs@gnu.org>
     [not found]                 ` <87obgipuhu.fsf@zigzag.favinet>
     [not found]                   ` <m28v7j5503.fsf@gmail.com>
     [not found]                     ` <m238xov1ah.fsf@gmail.com>
2013-02-21  6:31                       ` Thien-Thi Nguyen

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=87txwv6tnz.fsf@zigzag.favinet \
    --to=ttn@gnuvola.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rfflrccrd@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.
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).