From: Ulf Jasper <ulf.jasper@web.de>
To: raman@users.sf.net
Cc: emacs-pretest-bug@gnu.org, monnier@iro.umontreal.ca
Subject: Re: 22.1.50; newsticker and buffer-invisibility-spec:
Date: Sat, 25 Aug 2007 17:32:04 +0200 [thread overview]
Message-ID: <87fy277hqj.fsf@web.de> (raw)
In-Reply-To: <87odgzz9f5.fsf@web.de> (Ulf Jasper's message of "Wed\, 22 Aug 2007 20\:55\:10 +0200")
> "T. V. Raman" <raman@users.sf.net> writes:
>> Its bizarre use of buffer-invisibility-spec was triggering a bug
>> in the context of Emacspeak. I've fixed my code to work around it
>> -- but it would be good to get newsticker fixed up to match
>> emacs' use of buffer-invisibility-spec.
Newsticker sets `buffer-invisibility-spec´ to a list like '(ATOM1
ATOM2 ... ATOMn). It also sets the 'invisible text property to a list
like ´(ATOMi ... ATOMk). If I understand the Elisp manual (for GNU
Emacs 22.1) correctly,
----------------------------------------------------------------------
-- Variable: buffer-invisibility-spec
This variable specifies which kinds of `invisible' properties
actually make a character invisible. Setting this variable makes
it buffer-local.
`t'
A character is invisible if its `invisible' property is
non-`nil'. This is the default.
a list
Each element of the list specifies a criterion for
invisibility; if a character's `invisible' property fits any
one of these criteria, the character is invisible. The list
can have two kinds of elements:
`ATOM'
A character is invisible if its `invisible' property
value is ATOM or if it is a list with ATOM as a member.
`(ATOM . t)'
A character is invisible if its `invisible' property
value is ATOM or if it is a list with ATOM as a member.
Moreover, if this character is at the end of a line and
is followed by a visible newline, it displays an
ellipsis.
----------------------------------------------------------------------
the usage of `buffer-invisibility-spec' and the 'invisible text
property is valid. In which case it is not "bizarre", not even "odd".
Ulf
--
ANMERKUNG: Zwecks nicht notwendiges zu vermeiden verzögert und
Komplikationen, erinnern bitte sich deinen Hinweis und Kuponzahlen in
allen zu veranschlagen Korrespondenzen mit deinem Ansprüche Direktor.
next prev parent reply other threads:[~2007-08-25 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 13:28 22.1.50; newsticker and buffer-invisibility-spec: raman
2007-08-20 14:20 ` Tassilo Horn
2007-08-22 10:47 ` T. V. Raman
2007-08-20 14:27 ` Stefan Monnier
2007-08-22 10:48 ` T. V. Raman
2007-08-22 18:55 ` Ulf Jasper
2007-08-25 15:32 ` Ulf Jasper [this message]
2007-08-25 19:49 ` Stefan Monnier
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=87fy277hqj.fsf@web.de \
--to=ulf.jasper@web.de \
--cc=emacs-pretest-bug@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=raman@users.sf.net \
/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).