emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Jude DaShiell <jdashiel@panix.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: forms and org-mode
Date: Sat, 21 Aug 2021 18:33:50 +1000	[thread overview]
Message-ID: <878s0vp4lo.fsf@gmail.com> (raw)
In-Reply-To: <alpine.NEB.2.23.451.2108210353080.2487@panix1.panix.com>

OK, but I'm still a little unclear exactly what you are asking about.

If it is just a general question about whether Emacs Forms could be used
for data input into an org table, the basic answer is yes, I think so.

If your asking if anyone has done this - not that I'm aware of.

If your asking how hard it would be to do, well that depends.

The biggest challenge I can see is that Emacs forms expects a data file
which  just consists of one record per line where each record is
separated by a specific character. That part is not too hard. However,
where things might get tricky is if you want to keep the data in an org
file with other org data.

I imagine you could maintain a table in a data file fairly easily. You
can use the org '|' as the field separators and you would likely need to
write an input and output filter function to remove white space and add
it back on writing. None of this would be too hard.

However, if you wanted an emacs forms interface to one or more tables
inside a normal org file, it might be more tricky. You would need a far
more sophisticated input/output filters and possibly need to narrow the
file or do something else to help the filter functions target the data.

It has been many years since I used Emacs Forms. From memory, I gave up
on them as the level of maintenance exceeded the usefulness. I guess it
all really depends on how much data you need to edit and how predictable
the target data files are.

Jude DaShiell <jdashiel@panix.com> writes:

> My reason for using forms to do data input into org tables is to minimize
> errors in the data input to the org tables.
> On Sat, 21 Aug 2021, Tim Cross wrote:
>> So you are asking about using Emacs forms for data input into an org
>> table?
>> Just not clear on what exactly your asking about.
>> Jude DaShiell <jdashiel@panix.com> writes:
>> > A table with a time stamp column, a text column for notes and an interval
>> > column rounded to nearest hour.  Any statistics to be calculated on that
>> > intervals column.
>> >
>> >
>> > On Sat, 21 Aug 2021, Ihor Radchenko wrote:
>> >
>> >> Can you elaborate?
>> >>
>> >>

  reply	other threads:[~2021-08-21  8:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-21  2:50 forms and org-mode Jude DaShiell
2021-08-21  3:51 ` Ihor Radchenko
2021-08-21  4:41   ` Jude DaShiell
2021-08-21  5:00     ` Tim Cross
2021-08-21  7:54       ` Jude DaShiell
2021-08-21  8:33         ` Tim Cross [this message]
2021-08-21  8:55           ` Jude DaShiell
2021-08-21 10:14             ` Ihor Radchenko
2021-08-21 10:26               ` Greg Minshall
2021-08-21 10:39                 ` Ihor Radchenko
2021-08-21 11:41                   ` Tim Cross
2021-08-21 12:45                     ` Ihor Radchenko
2021-08-21  5:02     ` Ihor Radchenko

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=878s0vp4lo.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jdashiel@panix.com \


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