unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Werner LEMBERG <wl@gnu.org>
Cc: 3400@emacsbugs.donarmstrong.com
Subject: bug#3400: bug in add-text-properties
Date: Fri, 29 May 2009 11:01:55 -0400	[thread overview]
Message-ID: <jwvab4w551y.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <20090529.090050.266105248.wl@gnu.org> (Werner LEMBERG's message of "Fri, 29 May 2009 09:00:50 +0200 (CEST)")

> I disagree.  Whereever point is, it should report the character after
> point which is accessible (this is, visible).  Perhaps it makes sense
> to add a red warning message in the output of `C-x =' that point is
> not located right before the displayed character.

I think what would make most sense if for C-x = to notice such invisible
text and either give info about the whole invisible area, or prompt
which position within that area is actually desired.  In your case, you
want info about the visible char, but I most often use C-x =
specifically to get info about the part I can't see.

> If we had a small line instead of a blinking, block-like cursor (as it
> is used with, say, OpenOffice), I could accept your argumentation.

That can be configured via `cursor-type'.

>> if you're not 200% sure you absolutely need `intangible', then don't
>> use it.  It's a nasty beast.
> Indeed.  But for my particular needs -- filtering out some lines, then
> searching and editing the visible ones only without accidentally
> editing invisible stuff, it seems that `intangible' is still
> necessary, and probably will stay so.

Your call, but you've been warned.  I'd still recommend you first try it
without `intangible'.


        Stefan






  parent reply	other threads:[~2009-05-29 15:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27  5:26 bug#3400: bug in add-text-properties Werner LEMBERG
2009-05-28 15:15 ` martin rudalics
2009-05-28 16:26   ` Werner LEMBERG
2009-05-28 17:12     ` martin rudalics
2009-05-28 18:28     ` Stefan Monnier
2009-05-28 21:48       ` Werner LEMBERG
2009-05-29  2:05         ` Stefan Monnier
2009-05-29  7:00           ` Werner LEMBERG
2009-05-29 13:24             ` Lennart Borgman
2009-05-29 14:51               ` Drew Adams
2009-05-29 15:01             ` Stefan Monnier [this message]
2009-05-29 15:20               ` Werner LEMBERG
2009-05-29 16:08                 ` Stefan Monnier
2009-05-29 16:47                   ` martin rudalics
2009-05-30  5:51                     ` Werner LEMBERG
2009-05-30 10:12                       ` martin rudalics
2009-05-30  7:01                   ` Werner LEMBERG
2009-05-30 10:01                     ` Stephen Berman
2016-07-27 22:07                       ` Nicolas Petton
2016-07-29  2:26                         ` npostavs
2022-04-22 12:59                           ` bug#3400: Let C-x = show info about visible and invisible text near point Lars Ingebrigtsen

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=jwvab4w551y.fsf-monnier+emacsbugreports@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=3400@emacsbugs.donarmstrong.com \
    --cc=wl@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).