From: Uwe Brauer <oub@mat.ucm.es>
To: Ruijie Yu <ruijie@netyu.xyz>
Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-orgmode@gnu.org
Subject: Re: bi-lingual text
Date: Sun, 12 Mar 2023 08:49:04 +0100 [thread overview]
Message-ID: <87edpubea7.fsf@mat.ucm.es> (raw)
In-Reply-To: sdv8rg2fp20.fsf@fw.net.yu
[-- Attachment #1: Type: text/plain, Size: 2396 bytes --]
> Uwe Brauer <oub@mat.ucm.es> writes:
Hi
> `2C-mode' might be what you want. Be warned, though, that it might be
> confusing when first using it, and that there might be missing
> information since I have just begun to explore it because of your
> message.
> (Also, there doesn't seem to be much documentation on 2C at all, except
> for in its source code?)
> Two caveats:
> 1. Whenever you split using <F2> s (M-x 2C-split RET), the split will
> happen at the current column, while *consuming* the previous char. You
> can experiment with the command and see what I mean.
Thanks,
> 2. Currently, when you use <F2> 1 (M-x 2C-merge RET), the associated
> buffer is only minimised at the right side. If a user wants to reuse
> the same assoc buffer when typing <F2> s again, the user first has to
> hide the buffer (at least in my experience).
> What I tried:
> In "bilingual.org", type the following:
> * Bilingual
> Hello world.|!
> Good night.
> Here, "!" its not a character but means the cursor; "|" is the character
> before point, and will be used as the separator for the buffers.
> Then, run <F2> s (M-x 2C-split RET).
> There should now be two buffers side-by-side. Go to the right buffer
> and start typing.
> Bienvenue tout le monde.
> Bonne nuit.
> Then (in either buffer) run <F2> 1 (M-x 2C-merge RET). Now the
> remaining buffer should read:
> * Bilingual
> Hello world. |Bienvenue tout le monde.
> Good night. |Bonne nuit.
> Hopefully this helps -- not only for you, but for those who, like me an
> hour ago, accidentally discovered 2C-mode but did not understand how to
> use it.
Very nice, I played around with a paragraph that contained longer
sentences. So one has however to be it careful with the length of the
lines. It might be wise to set fill column to something like 60.
But thanks for pointing this out to me, it remains me a bit of
scroll-all-mode, but this is definitely much nicer and more suited.
Uwe Brauer
--
Warning: Content may be disturbing to some audiences
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military.
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine.
https://addons.thunderbird.net/en-US/thunderbird/addon/gmail-conversation-view/
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
prev parent reply other threads:[~2023-03-12 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 18:28 bi-lingual text Uwe Brauer
2023-03-12 6:07 ` Ruijie Yu via General discussions about Org-mode.
2023-03-12 7:49 ` Uwe Brauer [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edpubea7.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-orgmode@gnu.org \
--cc=ruijie@netyu.xyz \
/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).