From: Alex <agrambot@gmail.com>
To: emacs-orgmode@gnu.org
Cc: mail@nicolasgoaziou.fr
Subject: Re: Bug: orgtbl-self-insert-command does not overwrite whitespace [8.3.4 (8.3.4-50-g83e373-elpa @ /home/alex/.emacs.d/elpa/org-20160509/)]
Date: Fri, 20 May 2016 14:26:17 -0600 [thread overview]
Message-ID: <87futcbhna.fsf@gmail.com> (raw)
In-Reply-To: CAKGyR=SPUxQO+vC=xNEJhtTgpRz9Yvf4NWjjDQo77OH=nGkM2w@mail.gmail.com
Alex G <agrambot@gmail.com> writes:
>> > Backspace works as expected, however.
>> I'm afraid that as of org-20160516 on ELPA, backspace also does not
>> overwrite whitespace.
>
> Oh, it seems like backspace works fine in text modes like
> fundamental-mode and message-mode, but not prog-derived modes. I'd say
> that's another bug.
>
> A git bisect says that this commit by Bastien Guerry is the culprit:
> f0a64ab3b5c46c8c7b1c838de2ed20511357e43d
>
> Does anyone know why it also affects orgtbl-self-insert-command?
I believe I have figured out the issue for both problems:
a) orgtbl-self-insert-command wasn't updated along with
org-self-insert-command in the commit
73a5c27cc1751721344886e7518f20ff382265b5. Changing it accordingly fixes
the issue.
b) Backspace doesn't work in prog-derived modes as orgtbl-mode seems to
just remap delete-backward-char to orgtbl, but in prog modes backspace
is bound to backward-delete-char-untabify.
Perhaps something extra should be done about backspace in orgtbl-mode
instead of just a simple remapping?
next prev parent reply other threads:[~2016-05-20 22:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 3:15 Bug: orgtbl-self-insert-command does not overwrite whitespace [8.3.4 (8.3.4-50-g83e373-elpa @ /home/alex/.emacs.d/elpa/org-20160509/)] Alex G
2016-05-20 20:26 ` Alex [this message]
2016-05-21 12:42 ` Nicolas Goaziou
2016-05-21 18:15 ` Alex
2016-05-22 23:20 ` Nicolas Goaziou
-- strict thread matches above, loose matches on Subject: below --
2016-05-16 4:46 Alex
2016-05-18 18:19 ` Alex
2016-05-20 21:09 ` Nicolas Goaziou
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=87futcbhna.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).