From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: 28771@debbugs.gnu.org
Subject: bug#28771: 26.0.60; A couple space display property feature requests
Date: Tue, 10 Oct 2017 09:47:48 +0300 [thread overview]
Message-ID: <83efqbqz1n.fsf@gnu.org> (raw)
In-Reply-To: <87fuarc0px.fsf@gmail.com> (message from Alex on Mon, 09 Oct 2017 18:20:42 -0600)
> From: Alex <agrambot@gmail.com>
> Date: Mon, 09 Oct 2017 18:20:42 -0600
>
> I've branched this out from the following thread instead of posting it
> there:
> https://lists.gnu.org/archive/html/help-gnu-emacs/2017-10/msg00037.html
Sorry, I've somehow missed that. I answered there now.
> Here's a few features that would be nice for the pixel-specified space
> properties.
>
> 1. Specifying the pixel width to the left/center/right of the text area.
> This is helpful (I believe it's necessary if I want it to be robust)
> when one wants to pad either side of a string with the same number of
> pixels and the left side uses (:align-to 0).
>
> I could use (:width (+ left-fringe left-margin)) for the right
> padding, but this doesn't take into account line-number display, as
> well as the scroll-bar width (if it's on the left).
>
> 2. Specifying the pixel position relative to the left or right edge of
> the window. The right edge of the window currently may be the right
> edge of the right fringe or the scroll bar, depending on what side it
> is on. Also, just in the case that in the future the
> fringe/scroll-bar may not be the outermost elements, there should be
> a way to explicitly specify one of the edges.
These two requests are no in the original message, and I admit I don't
really understand the situations they describe. Can you elaborate
about them, preferably with an example that shows what is currently
possible and an explanation why the current capabilities are
insufficient? (Yes, I've seen the patches you propose, but I still
would like to understand the problems better.)
> 3. Following from "1." and the help-gnu-emacs thread, it would be nice
> if there was a display property that allowed you to pad a string on
> both sides with a pixel-specified space instead of surrounding it
> with 2 pixel-specified spaces.
I replied on help-gnu-emacs. In a nutshell, the 'space' display spec
is a replacing spec, so it cannot be easily used on non-space text.
You could probably have a before-string whose value is a space with
the 'space' display spec, if that makes any difference. Or you could
use the space-width spec, as described on help-gnu-emacs.
Thanks.
next prev parent reply other threads:[~2017-10-10 6:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 0:20 bug#28771: 26.0.60; A couple space display property feature requests Alex
2017-10-10 2:02 ` Alex
2017-10-10 6:47 ` Eli Zaretskii [this message]
2017-10-10 17:54 ` Alex
2017-10-10 19:12 ` Eli Zaretskii
2017-10-10 21:27 ` Alex
2017-10-11 12:59 ` Eli Zaretskii
2017-10-11 15:37 ` Eli Zaretskii
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=83efqbqz1n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28771@debbugs.gnu.org \
--cc=agrambot@gmail.com \
/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).