all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Van Ly <van.ly@sdf.org>, Eli Zaretskii <eliz@gnu.org>,
	57161@debbugs.gnu.org
Subject: bug#57161: 28.1.91; two column windows merge leaves 2nd column window showing
Date: Tue, 16 Aug 2022 03:24:56 +0200	[thread overview]
Message-ID: <87lerpask7.fsf@web.de> (raw)
In-Reply-To: <87mtc8ib7m.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 13 Aug 2022 14:23:25 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> I've never used this mode before, and I'm kinda flabbergasted that
> something as esoteric as this is bound to <f2> by default.

That whole 2C library is a bit esoteric.

If you edit the remaining narrow window and try to merge (again), the
second column is actually doubled in the original buffer.  That narrow
window is useless, it's even harmful!

BTW, I tried a buffer with this contents:

1 11
2 22
3 33

If you place the cursor before the separator (space char) instead of
after it, C-x 6 s infloops.  Not nice.


I then though: Do these narrow windows maybe suggest that one can
iterate 2C processing to conveniently edit more than two columns?  But
no, that just messes the original buffer if you try.


So this bug report is one detail.  The whole library doesn't look very
intuitive and user friendly.  Maybe 0.02 users in the world understand
it and make good use of it.  Or maybe it has never been a good package.

I have tried to use it multiple times and was always disappointed about
the experience.  It gives an unfinished impression.  Seems not good that
it occupies F2, and also not good that it's built in.

Michael.






  parent reply	other threads:[~2022-08-16  1:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12 17:55 bug#57161: 28.1.91; two column windows merge leaves 2nd column window showing Van Ly
2022-08-12 19:00 ` Eli Zaretskii
2022-08-12 19:10   ` Van Ly
2022-08-12 19:23     ` Eli Zaretskii
2022-08-12 19:43       ` Van Ly
2022-08-12 19:45         ` Eli Zaretskii
2022-08-13 12:23           ` Lars Ingebrigtsen
2022-08-13 12:47             ` Stefan Kangas
2022-08-13 14:21               ` Eli Zaretskii
2022-08-14 13:11               ` Van Ly
2022-08-15  5:58               ` Lars Ingebrigtsen
2022-08-15 11:36                 ` Eli Zaretskii
2022-08-13 14:15             ` Eli Zaretskii
2022-08-15  5:56               ` Lars Ingebrigtsen
2022-08-16  1:24             ` Michael Heerdegen [this message]
2022-08-16 11:11               ` Eli Zaretskii
2022-08-16 22:07                 ` Michael Heerdegen
2022-08-17  0:35                   ` Van Ly
2022-08-17 11:04                     ` Lars Ingebrigtsen
2022-08-14 13:04           ` Van Ly

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=87lerpask7.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=57161@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=van.ly@sdf.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 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.