unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: rms@gnu.org, monnier+gnu/emacs/pretest@rum.cs.yale.edu,
	monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org,
	emacs-pretest-bug@gnu.org
Subject: Re: info invisible changes
Date: 12 Nov 2002 11:59:14 +0100	[thread overview]
Message-ID: <5xbs4v9hq5.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <buobs4vywey.fsf@mcspd15.ucom.lsi.nec.co.jp>

Miles Bader <miles@lsi.nec.co.jp> writes:

> storm@cua.dk (Kim F. Storm) writes:
> > Is someone working on fixing fill.el to deal with these text properties?
> > 
> > If not, should the code in fill.el be modified in general to deal with
> > these properties, or can it be done by adding another type of filling
> > specifically for this type of mangled text?  Please advise!
> 
> I suspect that this is a somewhat hard problem.  Of course, by simply
> modifying the text directly (using properties where necessary to hold
> out-of-band info) instead of using invisible/display properties, the
> problem just goes away entirely.  ...and if you're gonna modify the
> buffer by filling anyway...

True!

However, I think that fill should at least be aware of 'invisible
properties (which should be doable), while dealing with 'display
properties is harder and less important (for my purpose at least).

If we fixed the 'invisible problem, then I could simply insert the
"see" into the buffer rather than using a 'display property and make
the *note part invisible to allow the Info navigation to remain
unchanged.

BTW, I was asked to implement image support in Info mode.  Has anyone
done some thoughts on how that should work [what kind of reference
would be in the info buffer, and where would the image be stored?]

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2002-11-12 10:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01  8:04 info invisible changes Miles Bader
     [not found] ` <200211011623.gA1GNAL03601@rum.cs.yale.edu>
2002-11-05  4:08   ` Miles Bader
2002-11-05 18:49     ` Stefan Monnier
2002-11-07  4:49       ` Richard Stallman
2002-11-05 23:57     ` Kim F. Storm
2002-11-06  9:51       ` Miles Bader
2002-11-06 12:46         ` Kim F. Storm
2002-11-06 12:30           ` Miles Bader
2002-11-06 15:11         ` Stefan Monnier
2002-11-06 16:32           ` Miles Bader
2002-11-07 15:08           ` Richard Stallman
2002-11-12 10:11             ` Kim F. Storm
2002-11-12  9:22               ` Miles Bader
2002-11-12 10:59                 ` Kim F. Storm [this message]
2002-11-12 17:28                   ` Robert J. Chassell
2002-11-13 14:37                     ` Kim F. Storm
2002-11-13 18:20                       ` Robert J. Chassell
2002-11-14 12:17                         ` Richard Stallman
2002-11-14 21:38                           ` Kim F. Storm
2002-11-12 18:49               ` Stefan Monnier
2002-11-13 23:31                 ` Kim F. Storm
2002-11-14  0:39                 ` Kim F. Storm
2002-11-14  4:09               ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2002-11-14 13:57 Karl Berry

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=5xbs4v9hq5.fsf@kfs2.cua.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=monnier+gnu/emacs/pretest@rum.cs.yale.edu \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=rms@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).