From: Merciadri Luca <Luca.Merciadri@student.ulg.ac.be>
To: help-gnu-emacs@gnu.org
Subject: Re: Unmatched parenthesis. Okay, but if this is a smiley?
Date: Sat, 26 Jun 2010 19:18:26 +0200 [thread overview]
Message-ID: <874ogpg1b1.fsf@merciadriluca-station.MERCIADRILUCA> (raw)
In-Reply-To: 87aaqhrj14.fsf@kuiper.lan.informatimago.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
pjb@informatimago.com (Pascal J. Bourguignon) writes:
> Merciadri Luca <Luca.Merciadri@student.ulg.ac.be> writes:
>
>> pjb@informatimago.com (Pascal J. Bourguignon) writes:
>>
>>> Merciadri Luca <Luca.Merciadri@student.ulg.ac.be> writes:
>>>> It sometimes happens to use smileys (e.g. in e-mails, through
>>>> e.g. Gnus) in emacs. The problem is that it always gives me `Unmatched
>>>> parenthesis' in the minibuffer. Is there some .el script to solve this
>>>> `issue?'
>>>
>>> Check the mode. In message buffers, no parenthesis checking should be done.
>> Could you be more explicit? Thanks.
>
> The behavior you describe is not 'normal'. When you have a normal
> GNUS message buffer, like the one I'm typing right now ;-), you can
> insert any number of unbalanced parentheses because no checking is
> done.
>
> Here are the major-mode and currently active minor modes in my GNUS message buffer:
>
> major-mode --> message-mode
>
> (defun current-minor-modes (&optional buffer)
> "The list of the minor modes currently active in the buffer (or current buffer)."
> (let ((result '()))
> (with-current-buffer (or buffer (current-buffer))
> (dolist (mode minor-mode-list result)
> (when (and (boundp mode) (symbol-value mode))
> (push mode result))))))
>
> (current-minor-modes) --> (abbrev-mode transient-mark-mode
> line-number-mode auto-compression-mode
> auto-encryption-mode
> unify-8859-on-encoding-mode
> unify-8859-on-decoding-mode
> blink-cursor-mode font-lock-mode
> global-font-lock-mode
> file-name-shadow-mode mouse-wheel-mode
> tooltip-mode shell-dirtrack-mode
> auto-image-file-mode display-time-mode
> mml-mode)
>
> So you must have some hook or some other minor mode configured that
> activates such mismatched parentheses dectection and signaling an
> error.
Very probable. I use built-in code-syntax helper (for C, Java, etc.),
which checks parentheses, etc., but it should not be launched if the
file is not such a code file, should it?
- --
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
- --
If it's too good to be true, then it probably is.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iEYEARECAAYFAkwmNmEACgkQM0LLzLt8MhztqgCgmglLBm2w197R4GzkVyUnRQK1
KiwAoIwmt5MJkT7ZqRNjsKVBFv99DcVb
=kRIb
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-06-26 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87eifunap5.fsf@merciadriluca-station.MERCIADRILUCA>
2010-06-25 20:12 ` Unmatched parenthesis. Okay, but if this is a smiley? Pascal J. Bourguignon
[not found] ` <87k4pmqm6a.fsf@merciadriluca-station.MERCIADRILUCA>
2010-06-26 14:00 ` Pascal J. Bourguignon
2010-06-26 17:18 ` Merciadri Luca [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=874ogpg1b1.fsf@merciadriluca-station.MERCIADRILUCA \
--to=luca.merciadri@student.ulg.ac.be \
--cc=help-gnu-emacs@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.
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).