emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-devel@gnu.org, emacs-orgmode@gnu.org, ingo.lohmar@posteo.net
Subject: Re: Emacs master, faces with :extend t let cursor vanish at EOL?!
Date: Wed, 23 Oct 2019 19:06:46 +0300	[thread overview]
Message-ID: <83h83zzbs9.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY2+EmyoOwwaVzOLU+MydOJ3etdSzo8sR1bG8Ef4B+Hn7Q@mail.gmail.com> (message from Kaushal Modi on Tue, 22 Oct 2019 16:17:04 -0400)

> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Tue, 22 Oct 2019 16:17:04 -0400
> Cc: emacs-org list <emacs-orgmode@gnu.org>,
>  Ingo Lohmar <ingo.lohmar@posteo.net> 

I suggest not to cross-post to 2 mailing lists.

> The issue occurs because of the new :extend feature for faces to extend till end of lines.
> 
> With that enabled, I have also seen that the cursor "hides" automatically only at end of lines inside the Org
> source blocks. i.e within
> 
> #+begin_src emacs-lisp
> (message "hello")X
> #+end_src
> 
> Above: X is where the cursor would be, but it would not be visible (with the :extend t added to the org-block
> face). The cursor would show up again on doing C-b i.e. bringing it to any column position other than the
> EOL.

I tried to reproduce this, but couldn't.  The OP says "often", so I
understand the problem is not 100% reproducible and the exact
situations in which it arises are not yet known.

So I suggest to find a reproducible recipe and then report it with
report-emacs-bug, so that the problem could be debugged and solved.

Thanks.

  reply	other threads:[~2019-10-23 16:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 19:52 Emacs master, faces with :extend t let cursor vanish at EOL?! Ingo Lohmar
2019-10-22 20:17 ` Kaushal Modi
2019-10-23 16:06   ` Eli Zaretskii [this message]
2020-02-04 10:07 ` Bastien
2020-02-04 19:27   ` Ingo Lohmar
2020-02-04 23:16     ` Bastien

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.orgmode.org/

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

  git send-email \
    --in-reply-to=83h83zzbs9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=ingo.lohmar@posteo.net \
    --cc=kaushal.modi@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/org-mode.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).