From: Jean Louis <bugs@gnu.support>
To: Gerardo Moro <gerardomoro37@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Remembrance Agents
Date: Mon, 30 Nov 2020 13:35:18 +0300 [thread overview]
Message-ID: <X8TK5qva73tVftJL@protected.rcdrun.com> (raw)
In-Reply-To: <87wny3xij3.fsf@ucl.ac.uk>
* Eric S Fraga <e.fraga@ucl.ac.uk> [2020-11-30 13:11]:
> On Monday, 30 Nov 2020 at 11:37, Gerardo Moro wrote:
> > Ok, thanks. How do you specify the location and is the formatting ok when
> > showing you the relevance pieces of text from the local databases?
>
> The agent needs to be told which files to index (check the man page for
> ra-index) and, in my case, I point it to all .org files and all text
> files under ~/Mail. The formatting is okay as far as I am concerned but
> this is a subjective aspect that will differ for everybody!
SMART (String Matching Algorithm Research Tool)
https://github.com/smart-tool/smart
Does it use this algorithm? I am cloning that one to see how useful it
could be in relevance searches.
,----
| However, I can also see that the PostgreSQL database has already
| built-in features for relevance searches:
|
| https://www.postgresql.org/docs/current/textsearch-intro.html
`----
This makes then many external software pieces redundant, it becomes
again trivial to work with a database as underlying algorithm and
functions have already been programmed. Making a new remembrance agent
based on various structured information is making few higher level
functions that integrate the underlying capability of PostgreSQL
database and Emacs users' editing environment:
0. Create appropriate table in the database.
1. Make automatic or semi-automatic list of Org files or other files.
2. Make simple Emacs Lisp function to index all those files in the
database. This is probably few lines function.
3. Make few Emacs Lisp functions that observes what users is doing and
display to user relevant results with the possibility to construct
hyperlinks from the result buffer straight to Org buffer, or
possibility to open up those relevant files for more references.
Jean
next prev parent reply other threads:[~2020-11-30 10:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 16:59 Remembrance Agents Gerardo Moro
2020-11-28 17:08 ` George Mauer
2020-11-28 18:26 ` Jean Louis
2020-11-29 13:07 ` Gerardo Moro
2020-11-29 13:52 ` Eric S Fraga
2020-11-29 17:29 ` Jean Louis
2020-11-29 17:47 ` Eric S Fraga
2020-11-30 11:15 ` Jean Louis
2021-01-06 6:41 ` Possibility to copy text outside EMACS and send it to orgmode document Gerardo Moro
2021-01-06 6:48 ` Samuel Wales
2021-01-06 6:49 ` Tom Gillespie
2021-01-06 6:58 ` Gerardo Moro
2021-01-07 5:14 ` Ihor Radchenko
2021-01-07 5:36 ` Gerardo Moro
2021-01-07 6:17 ` Tom Gillespie
2021-01-07 6:29 ` Gerardo Moro
2021-01-07 7:54 ` Ihor Radchenko
2021-01-09 17:32 ` TRS-80
2021-01-06 15:56 ` Tim Visher
2021-01-06 17:42 ` Bob Newell
2021-01-06 20:46 ` Gerardo Moro
2021-01-06 16:14 ` Maxim Nikulin
2021-01-06 16:31 ` Juan Manuel Macías
2020-11-30 6:48 ` Remembrance Agents Gerardo Moro
2020-11-30 9:31 ` Eric S Fraga
2020-11-30 9:37 ` Gerardo Moro
2020-11-30 10:09 ` Eric S Fraga
2020-11-30 10:35 ` Jean Louis [this message]
2020-11-30 10:18 ` Jean Louis
2020-11-30 10:16 ` Jean Louis
2020-11-30 11:16 ` Gerardo Moro
2020-11-30 11:25 ` Jean Louis
2020-11-29 17:15 ` Jean Louis
-- strict thread matches above, loose matches on Subject: below --
2020-12-02 8:21 hpgisleropen
2020-12-02 11:37 ` 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=X8TK5qva73tVftJL@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=emacs-orgmode@gnu.org \
--cc=gerardomoro37@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/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).