all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 18183@debbugs.gnu.org
Subject: bug#18183: 24.3; table-fixed-width-mode fails with kill/yank
Date: Mon, 7 Dec 2020 14:18:54 -0500	[thread overview]
Message-ID: <20201207191854.nqswve4vjk5q3ucz@E15-2016.optimum.net> (raw)
In-Reply-To: <87wnxtiubi.fsf@gnus.org>

Follow-up: The behavior of the table logic is different when not in an
org buffer. There seems to be confusion (possibly my confusion?) between
using table and org-table. In any event, the ability to mess up things
can itself be considered a bug.

Try this. In both an empty scratch buffer and an org buffer, perform M-x
table-insert. From within each table, press TAB in an attempt to
navigate table cells. It works only in the scratch buffer, and in the
org buffer, I get a message telling me "Use ‘C-c '’ to edit table.el
tables". In the scratch buffer, that is not necessary (and in fact is
undefined) , and you can edit the table directly. My fix (so far) works
only in the scratch buffer, not in the org buffer.

(TANGENT: Also, I see that when using the C-c ' method and canceling out
using C-c C-k, POINT is improperly restored to the beginning of the
table instead of the point at which C-c ' was invoked.)

When the table.el table is created in an org buffer, function
org-src--edit-element does the work, and I don't see it using any of the
code from table.el. This is asking for trouble in that any code
maintenance to table.el functionality (eg. any fix for this bug report)
needs to be done in two places, and in this case the code in each place
seems very different, so it really is double work.

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0





  parent reply	other threads:[~2020-12-07 19:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-03 18:15 bug#18183: 24.3; table-fixed-width-mode fails with kill/yank Boruch Baum
2020-12-04 11:29 ` Lars Ingebrigtsen
2020-12-06  9:06   ` Boruch Baum
2020-12-06 14:30     ` Lars Ingebrigtsen
2020-12-06 18:20       ` Boruch Baum
2020-12-07 13:53         ` Lars Ingebrigtsen
2020-12-07 14:06           ` Lars Ingebrigtsen
2020-12-07 17:36             ` Boruch Baum
2020-12-07 18:21             ` Boruch Baum
2020-12-08 13:39               ` Lars Ingebrigtsen
2020-12-07 19:18             ` Boruch Baum [this message]
2020-12-08  7:18             ` Boruch Baum
2020-12-08 13:40               ` Lars Ingebrigtsen
2020-12-08 13:56                 ` Boruch Baum
2020-12-08 13:59                   ` Lars Ingebrigtsen
2020-12-08 14:30                     ` Michael Albinus
2020-12-08 14:49                       ` Lars Ingebrigtsen
2020-12-10 10:37                         ` Bastien
2020-12-14  9:36                           ` Boruch Baum
2020-12-14 18:21                             ` Bastien
2020-12-14 19:32                               ` Boruch Baum
2020-12-08  7:46             ` Boruch Baum
2020-12-07 16:02           ` Boruch Baum
     [not found]           ` <20201209115145.oamb5hjjv65bw23s@E15-2016.optimum.net>
2020-12-09 11:53             ` Boruch Baum
2020-12-09 19:35               ` Lars Ingebrigtsen
2020-12-10  7:04                 ` Boruch Baum

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=20201207191854.nqswve4vjk5q3ucz@E15-2016.optimum.net \
    --to=boruch_baum@gmx.com \
    --cc=18183@debbugs.gnu.org \
    --cc=larsi@gnus.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.