unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: bug in forward-visible-line: Patch
Date: Fri, 23 May 2003 11:18:35 -0500 (CDT)	[thread overview]
Message-ID: <200305231618.h4NGIZI11628@eel.dms.auburn.edu> (raw)
In-Reply-To: <buohe7mcabu.fsf@mcspd15.ucom.lsi.nec.co.jp> (message from Miles Bader on 23 May 2003 17:54:13 +0900)

Miles Bader wrote:

   BTW, one problem with the name `visiblep' is that it could be confused
   to mean the same thing as `pos-visible-in-window-p'.  OTOH, I don't
   think I don't think `invisiblep' has this problem, since the term of
   `invisible' in emacs is strongly associated with the invisible property.

As I already pointed out in my reply to David Kastrup, I failed to
notice at the time when I proposed this function that there already
was a function, `line-move-invisible', with essentially the same
functionality as invisiblep.  This function currently works fine in
the absence of invisibility properties that are lists with two or more
elements, but malfunctions in the presence of such invisibility
properties.  This is a bug that should be fixed and can easily be
fixed by either using the new version of `line-move-invisible' which I
proposed in a later posting or by using the C functionality and making
`line-move-invisible' a primitive, as Stefan suggested.  The advantage
of the latter solution would be that if `line-move-invisible' used the
same function as display to determine visibility (Stefan seems to
suggest that this would be easy to implement), then it would actually
be "theoretically impossible" for `line-move-invisible' to get it
wrong.

Sincerely,

Luc.

  reply	other threads:[~2003-05-23 16:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22  4:43 bug in forward-visible-line: Patch Luc Teirlinck
2003-05-22 12:56 ` Stefan Monnier
2003-05-22 17:46   ` Luc Teirlinck
2003-05-22 21:40   ` Luc Teirlinck
2003-05-22 21:51     ` Stefan Monnier
2003-05-22 22:03       ` Luc Teirlinck
2003-05-22 22:23         ` Luc Teirlinck
2003-05-22 23:38       ` Luc Teirlinck
2003-05-23  0:03         ` Luc Teirlinck
2003-05-22 22:27     ` David Kastrup
2003-05-23  8:54       ` Miles Bader
2003-05-23 16:18         ` Luc Teirlinck [this message]
2003-05-24 23:19           ` Richard Stallman
2003-05-23 22:48         ` Richard Stallman
2003-05-23 15:50       ` Luc Teirlinck
2003-05-22 21:46   ` Luc Teirlinck

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=200305231618.h4NGIZI11628@eel.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@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.
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).