emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Torsten Wagner <torsten.wagner@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Bastien <bzg@altern.org>, Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Problem: Moving rows in a table changes vsum start and end
Date: Sun, 30 Sep 2012 16:30:55 +0900	[thread overview]
Message-ID: <CAPaq-gO_xKbNm9Tiqv5v=yWVnp22mM-czi=mByJ0CRmEvPGi4w@mail.gmail.com> (raw)
In-Reply-To: <4A0ED057-7239-4D88-8537-583AC1367721@gmail.com>

Hi Carsten,

> Thorsten, if you look at the manual, there are ways to write this limits of vsum etc in a way that they are relative to the table boundaries or to horizontal lines.  This is robust agains changes of rows.

Yes I know, thanks for pointing to it. It is just an dangerous culprit
since people might not be aware of the fact that the formular changes
along with row-moving operations.  Esp. if you use vsum or other range
based operations (with a start and end), one might expect that there
should be no change.

I can only speak for myself, however, as great as it is to use
org-tables, I always have this little paranoid fear that certain cells
did not get updated correctly, might it be due to wrong inputs from my
side or because of a hidden bug. For really critical parts, esp.
during the set-up of a new table, I find myself checking the numbers
by hand again to make sure its going to be ok.
Another problem I faced sometimes is the fact that after a while I
forgot that a certain cell is addressed by a formular. I do changes by
hand and just the next press of C-u C-c C-c might overwrite them
accidentally without my notice.

Having overlays or any sort of highlighting might be very helpful (and
as the nature of emacs, people might just decide to turn them on and
off if they get annoyed).
I was thinking of:
+ Mark all cells/numbers which depend or are part of a formular (kind
what we have already in the formular editor but for all and every
+ Mark all cells which were updated by  C-u C-c C-c (as the above but
in addition being now different compared to the previous result)
+ Mark the parts of the formulars which using the cell in which the
pointer is currently placed (reverse compared to the already existing
formular highlighting)
+ Mark all cells which have by formulars some relation to the cell in
which the pointer is currently placed (use two colors to indicate
inputs and outputs)

Those would give me a much more confidence, e.g., that all the fields
are updated correctly, that I did not overwrite by accident an
calculated value and it would help me to understand quickly the
relation of cells even months after writing down the formulars.



      parent reply	other threads:[~2012-09-30  7:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28  8:37 Torsten Wagner
2012-09-28  8:46 ` Bastien
2012-09-28 12:32   ` Torsten Wagner
2012-09-28 13:53     ` Bastien
2012-09-28 16:17       ` Torsten Wagner
2012-09-28 16:56         ` Bastien
2012-09-28 16:00     ` Bastien
2012-09-28 16:18       ` Torsten Wagner
2012-09-29  9:17       ` Carsten Dominik
2012-09-29  9:57         ` Achim Gratz
2012-09-29  9:59           ` Bastien
2012-09-29 10:03             ` Achim Gratz
2012-09-29 10:01           ` Carsten Dominik
2012-09-29 10:04             ` Bastien
2012-09-29 10:11             ` Achim Gratz
2012-09-29 10:58               ` Carsten Dominik
2012-09-29 12:02                 ` Achim Gratz
2012-09-30  7:30         ` Torsten Wagner [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:

  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='CAPaq-gO_xKbNm9Tiqv5v=yWVnp22mM-czi=mByJ0CRmEvPGi4w@mail.gmail.com' \
    --to=torsten.wagner@gmail.com \
    --cc=bzg@altern.org \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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).