From: "ken manheimer" <ken.manheimer@gmail.com>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
Cc: Kenichi Handa <handa@m17n.org>, Emacs Devel <emacs-devel@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Carsten Dominik <dominik@science.uva.nl>
Subject: Re: Add a function to test for invisible characters?
Date: Mon, 23 Jun 2008 16:21:29 -0400 [thread overview]
Message-ID: <2cd46e7f0806231321s702ed051r7efbe7c2963ef651@mail.gmail.com> (raw)
In-Reply-To: <485FFAD3.4010007@gmail.com>
On Mon, Jun 23, 2008 at 3:34 PM, Lennart Borgman (gmail)
<lennart.borgman@gmail.com> wrote:
> Lennart Borgman (gmail) wrote:
>>
>> Stefan Monnier wrote:
>>>>
>>>> I asked some time ago if a function to test if a character is
>>>> invisible. I think nothing has been done to this, or am I mistaken?
>>>
>>> It's called `invisible-p'.
>>
>>
>> Ah, thanks, there it is. Very nice.
>
> I grepped for "'invisible" to see if there were any places where this
> should/could be used. In some cases I do not understand what should be done.
> For example allout.el has
>
> (defsubst allout-hidden-p (&optional pos)
> "Non-nil if the character after point is invisible."
> (eq (get-char-property (or pos (point)) 'invisible) 'allout))
>
> However here are a some that I think maybe should use invisible-p or perhaps
> test a little bit more careful:
> [...]
i think you inferred correctly that i deliberately didn't use
invisible-p. that's because i needed to detect points that are hidden
specifically by allout, not for some other purpose. i guess i the
docstring should be clearer about that.
--
ken
http://myriadicity.net
next prev parent reply other threads:[~2008-06-23 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 15:33 Add a function to test for invisible characters? Lennart Borgman (gmail)
2008-06-23 18:50 ` Stefan Monnier
2008-06-23 18:54 ` Lennart Borgman (gmail)
2008-06-23 19:34 ` Lennart Borgman (gmail)
2008-06-23 20:21 ` ken manheimer [this message]
2008-06-24 13:39 ` T. V. Raman
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=2cd46e7f0806231321s702ed051r7efbe7c2963ef651@mail.gmail.com \
--to=ken.manheimer@gmail.com \
--cc=dominik@science.uva.nl \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=lennart.borgman@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).