unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hanno Perrey <hanno@hoowl.se>
To: rms@gnu.org
Cc: philipk@posteo.net, stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: jami-bot and org-jami-bot
Date: Wed, 17 Jan 2024 09:00:39 +0100	[thread overview]
Message-ID: <87ply0l5qs.fsf@hoowl.se> (raw)
In-Reply-To: <E1rPaAx-0005rJ-GA@fencepost.gnu.org>


Hej,

>   > While this is technically true, the capture functionality is only a hook
>   > added to jami-bot. It would be very easy to "capture" messages into
>   > plain text files or other formats with only a few lines of code and only
>   > requiring jami-bot.
>
> This might be "very easy" for someone who understands jami-bot, but it
> is NOT as easy for a USER as simply using org-jami-bot.  Even if the
> code to do so is rather simple, there is a big practical diffeence for
> a user between "Just load this file" and "You need to write 50 lines
> of code."

I completely get your point and I think we are talking about different
things. I was thinking of developers or power-users, who I think are the
main target user-base for jami-bot as it does not come with much
built-in functionality for the user. It is more of a library to make
automatic messaging through Jami easier. User features would be added by
packages building on top of it, such as org-jami-bot.

While I stand by my point that implementing a specific use case is
straightforward (I should not have said "very easy") for someone
familiar with Elisp, creating a package that replicates Org mode
features but without Org mode and is simple to use and configure *is*
work.

> Can you do this easy job, so that using jami-bot without Org is 100% as
> easy as using it with Org?

No. Currently, I simply do not have the spare time.

What is more, I am a heavy Org mode user and do not have a clear
understanding of the use case without Org mode. Who are the users and
what are their needs? What should the format be? What needs to be
configurable?

If anyone is interested in working on such a package or even just
scratching their own itch and creating a hook for a specific use case,
then I am more than happy to advice and help out.

Alternatively, if a generic capture framework for Emacs is created, I am
happy to target that instead of Org mode capture.

>   > However, with the latter I have not implemented any actual capture
>   > feature, only the "glue" to Org mode's.
>
> I don't understand this part at all.  What is a "capture" feature?
> What does it do?  What does org-capture do?

"capturing" refers to the process of storing new information in your
collection of notes. org-capture does this very quickly and
unobtrusively. It is highly configurable and a framework that I use for
a lot of different knowledge-storing actions, from todos to
bibliographic references. For me, it is the natural entry point for new
information as it is automatically stored where I can find it again.

> I have never used Org mode.

And I am similarly unfamiliar with your workflow and needs for storing
notes (this is what we talk about here as org-jami-bot does just that
through org-capture). By targeting org-capture, I had hoped to create a
tool that would be useful for anyone who is familiar with its mechanism.
I understand that this alienates anyone who does not use Org mode but to
the best of my knowledge, there is currently no more generic way in
Emacs.

Best wishes,
Hanno



  reply	other threads:[~2024-01-17  8:00 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28 11:21 [ELPA] New package: jami-bot and org-jami-bot Hanno Perrey
2023-12-28 21:33 ` Stefan Kangas
2023-12-29 14:08   ` Hanno Perrey
2023-12-30  3:20 ` Richard Stallman
2023-12-30 10:29   ` Hanno Perrey
2024-01-01  3:34     ` Richard Stallman
2023-12-30 12:15   ` [DISCUSSION] Possible inclusion of org-capture.el into Emacs core (was: [ELPA] New package: jami-bot and org-jami-bot) Ihor Radchenko
2023-12-30 17:43     ` Stefan Kangas
2024-01-01  3:34     ` Richard Stallman
2024-01-01  3:59     ` Richard Stallman
2024-01-01 14:05       ` Ihor Radchenko
2023-12-30 12:43   ` [DISCUSSION] org-capture.el vs remember.el " Ihor Radchenko
2023-12-30 17:20     ` Stefan Kangas
2023-12-30 19:16       ` João Távora
2023-12-30 19:19         ` João Távora
2023-12-31 18:05         ` Adam Porter
2024-01-07 21:01 ` [ELPA] New package: jami-bot and org-jami-bot Stefan Kangas
2024-01-08 21:08   ` Richard Stallman
2024-01-08 21:29     ` Ihor Radchenko
2024-01-09  3:30     ` Eli Zaretskii
2024-01-09  4:42       ` Stefan Kangas
2024-01-10  4:24         ` Richard Stallman
2024-01-10  5:36           ` Stefan Kangas
2024-01-10  4:24       ` Richard Stallman
2024-01-11 15:30         ` ELPA packages and Org mode integration (was: [ELPA] New package: jami-bot and org-jami-bot) Ihor Radchenko
2024-01-09 19:39   ` [ELPA] New package: jami-bot and org-jami-bot Philip Kaludercic
2024-01-11 18:51     ` Richard Stallman
2024-01-11 20:12       ` Stefan Kangas
2024-01-12  7:24         ` Eli Zaretskii
2024-01-12 12:38           ` Ihor Radchenko
2024-01-12 13:59             ` Eli Zaretskii
2024-01-12 14:13               ` Ihor Radchenko
2024-01-12 14:37                 ` Eli Zaretskii
2024-01-12 14:45                   ` Ihor Radchenko
2024-01-12 15:04                     ` Eli Zaretskii
2024-01-12 15:17                       ` Ihor Radchenko
2024-01-14  3:03         ` Richard Stallman
2024-01-14  3:03         ` Richard Stallman
2024-01-14  9:58           ` Stefan Kangas
2024-01-14 10:25             ` Emanuel Berg
2024-01-14 11:43               ` Ihor Radchenko
2024-01-14 10:47             ` Emanuel Berg
2024-01-17  3:29             ` Richard Stallman
2024-01-31  3:34             ` Richard Stallman
2024-02-03  9:28               ` Hanno Perrey
2024-01-15  3:12           ` Richard Stallman
2024-01-12 15:04       ` Hanno Perrey
2024-01-16  3:31         ` Richard Stallman
2024-01-17  8:00           ` Hanno Perrey [this message]
2024-01-12 14:58     ` Hanno Perrey
2024-01-14 18:46     ` Hanno Perrey
2024-01-15  7:06       ` Philip Kaludercic
2024-01-17  7:59         ` Hanno Perrey
2024-01-17 23:39           ` Philip Kaludercic
2024-01-20 14:46             ` Hanno Perrey

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=87ply0l5qs.fsf@hoowl.se \
    --to=hanno@hoowl.se \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=rms@gnu.org \
    --cc=stefankangas@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 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).