all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Better ways to inspect text properties?
Date: Thu, 27 Oct 2022 08:46:47 +0300	[thread overview]
Message-ID: <83h6zpn7i0.fsf@gnu.org> (raw)
In-Reply-To: <CADs++6jxk1NGo54LEszDP44P3vjhAyQMoYmwqaiZC+3Vih5d0g@mail.gmail.com> (message from Eduardo Ochs on Wed, 26 Oct 2022 20:19:59 -0300)

> From: Eduardo Ochs <eduardoochs@gmail.com>
> Date: Wed, 26 Oct 2022 20:19:59 -0300
> 
> suppose that I create a file /tmp/foo.org whose contents are just
> this:
> 
>   a[[http://b/][c]]d
> 
> and then I visit /tmp/foo.org, and I pretty-print the result of
> (buffer-substring (point-min) (point-max)). The result is:
> 
> #("a[[http://b/][c]]d\n" 0 1
>   (fontified t)
>   1 13
>   (face org-link font-lock-multiline t keymap
>         (keymap
>          (follow-link . mouse-face)
>          (mouse-3 . org-find-file-at-mouse)
>          (mouse-2 . org-open-at-mouse))
>         mouse-face highlight invisible org-link htmlize-link
>         (:uri "http://b/")
>         help-echo "LINK: http://b/" fontified t)
>   13 14
>   (face org-link font-lock-multiline t keymap
>         (keymap
>          (follow-link . mouse-face)
>          (mouse-3 . org-find-file-at-mouse)
>          (mouse-2 . org-open-at-mouse))
>         mouse-face highlight invisible org-link rear-nonsticky
>         (mouse-face highlight keymap invisible intangible help-echo
> org-linked-text htmlize-link)
>         htmlize-link
>         (:uri "http://b/")
>         help-echo "LINK: http://b/" fontified t)
>   14 15
>   (font-lock-multiline t keymap
>                        (keymap
>                         (follow-link . mouse-face)
>                         (mouse-3 . org-find-file-at-mouse)
>                         (mouse-2 . org-open-at-mouse))
>                        mouse-face highlight face org-link rear-nonsticky
>                        (mouse-face highlight keymap invisible
> intangible help-echo org-linked-text htmlize-link)
>                        htmlize-link
>                        (:uri "http://b/")
>                        help-echo "LINK: http://b/" fontified t)
>   15 16
>   (font-lock-multiline t keymap
>                        (keymap
>                         (follow-link . mouse-face)
>                         (mouse-3 . org-find-file-at-mouse)
>                         (mouse-2 . org-open-at-mouse))
>                        mouse-face highlight invisible org-link face
> org-link htmlize-link
>                        (:uri "http://b/")
>                        help-echo "LINK: http://b/" fontified t)
>   16 17
>   (font-lock-multiline t keymap
>                        (keymap
>                         (follow-link . mouse-face)
>                         (mouse-3 . org-find-file-at-mouse)
>                         (mouse-2 . org-open-at-mouse))
>                        mouse-face highlight invisible org-link face
> org-link htmlize-link
>                        (:uri "http://b/")
>                        help-echo "LINK: http://b/" rear-nonsticky
>                        (mouse-face highlight keymap invisible
> intangible help-echo org-linked-text htmlize-link)
>                        fontified t)
>   17 18
>   (rear-nonsticky t fontified t)
>   18 19
>   (fontified t))
> 
> This is not very human-friendly (to me). Can you recommend me ways to
> optimize that output?

Please tell which part(s) is/are not very human-friendly in the above.
Otherwise it's hard to suggest improvements, because to me the above
is quite friendly and easy to read and understand.



  parent reply	other threads:[~2022-10-27  5:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 23:19 Better ways to inspect text properties? Eduardo Ochs
2022-10-27  2:54 ` Emanuel Berg
2022-10-27  5:46 ` Eli Zaretskii [this message]
2022-10-27  6:45   ` Eduardo Ochs
2022-10-27  7:25     ` Emanuel Berg
2022-10-27 14:03   ` Eduardo Ochs
2022-10-27 15:05     ` Emanuel Berg
2022-10-28 15:19       ` Eduardo Ochs
2022-10-29 23:46 ` Samuel Wales
2022-10-30  1:08   ` Eduardo Ochs
2022-10-30  4:51     ` Samuel Wales

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83h6zpn7i0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.