unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mohsin Kaleem <mohkale@kisara.moe>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48901@debbugs.gnu.org
Subject: bug#48901: [kisara.moe] Re: [kisara.moe] Re: bug#48901: [kisara.moe] 28.0.50; Support text-based fringe contents alongside bitmaps
Date: Tue, 15 Jun 2021 23:10:33 +0100	[thread overview]
Message-ID: <877diulqxy.fsf@kisara.moe> (raw)
In-Reply-To: <83y2blg59g.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> From: mohsin kaleem <mohkale@kisara.moe>
>> Date: Mon, 07 Jun 2021 14:30:23 +0100
>> 
>> 
>> This is more a feature request than a bug-report. At the moment the
>> recommended way to show extra information about certain lines in a
>> buffer is the fringe. This is done by defining a fringe-bitmap and then
>> having that render onto the fringe, however this is a graphical
>> only solution and terminal frames don't support this. Some packages such
>> as flycheck let you work around this by rendering what you would've
>> rendered on the frame, onto the margin which supports rendering regular
>> strings (alongside any other string-properties such as faces) that can
>> be visible in both terminal and GUI frames.
>> However as a solution that isn't ideal, for one margins weren't designed
>> for this purpose and for another there doesn't seem to be a way to set
>> the background or other properties of a margin to make it resemble the
>> fringe (in my case I'd like the background of the margin to match
>> the fringe background but only for the left margin where I will show the
>> fringe indicators). There's also the issue with interference between
>> this representation and other packages such as olivetti that use the
>> margin to center text.
>> I'd like to recommend we support rendering both text and bitmaps onto
>> the fringe, rendering nothing (or perhaps a block element) if a package
>> tries to render a bitmap on a terminal frame.
>
> Sorry, I don't understand: you begin by saying that fringe bitmaps
> have a disadvantage for TTY frames, and end by requesting a different
> features with the same disadvantage?  Or what did I miss?

Dear Eli,

Apologies I seem to have misunderstood the usage or implementation of
fringes vs. margins.
In retrospect the distinction isn't all that important.
I've tried using the margin based approach for the past few days and
the only issue I still have left is that there's no-way to specify the
default face for the margin (something akin to the `fringe' face).
Ideally I'd like to be able to do so separately for the left and right
margins (as I really only intend to use one of them), but otherwise the
rest of the issues I raised in my original email can be disregarded.

What are your thoughts on having a dedicated face for the margin?

Thank you,

---
Mohsin K.





  reply	other threads:[~2021-06-15 22:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 13:30 bug#48901: [kisara.moe] 28.0.50; Support text-based fringe contents alongside bitmaps mohsin kaleem
2021-06-07 13:42 ` Eli Zaretskii
2021-06-15 22:10   ` Mohsin Kaleem [this message]
2021-06-16 15:01     ` bug#48901: [kisara.moe] Re: [kisara.moe] " Eli Zaretskii
     [not found]       ` <875yxpla3r.fsf@kisara.moe>
2021-07-05 11:43         ` bug#48901: [kisara.moe] Re: [kisara.moe] " 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=877diulqxy.fsf@kisara.moe \
    --to=mohkale@kisara.moe \
    --cc=48901@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).