If I read https://github.com/jethrokuan/org-roam/blob/b7afb02015a31a2cba02415ba863149ad7c0cee5/org-roam.el#L958 correctly, there is no particular ordering for the backlinks. It would be great to be able to configure it, for instance:

• most recently updated first (maybe this could be the default choice)
• oldest file first
• alphabetical order of title

Though it may be obvious that the android-sdk is a dependency for building orgzly, if it is not installed, then trying to run gradlew to build (as indicated in the README file) results in a cryptic error message:

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> kotlin.KotlinNullPointerException (no error message)

If one m

In the Issue #161 we have been talking about the org-brain "API", and the need to document the use of the org-brain functions from elisp with the needed arguments, parameters, etc. I want to work with you in what you need related to the more complex linking workflow possible.

All about the issue #163 is a good example of a coding, reference and documentation need for me. How do I

It seems like the / is causing unintentional italics. I don't know org formatting rules, but maybe it needs to be escaped? If not, maybe the formatting engine is off?

At this point, the 'table modification' actions are aligned left:

Hence, when scrolling the table to the right, they scroll out of view and cannot be used anymore:

Should

One bold, verbatim, italic, underline or code character followed by text then an other same highlighting does not correctly displayed.
In the snippet below, all the "should not" part are highlighted. Except for strike-through that is not managed at all.

*b* should not bold *bold* 
=v= should not verb =verb= 
_u_ should not underline _underline_
/i/ should not italic /ital

I'm starting to look at org-super-agenda, but the documentation is particularly difficult to follow. Installing it via MELPA gets it installed properly (I think) with an Info file, but the Info file does not look at all good. For instance, the pictures are totally gone when viewed in Emacs Info. I would suggest redoing your Info file from scratch -- perhaps as an Org file exported into Texinfo

A pip install requirements.txt runs into permission issues as a non-root user. Since sudo pip should never be invoked, pip install requirements.txt should read pip install requirements.txt --user.

When using the workflow where a single notes file is created per PDF, would it be possible to add some customizability so that the notes file could be named something like examplepdf-org-noter.org rather than examplepdf.org.

I would like this functionality as it would allow the use of Doom Emacs file-templating features [(documented here)](https://github.com/hlissner/doom-emacs/blob/develop

I'm currently using org-ql-search to create a pseudo org-agenda buffer. However, the query language doesn't seem to allow filtering the results based on the result of some predicate (like, for example org-agenda-skip-function does). Does it make sense to add such a parameter to org-ql-search (and also org-ql-block, once #79 is resolved)?

The alternative is to write custom code to iterat

Actual Behavior

I'm using org-attach as image and document references in the org notes. It works fine with ox-latex and ox-html, and it gets correct link, but with ox-hugo it gets incorrect references

For example, for [[attachment:MIT18_02SC_

It would be nice to be able to edit several similar notes using Column View. This could be done if notes supported using Org properties for fields instead of only subheadings.

Another interesting idea would be to support Org tables for defining several similar notes.

I would love to be able to create notes, directly from org-wiki-helm. In this way, the user would first use org-wiki-helm to search for the note. Then failing that, he would hit [RET] to automatically create the file.

This would be similar to how org-velocity and deft work... except that it relies on helm, which of course makes it all that much better! :)

Thanks for this good package. I find it quite enlightening!

I would like to suggest an addition: perhaps add one parameter size in org-sidebar and use it as follows?

(display-buffer-in-side-window (current-buffer)
                                         (list (cons 'side org-sidebar-side)
                                               (cons 'slot slot)
                            

Just ran into this amazing idea/package, it would be great to have a video tutorial or something, does anyone know anything that kind of help?

Derived from #112