From: Carsten Dominik <email@example.com>
Cc: firstname.lastname@example.org, Paul Stansell <email@example.com>
Subject: Re: Bug: spreadsheet [7.7]
Date: Sun, 16 Oct 2011 13:39:48 +0200 [thread overview]
Message-ID: <B7C025B2-7818-4AF9-9D00-F2A08825477A@gmail.com> (raw)
On 2.10.2011, at 18:35, Nick Dokos wrote:
> Paul Stansell <firstname.lastname@example.org> wrote:
>> To reproduce the bug do the following:
>> Edit this file with emacs orgmode.
>> Place the cursor in the small table below and type C-c } to toggle on the
>> display a labelled grid giving the cell references.
>> Change the c=1 in the CONSTANTS line to c=2 and refresh this line with C-c
>> Put the cursor on the TBLFM line and refresh this line with C-c C-c.
>> An "I*1" appears above the table which should not appear and can't be
>> removed with the usual emacs commands.
>> | 1 |
>> #+TBLFM: $1=$c
>> #+CONSTANTS: c=1
> Yup: I can reproduce it too. Toggling the table coordinates inserts
> overlays and apparently something is out of sync and that particular
> overlay does not get deleted appropriately.
> You can check that there is an overlay there by placing the cursor
> right after it and evaluating
> (overlay-at (point))
> which should return a list of overlays at point. Assuming that you
> get a non-nil result with just that one overlay in the list, you can
> delete it with
> (delete-overlay (car (overlay-at (point))))
> Haven't figured out why it gets left over though.
I have made a brute force solution for this issue, pressing
C-c C-c on a #+ line will remove these overlays first.
Not nice, but it helps with this problem.
next prev parent reply other threads:[~2011-10-16 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-02 14:14 Bug: spreadsheet [7.7] Paul Stansell
2011-10-02 16:35 ` Nick Dokos
2011-10-16 11:39 ` Carsten Dominik [this message]
2011-10-16 14:40 ` Christian Moe
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).