From: daniela-spit@gmx.it
To: Jean Louis <bugs@gnu.support>
Cc: tomas@tuxteam.de, emacs-orgmode@gnu.org,
Ihor Radchenko <yantar92@gmail.com>
Subject: Re: Emacs inserts hardwired org-agenda-files variable, overwriting user options
Date: Sat, 12 Dec 2020 03:41:03 +0100 [thread overview]
Message-ID: <trinity-05c29270-f619-4631-9719-63566e1f9d87-1607740863056@3c-app-mailcom-bs06> (raw)
In-Reply-To: <X9QsZC84XKBOb8Zr@protected.rcdrun.com>
> Sent: Saturday, December 12, 2020 at 3:35 AM
> From: "Jean Louis" <bugs@gnu.support>
> To: "Ihor Radchenko" <yantar92@gmail.com>
> Cc: daniela-spit@gmx.it, tomas@tuxteam.de, emacs-orgmode@gnu.org
> Subject: Re: Emacs inserts hardwired org-agenda-files variable, overwriting user options
>
> * Ihor Radchenko <yantar92@gmail.com> [2020-12-11 17:24]:
> > > ... there is no active
> > > hacking on org-agenda and adding new features.
> >
> > You are welcome to submit patches.
> >
> > I have experimental code to use pretty-symbols in agenda and align tags
> > even when frame size changes [1]. However, last time I proposed this on
> > mailing list, there was no interest...
> >
> > [1] https://orgmode.org/list/87r1v71aw0.fsf@localhost/
>
> By the way I have completely switched all action management to my
> database system with tabulated list mode. No more using Org for action
> management, only for document, not even short notes. Access to notes
> by relevance search by using PostgreSQL full text search is so much
> more logical personally. Computer performs search but as database is
> more compact it does not search over all files. Things are easily
> reordered rather then refiled. Key bindings for majority of actions
> are way shorter as tabulated list mode is not editing mode.
>
> - tasks can be assigned to one among 200,000+ people in the database,
> and I need not take care how their names are written and if I will
> lose a task because I made a type in writing their names. Person is
> rather selected and computer thinks what is their unique ID, not
> name.
>
> - listing tasks assigned to specific person or group of people is
> quick and easy, related to person or group is quick or easy.
>
> - daily list of pending tasks can be sent by email automatically, list
> of completed tasks can be sent. Task as such can be sent with one or
> two keys pressed without me thinking as all related objects are
> integrated (email address of assignee is already known).
>
> - I need not keep one list of assignees in one file, other list in
> other file, etc. I can list all asignees straight with one key or
> see actions assigned to them.
>
> - and I do not write subordinate tasks as TODO any more, that makes no
> sense. There is one senior section on what subject, project or
> objective has to be fullfiled and those subordinate tasks which are
> not marked with TODO repetitevely can be marked as redundant or
> superfluous, purposeless when senior objective have been
> completed. This means they are not done as there is no need to get
> something done if objective have been fullfiled. Org mode have
> imposed reverse on users where for example a list of items is only
> then completed as DONE when subordinate tasks have been completed as
> DONE, which makes users lie to themselves as they will then
> "complete" the task which is not complete because it is purposeless
> only to complete the senior task as DONE.
>
> And I think it is possible for anybody regardless of programming skill
> level to make one's own system of management of tasks within less than
> a week that will get more aligned to personal individualized way of
> handling tasks, then trying to accommodate personal needs to software
> that may have gone one completly wrong direction.
If I said that I would be barraged by accusations of rudeness! :)
> Software is there to help the human, not human to help the software.
>
>
next prev parent reply other threads:[~2020-12-12 2:44 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 18:52 Emacs inserts hardwired org-agenda-files variable, overwriting user options daniela-spit
2020-11-29 20:07 ` Tom Gillespie
2020-11-29 20:19 ` daniela-spit
2020-11-29 21:01 ` Tom Gillespie
2020-11-29 21:02 ` Kyle Meyer
2020-11-29 22:08 ` daniela-spit
2020-12-11 3:59 ` TRS-80
2020-12-11 4:16 ` daniela-spit
2020-12-11 4:32 ` daniela-spit
2020-12-11 8:25 ` tomas
2020-12-11 13:47 ` daniela-spit
2020-12-11 13:59 ` Detlef Steuer
2020-12-11 14:18 ` daniela-spit
2020-12-11 14:23 ` Christopher Dimech
2020-12-11 14:26 ` Ihor Radchenko
2020-12-11 14:47 ` daniela-spit
2020-12-12 2:35 ` Jean Louis
2020-12-12 2:41 ` daniela-spit [this message]
2020-12-13 5:19 ` Jean Louis
2020-12-13 5:51 ` daniela-spit
2020-12-13 13:19 ` Jean Louis
2020-12-13 17:49 ` Christopher Dimech
2020-12-13 20:28 ` Jean Louis
2020-12-13 3:33 ` TRS-80
2020-12-13 8:46 ` Jean Louis
2020-12-13 9:28 ` Ihor Radchenko
2020-12-13 17:31 ` Jean Louis
2020-12-13 17:57 ` Christopher Dimech
2020-12-13 17:59 ` Christopher Dimech
2020-12-14 12:49 ` Ihor Radchenko
2020-12-14 19:39 ` Jean Louis
2020-12-11 14:43 ` tomas
2020-12-11 14:54 ` daniela-spit
2020-12-11 15:46 ` tomas
2020-12-11 15:58 ` daniela-spit
2020-12-11 6:25 ` Jean Louis
2020-11-29 20:15 ` Jean Louis
2020-11-29 20:46 ` daniela-spit
2020-11-29 20:58 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-05c29270-f619-4631-9719-63566e1f9d87-1607740863056@3c-app-mailcom-bs06 \
--to=daniela-spit@gmx.it \
--cc=bugs@gnu.support \
--cc=emacs-orgmode@gnu.org \
--cc=tomas@tuxteam.de \
--cc=yantar92@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.