If you put the links in a file using org-mode (e.g. ending in .org), you can create links like this by:
[[file:d:/path/to/filename with spaces]]
I'm assuming you are on Windows, and this works for on Windows 8, Emacs 24.4.1.
If you use org-ref (https://github.com/jkitchin/org-ref), you can do this:
#+caption: test label:some-source-code
for i in 1:10:
See Listing ref:some-source-code
This exports to PDF and HTML with active links.
You can use the following links:
The first will take you to the Elisp Intro, the second to the Reference Manual.
Whenever you may wish to link to an info document, use the following syntax:
The file and node names are always listed on the top of any info file. In case the node name has spaces, then you'll ...
The history of visited nodes is stored in the variable Info-history-list. You will need to persist this variable across sessions. One way to do so it to use desktop-mode. Desktop mode automatically persists the variables that are declared in desktop-globals-to-save. So if you use desktop-mode something like the following should doe the trick
I found the solution, Org-mode radio target can be used here.
here is the doc: http://orgmode.org/org.html#Internal-links
Here is a named table.
#+NAME: my target
| x | y |
| 1 | 2 |
I can reference it with its name. Like this:
There are also table remote references further explained by an example in the following.
First we ...
My orglink package does that. It "implements support for some Org Mode link types in other major modes. Links can be opened and edited like in Org Mode".
These are some examples of links that it does and does not support:
[[Code][start of code]]
The string behind :: is actually a search. In this context one understands the relevant comment in the source code of the function org-html-link in the library file ox-html.el (org 8.2.5).
;; Add search option, if any. A search option can be
;; relative to a custom-id or a headline title. Any other
;; option is ignored.
So, you can either ...
@Iqbal gives a great answer to your question.
You might also consider using bookmarks to record Info locations of interest, including a bookmark for where you left off (which you update at the next left-off place, by just setting it again).
This is simple to do, and is exactly what you would do with a book or multiple books that you are reading.
The reason for the error is that you did not use the correct format to add a text property.
quote from manual:
Function: add-text-properties start end props &optional object
The argument props specifies which properties to add. It should have the form of a property list (see Property Lists): a list whose elements include the property names ...
It's not 100% clear if you want only the ability to click on URLs,
or if you want to change their faces in the buffer. For the
former, you can use either browse-url as you suggest:
(global-set-key [mouse-1] #'browse-url) ; pick your preferred mouse button
Or, if you just want it to open without having to confirm the URL,
you could ...
for i in 1:10:
This should link back to some-source-code.
Caveat: [[file:::some-source-code]] is performing a degenerate search and will look for <<some-source-code>> links before #+NAME: some-source-code.
I don't understand what you are hoping to get or expecting. I think if you have a description, you will get a hyperlink to the file, not the image itself.
Of these two links, the first turns into the word test which is hyperlinked to the file, and the second is shown as the image in the pdf for me.
Use org-store-link to store the position of your current emacs buffer file and in your org file org-insert-link to insert the stored link. This prompts you with a selection of links and a query for the description to insert.
Assuming the current buffer is an org-mode buffer,
the following code collects paths of file links in the current buffer.
(org-element-map (org-element-parse-buffer) 'link
(when (string= (org-element-property :type link) "file")
(org-element-property :path link))))
In an org buffer, (org-element-parse-buffer) returns the parse
You can set up your own protocols in org-link-parameters with org-link-set-parameters.
If you run
(org-link-set-parameters "chrome" :follow (lambda (path) (browse-url-chrome (concat "http:" path))))
(org-link-set-parameters "chromes" :follow (lambda (path) (browse-url-chrome (concat "https:" path))))
(org-link-set-parameters "chromium" :follow (lambda (...
I'll answer your actual problem of modifying the action for following links with pdf-tools.
The customizable option pdf-links-browse-uri-function holds a function that receives a string with the uri as an argument and should take the appropriate action, e.g., open the link in a browser.
You can define your own function and register it there with M-x ...
markdown-follow-thing-at-point (C-c C-o) and also markdown-follow-link-at-point will follow links. If you have a link like [filelink](/path/to/file.md) then calling one of the above functions while cursor is on the markdown link will take you to the file.
I would make this a comment, but I don't have enough rep so here goes:
Check out this function: org-activate-plain-links (in org.el).
You can modify the function around the 'add-text-properties', doing a match on each link using a cond for instance.
I have student supervision now, but if you don't succeed in doing this, I'll add more information later.
I hope this is not to send a bad signal. I will answer my own question once more. The comments are very helpful in guiding me, however I have to use both my 'knowledge' of my setup, my laziness, and the good suggestions to come up with the following solution.
At first I thought bisecting as @Drew suggested is a tedious task. So I do M-x package-install RET ...
One way to accomplish what you want is to wrap org-contacts with a special org-contacts-mode as demonstrated in the following.
This new major mode defines the keys l and c as you specified it in its local keymap.
You may paste the code into your .emacs file after (require 'org-contacts) or a suitable autoload.
You can just call org-contacts instead of your ...
I plan on using one dictionary for everything, I'd prefer not to include the entire file for each document.
I have this in my .emacs:
'(("google" . "http://www.google.com/search?q=")
("dictionary" . "file:~/Brainbank/main/dictionary.org::")))
Then include a link to the file:
It's not automated, and ...
So this may not be exactly what you want but it turns the section that is underneath your point into a link that should be shorter.
(defun compress-org-link (arg)
(let ((url (thing-at-point 'url))
(bounds (bounds-of-thing-at-point 'url)))
(kill-region (car bounds) (cdr bounds))
(insert (format "[[%s][%s]]" url (truncate-...
The function browse-url-url-encode-chars translates
if used in the following way:
(browse-url-url-encode-chars "https://en.wikipedia.org/wiki/Blue_(disambiguation)" "[\"()$]")
Citation of the doc string of browse-url-...
You can easily build this functionality by getting at abo-abo's org-download package. Look at the command org-download-image which takes an image address as its argument and downloads it to an attachment directory.
For associating an image directory with an org document, I would always recommend to use the org attachment mechanism. I prefer to have a clear ...
The function org-wiki-insert inserts a wiki: link of the form [[wiki:MyHeading][MyHeading]].
But, it's more convenient to use the built-in org-insert-link. For that we need two things: completions for the link target and a default description. For the first, we just need to define a function called org-wiki-complete-link and org-mode will pick it up for ...
If those are URLs you would put in the location bar at the top of a browser window, then they represent an implied "http://" (or possibly "https://") protocol prefix. Try making that prefix explicit in the Org link. Is it correctly clickable now?
Seems like Org successfully stores the link to a heading like this one but fails to parse it as an internal link afterwards.
Here's a workaround: use the CUSTOM_ID property:
Working link: [[#heading-with-links][heading with links]]
* heading with [[file:alink.stuff][links]]
- some notes here
You may consider putting your glossary in another format. For example, I use list definitions to accomplish what you are after, for example:
* List of Acronyms
- <<<ABI>>> :: Application Binary Interface
- <<<API>>> :: Application Programming Interface
- <<<DOR>>> :: Documentation Requirement