all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Davide Masserut <dm@mssdvd.com>
Cc: 54843@debbugs.gnu.org
Subject: bug#54843: 29.0.50; rcirc-omit-mode hiding the overlay arrow
Date: Fri, 22 Apr 2022 10:20:28 +0000	[thread overview]
Message-ID: <87sfq5to5v.fsf@posteo.net> (raw)
In-Reply-To: <87o80vg3b4.fsf@mssdvd.com> (Davide Masserut's message of "Wed, 20 Apr 2022 17:52:31 +0200")

Davide Masserut <dm@mssdvd.com> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Could you test if the following improves the situation:
>
> I'm sorry but that doesn't work.
>
>> I am not certain, but my intuition is that the issue should be fixed
>> somewhere around here.
>
> Could the problem be in the C code (xdisp.c ?) that handles the arrow?
> The code in rcirc.el looks quite straightforward to me.

I don't think so, the arrow is behaving just the way it should.
E.g. try setting it in some Elisp file with outline-minor-mode enabled.
If you fold the section the arrow marker is placed within, it disappears
from the fringe.  It could be argued that this shouldn't be the case,
but I think that for rcirc what we actually want is to ensure that the
marker is always placed so that it isn't affected by rcirc-omit-mode.

-- 
	Philip Kaludercic





      reply	other threads:[~2022-04-22 10:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10 19:12 bug#54843: 29.0.50; rcirc-omit-mode hiding the overlay arrow Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-11 15:47 ` Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-20 14:56 ` Philip Kaludercic
2022-04-20 15:52   ` Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-22 10:20     ` Philip Kaludercic [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

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

  git send-email \
    --in-reply-to=87sfq5to5v.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=54843@debbugs.gnu.org \
    --cc=dm@mssdvd.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 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.