From: Luca Ferrari <fluca1978@gmail.com>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: emacs starts writing in reverse order
Date: Sat, 6 Feb 2021 15:49:29 +0100 [thread overview]
Message-ID: <CAKoxK+78V147KWm0PvJ8pEi5yoOVhwaNmAde-OaxsZ0_6Wqa+A@mail.gmail.com> (raw)
In-Reply-To: <CAKoxK+40+iZuzCpOraZY95tWbDHpO+yHDfEp48iR+w=F3dviWw@mail.gmail.com>
On Sat, Feb 6, 2021 at 1:55 PM Luca Ferrari <fluca1978@gmail.com> wrote:
>
> What is happening? I suspect is something related to bidirectional
> editing, could it be?
In particular I can see that this happens when I label the source code
snippet with a language. If I enter a block without the language I'm
able to edit it inline and nothing strange happens, but if I mark the
block of code such as 'sql' then Emacs does not allow me to edit it
inline,. I have to switch to an indirect buffer and when I return from
such buffer Emacs seems to be screwed up.
Luca
prev parent reply other threads:[~2021-02-06 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 12:55 emacs starts writing in reverse order Luca Ferrari
2021-02-06 13:14 ` Eli Zaretskii
2021-02-06 13:19 ` Eli Zaretskii
2021-02-06 14:49 ` Luca Ferrari [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=CAKoxK+78V147KWm0PvJ8pEi5yoOVhwaNmAde-OaxsZ0_6Wqa+A@mail.gmail.com \
--to=fluca1978@gmail.com \
--cc=help-gnu-emacs@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.
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).