unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrew Hyatt <ahyatt@gmail.com>
To: Andrew Hyatt <ahyatt@gmail.com>, emacs-devel@gnu.org
Subject: Re: [NonGNU ELPA] New package: ekg
Date: Wed, 4 Jan 2023 20:24:02 -0500	[thread overview]
Message-ID: <CAM6wYY+rM66ezm413EghnWEi-EEB5xNVdLFBafrQWJnWwnQdJA@mail.gmail.com> (raw)
In-Reply-To: <Y7Uw2DSA66thjjNE@protected.localdomain>


[-- Attachment #1.1: Type: text/plain, Size: 3405 bytes --]

On Wed, Jan 4, 2023 at 3:03 AM Jean Louis <bugs@gnu.support> wrote:

> * Andrew Hyatt <ahyatt@gmail.com> [2023-01-03 01:29]:
> > I've created a new package called ekg, which can be found at
> > https://github.com/ahyatt/ekg.  I'd like to add it to NonGNU ELPA.
>
> Great to see new package.
>
> My opinions are not related to recording it to NonGNU ELPA.
>
> Related to design, and being heavy user of 1736 different tags, it is
> alright to search within titles, but that only titles are tags is not
> quite in place. That it isn't unique to ekg, does not make it
> better. Maybe there is no need to talk about tags in that place.
>
> I search by title, and by tags, or by both, and by other complexities.
>
> A document may be named "Certificate of Good Standing" and can have
> tag "todo" or tag "Armenia", or "free" or anything that is not
> directly related to title.
>
> I leave that to you. However, I see that the idea comes from the
> following problem you encountered:
>
> > The advantage of this method is that it solves something that has
> > bothered me for a while about the recent suite of tools like org-roam:
> > backlinks are non-symmetrical. If you enter a note in your org-roam
> > daily about emacs, and link it to the emacs note, then when you go to
> > the emacs note, you have to explicitly enable the backlinks buffer to
> > see the daily entry where you first entered it. Systems such as Logseq
> > and the original Roam have backlinks alongside normal content, but
> > this doesn’t seem possible in emacs, where a buffer of a file is
> > expected show the file, and tricks with overlays can’t solve the
> > issue
>
> Your paragraph has explained something, I get only vague clue about
> the main point.
>
> Can you provide screenshot?
>

I've attached a screenshot of ekg, showing a document about "chicago style
pizza" and a reference to it.  They both have the same tags: the date they
were created on, and "chicago style pizza".  If I want a note to show up
when I look at the "chicago style pizza" tag, then I tag it with that tag,
not link it.

This is opposed to the other way of doing it, where you have to use another
buffer.  I'm including a screenshot of how org-roam does it.  But that's
different also to how Logseq does it, which is to have the backlinks
inline.  I'm attaching a third screenshot to show you what I mean there,
see the "Unlinked references" at the bottom.

>
> Is your main point to show the buffer with backlinks at all times?
>

My main point is that it shouldn't be in a separate buffer.  I want it
inline.  It doesn't work to have it inline in the note itself, but it does
work if you have a buffer that lists all notes with the tag, and instead of
linking references to get the backlinks, you just tag things the same way.
Hope this helps.


>
> Or to record the backlinks in first place?
>
> > One of the notable design choices is that this is built on top of my
> triples
> > package (which has been added to GNU ELPA), and so everything, notes,
> tags,
> > URLs, and all, is stored in a sqlite database.
>
> That is good, I may test it and see how it works and if it is scalable.
>
> --
> Jean
>
> Take action in Free Software Foundation campaigns:
> https://www.fsf.org/campaigns
>
> In support of Richard M. Stallman
> https://stallmansupport.org/
>

[-- Attachment #1.2: Type: text/html, Size: 4520 bytes --]

[-- Attachment #2: Screenshot - ekg "backlinks".jpg --]
[-- Type: image/jpeg, Size: 263044 bytes --]

[-- Attachment #3: Screenshot - org roam backlinks.jpg --]
[-- Type: image/jpeg, Size: 399343 bytes --]

[-- Attachment #4: Screenshot - logseq backlinks.jpg --]
[-- Type: image/jpeg, Size: 366802 bytes --]

  reply	other threads:[~2023-01-05  1:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-02 22:27 [NonGNU ELPA] New package: ekg Andrew Hyatt
2023-01-04  7:55 ` Jean Louis
2023-01-05  1:24   ` Andrew Hyatt [this message]
2023-01-06 17:32     ` Jean Louis
2023-01-17  5:18 ` Andrew Hyatt
2023-01-19  9:27   ` Jean Louis
2023-01-19 14:26     ` Andrew Hyatt
2023-01-20  6:53       ` Jean Louis
2023-01-20 16:58         ` Andrew Hyatt

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=CAM6wYY+rM66ezm413EghnWEi-EEB5xNVdLFBafrQWJnWwnQdJA@mail.gmail.com \
    --to=ahyatt@gmail.com \
    --cc=emacs-devel@gnu.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).