New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Org id is not being used for links #303
Comments
|
It looks like you should add If you don't want the notebook links, you can also use |
|
Ah. That worked for the org-id link. However - each time I call org-store-link : I get the question 'which function for creating the link?' and there's only one option there |
|
If you delete org-id-store-link you will see two options, the other one for the nb link. I am not sure why there is a preloaded choice. if you set the nb :store link to nil I think that will go away. |
|
Yes, it did go away after setting nb :store link to nil. I have not really used the nb links before - any advantages of using nb links that I should be aware of ? I use nb-new for any new project and org-projectile to capture project specific tasks. |
|
nb links are more portable than id links in some ways. For example, in a git repo if someone makes a heading and links to it by an id, you will not necessarily be able to follow that link if you haven't opened the org-file and had the id registered. This happens a lot to me in shared project files with my students. The nb link avoids that issue and allows you to make a link relative to a project root that works on other machines that also have the project, but maybe in another place (so neither relative nor absolute links would work) as long as you have visited the project with projectile (so that it knows where the root is). nb links make it easy to make links between projects that don't break when project move around. in principle id links can do this too, but in practice if the id isn't in the id database, it triggers a very long search that the nb link avoids. nb links have some different actions associated with them also which might be useful, e.g. open bash in the directory with M-b, or finder/explorer with M-e, etc. |
|
I see now what you mean. It appears the nb link references a position? How do you deal with updates in the document? |
|
It can reference a position but if you do that with a character or line number it is fragile and if the document updates the link will not point to the same place anymore. You can also use org references (I think) to headlines. I am thinking of adding some git link capabilities so you can link to past versions of files. It is possible to link to an image, and see an overlay of the image on the link. |
|
Is there a way to make nb-links compatible with https://github.com/nobiot/org-transclusion? |
|
I don't know a way to make them compatible. It would probably have to be the other way around, which is figure out how to make org-transclusion work with that kind of link. |
|
OK, just for my understanding, how does emacs resolve a link like |
|
It runs the function |
|
I saw this function in the docs, but if I run this outside of a project it claims that |
|
The only way you can run it outside a project is like |
|
thanks! |
I'm unable to use org-id's for storing links - with scimax loaded and zero user customisation scripts (except the snippet below). Link targets come out to something like
nb:my_org::notes.org::c721452. Would be grateful for advice on fixing this.Snippet for org id:
The text was updated successfully, but these errors were encountered: