unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 40856@debbugs.gnu.org
Subject: bug#40856: Feature request: support arbitrary propertized strings in wrap-prefix specifications
Date: Sun, 26 Apr 2020 14:25:32 -0400	[thread overview]
Message-ID: <16bbfd22-acce-66ce-28ff-9cbbac95cabb@gmail.com> (raw)
In-Reply-To: <83blne5eir.fsf@gnu.org>

On 26/04/2020 13.43, Eli Zaretskii wrote:
>> Cc: 40856@debbugs.gnu.org
>> From: Clément Pit-Claudel <cpitclaudel@gmail.com>
>> Date: Sun, 26 Apr 2020 13:23:15 -0400
>>
>> What I meant to say is that if it's cheap enough to draw this:
>>
>> ⟝ bbbbbbbbbbb
>> ⟝ bbbbbbbbbbb
>> ⟝ bbbbbbbbbbb
>> ⟝ bbbbbbbbbbb
>> ⟝ bbbbbbbbbbb
>>
>> (where "⟝" is a wrap-prefix on all lines but the first)
>>
>> … then it should be cheap enough to draw this:
>>
>> ⟝ bbbbbbbbbbb
>>    bbbbbbbbbbb
>>    bbbbbbbbbbb
>>    bbbbbbbbbbb
>>    bbbbbbbbbbb
>>
>> where the indentation is a specified space as wide as "⟝".
> 
> And what I meant is that the second one is more expensive, because for
> each line but the first, Emacs will have to produce glyphs both for
> "⟝" (to obtain its width) and for the stretch of space.

Got it. I assumed that producing a stretch of space was cheap.





      reply	other threads:[~2020-04-26 18:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-25 21:24 bug#40856: Feature request: support arbitrary propertized strings in wrap-prefix specifications Clément Pit-Claudel
2020-04-26 15:33 ` Eli Zaretskii
2020-04-26 16:09   ` Clément Pit-Claudel
2020-04-26 17:07     ` Eli Zaretskii
2020-04-26 17:23       ` Clément Pit-Claudel
2020-04-26 17:43         ` Eli Zaretskii
2020-04-26 18:25           ` Clément Pit-Claudel [this message]

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=16bbfd22-acce-66ce-28ff-9cbbac95cabb@gmail.com \
    --to=cpitclaudel@gmail.com \
    --cc=40856@debbugs.gnu.org \
    --cc=eliz@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).