From: Eli Zaretskii <eliz@gnu.org>
To: John Task <q01@disroot.org>
Cc: emacs-devel@gnu.org
Subject: Re: [NonGNU Elpa] New package: ETT
Date: Wed, 03 May 2023 18:55:25 +0300 [thread overview]
Message-ID: <831qjxmmtu.fsf@gnu.org> (raw)
In-Reply-To: <86mt2lbj2e.fsf@disroot.org> (message from John Task on Wed, 03 May 2023 11:07:24 -0300)
> From: John Task <q01@disroot.org>
> Cc: emacs-devel@gnu.org
> Date: Wed, 03 May 2023 11:07:24 -0300
>
> Thanks for the reply.
>
> > Since Emacs has Org and todo-mode, which both seem to fit the above
> > description, it would be good to know what makes this particular
> > package stand out.
(Sorry, I said "todo-mode", but I really meant the timeclock package
instead.)
> Basically, ETT is largely modeled after "modern" time trackers, which
> not only track time but also gather statistics, display graphs,
> support setting goals, and (the most important thing) are easy to use.
> ETT is indeed designed to be easy to use; knowing three or four
> commands allows anyone to use it. Given the set of features it
> offers, this fact alone makes it stand out.
timeclock has just 2 main commands: clock in and clock out.
Anyway, did you consider extending existing packages with those modern
features, instead of making a completely new separate package?
next prev parent reply other threads:[~2023-05-03 15:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 14:07 [NonGNU Elpa] New package: ETT John Task
2023-05-03 15:55 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-03 18:06 John Task
2023-05-03 17:14 John Task
2023-05-03 18:05 ` Eli Zaretskii
2023-05-03 15:29 John Task
2023-05-03 16:57 ` Sam Steingold
2023-05-03 15:02 John Task
2023-05-03 16:41 ` Philip Kaludercic
2023-05-02 21:21 John Task
2023-05-03 6:08 ` Philip Kaludercic
2023-05-03 6:11 ` Philip Kaludercic
2023-05-03 7:12 ` Yuri Khan
2023-05-03 11:12 ` Eli Zaretskii
2023-03-01 18:17 John Task
2023-03-01 17:46 John Task
2023-03-02 4:33 ` Richard Stallman
2023-03-02 10:08 ` Holger Schurig
2023-03-02 14:50 ` q01
2023-03-02 15:55 ` John Task
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831qjxmmtu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=q01@disroot.org \
/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.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).