From: "Quiliro Ordóñez" <quiliro@riseup.net>
To: "Sébastien Rey-Coyrehourcq"
<sebastien.rey-coyrehourcq@univ-rouen.fr>,
"Alan Schmitt" <alan.schmitt@polytechnique.org>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: SQLite for contacts and relations to Org - Re: contact management in emacs
Date: Sun, 09 Oct 2022 15:21:29 +0000 [thread overview]
Message-ID: <f9b0aa1f9a3f4f8b62157fc44d4e44f5@riseup.net> (raw)
In-Reply-To: <Y0KlELX5UFQoo0OA@protected.localdomain>
El 2022-10-09 05:40, Jean Louis escribió:
> But I can as well edit my contacts by using external tools and
> exchange information with other software.
>
> Do you wish to share your contacts? That is easy, one can simple send
> the full file to somebody.
>
> By followed the thought patterns described one shall understand that
> contacts may be separated from single mode (Org) and separated from
> single software (Emacs) and that it will not minimize or limit you but
> rather widen the capacities and usefulness for human.
This is a great summary about the use of database to hold information.
But it requires experience configuring databases for end-users. It
could work if the database was set up by someone else or if the fields
were easy to define by the end-user by some kind of interface.
On the other hand, there is a movement to use plain text for everything.
I know you disagree. But here is some information about accounting
this way: https://plaintextaccounting.org
I learned a lot of elisp by reading your long explanation about how to
construct a contact database directly on Emacs 29 without adding
anything else. Thank you very much!
next prev parent reply other threads:[~2022-10-09 15:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 11:08 contact management in emacs Alan Schmitt
2021-02-27 11:31 ` Martin Steffen
2021-02-27 13:20 ` andrés ramírez
2021-02-27 14:40 ` Eric S Fraga
2021-02-27 15:12 ` andrés ramírez
2021-02-28 10:21 ` Eric S Fraga
2021-02-27 15:14 ` Martin Steffen
2021-02-27 17:00 ` Dr. Arne Babenhauserheide
2021-02-27 16:53 ` Bob Newell
2021-02-28 9:06 ` Russell Adams
2021-02-28 11:09 ` Alan Schmitt
2021-03-03 14:40 ` TRS-80
2021-03-07 22:57 ` Jean Louis
2021-03-08 20:06 ` John Kitchin
2021-03-10 8:32 ` Jean Louis
2021-03-07 22:13 ` Jean Louis
2021-03-08 7:49 ` Alan Schmitt
2021-03-08 8:12 ` Jose E. Marchesi
2021-03-10 8:32 ` Jean Louis
2022-09-09 16:11 ` Sébastien Rey-Coyrehourcq
2022-09-10 5:46 ` Ihor Radchenko
2022-10-09 10:40 ` SQLite for contacts and relations to Org - " Jean Louis
2022-10-09 15:21 ` Quiliro Ordóñez [this message]
2022-10-09 16:59 ` Jean Louis
2022-10-09 19:09 ` Quiliro Ordóñez
2022-10-10 6:12 ` Jean Louis
2022-10-10 22:29 ` Robert Weiner
2022-10-10 23:32 ` Jean Louis
2022-10-11 3:20 ` Robert Weiner
2022-10-11 5:54 ` Sébastien Rey-Coyrehourcq
2022-10-11 19:59 ` Jean Louis
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=f9b0aa1f9a3f4f8b62157fc44d4e44f5@riseup.net \
--to=quiliro@riseup.net \
--cc=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
--cc=sebastien.rey-coyrehourcq@univ-rouen.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).