Re: [O] Links to LaTeX equations

On Fri, Jun 28, 2019 at 4:46 PM Fraga, Eric wrote: > On Friday, 28 Jun 2019 at 11:58, Ken Mankoff wrote: > > Why don't you define the link in Org? > > > > #+NAME: eq:foo > > \begin{equation} > > And why are the obvious solutions not those that come to mind (for > me) > > Many thanks. Nothing

Re: [O] Links in Org-mode : Clunky

Dear Nathan, > Has anyone coded such a plugin or am I missing some cool Helm-fu? Not exactly the same, but see the code below. Note that the code does not support creating CUSTOM_ID. Instead, it silently creates an ID if it does not exist (see (org-id-get ... 'create)). The helm completion will w

[O] Links in Org-mode : Clunky

Hello all, I've always found that the links in org-mode are basically very clunky to try to use in a quick fashion. To my understanding (see my other question about CUSTOM_ID versus ID) it's a good practice to store either a CUSTOM_ID or ID - (still can't grok the difference) and then store a hyp

Re: [O] Links to LaTeX equations

Org-ref provides a ref link for exactly this purpose. It looks like ref:an-equation and if you click on it it jumps to the label. The link is red if the label doesn't exist and maroonish if it does. It exports in latex as \ref{an-equation}. It sounds like just what you need. You can get org-ref on

Re: [O] Links to LaTeX equations

On Friday, 28 Jun 2019 at 10:19, John Kitchin wrote: > Org-ref provides a ref link for exactly this purpose. Thanks John. I've looked at org-ref before and it looks nice. However, due to my organically grown org (and Emacs) customizations (over 35 years...), I couldn't get it to work well for m

Re: [O] Links to LaTeX equations

Hi Eric, On 2019-06-28 at 10:55 -02, Fraga, Eric wrote... > I would like to be able to use org fully with respect to links and > targets. If I define a label in LaTeX directly, \label{an-equation} > for instance, I get no benefit from using an org link to it, e.g. > [[an-equation]] Why don't you

Re: [O] Links to LaTeX equations

On Friday, 28 Jun 2019 at 11:58, Ken Mankoff wrote: > Why don't you define the link in Org? > > #+NAME: eq:foo > \begin{equation} And why are the obvious solutions not those that come to mind (for me) Many thanks. Nothing in the documentation to even suggest this possibility. That's my excu

[O] Links to LaTeX equations

Hello all, it's that time of year where I have to think about revamping my lecture slides (having just finished one year, the next one starts...). I write these in org and export to beamer obviously! I teach a technical subject. I therefore have quite a few equations in my slides and I use LaTe

Re: [O] Links for getting email in Gmail (IMAP) with Gnus ?

Le mar. 13 nov. 2018 à 09:36:17 , Eric S Fraga a envoyé ce message: > On Saturday, 10 Nov 2018 at 22:09, Joseph Vidal-Rosset wrote: >> Hello, >> >> I know that it is possible to link emails in Todo list, but I meet >> difficulties with Gmail IMAP and Gnus when the mail is in the box "All >> ema

[O] Links for getting email in Gmail (IMAP) with Gnus ?

Hello, I know that it is possible to link emails in Todo list, but I meet difficulties with Gmail IMAP and Gnus when the mail is in the box "All emails" ("Tous les messages" in French): as soon as the email is in this Archive, the link is broken and Gnus does not fetch it. Help and code are welco

Re: [O] links cause table misalignment

Thomas P writes: > Curious. Not even if you set your cursor on the a and press TAB again? (I > sometimes have to do it twice). > > This is what I did: > > Downloaded https://orgmode.org/org-9.1.9.zip and unzipped to ~/tmp/org-9.1.9 > > Ran: > emacs -Q > > In the scratch-buffer: > (add-to-list

Re: [O] links cause table misalignment

Curious. Not even if you set your cursor on the a and press TAB again? (I sometimes have to do it twice). This is what I did: Downloaded https://orgmode.org/org-9.1.9.zip and unzipped to ~/tmp/org-9.1.9 Ran: emacs -Q In the scratch-buffer: (add-to-list 'load-path "~/tmp/org-9.1.9/lisp") (r

Re: [O] links cause table misalignment

Hello, Thomas P writes: > With org-mode 9.1.9, my tables sometimes become misaligned when I press TAB > and the cursor is in a cell with a link. > > In an org-mode buffer, enter: > > | aa | aa | > | [[a][a]] | | > > The lower-left cell becomes misaligned when I press TAB and the cursor > is on

[O] links cause table misalignment

Hello, With org-mode 9.1.9, my tables sometimes become misaligned when I press TAB and the cursor is in a cell with a link. In an org-mode buffer, enter: | aa | aa | | [[a][a]] | | The lower-left cell becomes misaligned when I press TAB and the cursor is on the link "a". I get no misalignmen

Re: [O] links to id:

I'm a bit confused by your description of the problem. Could you describe it again with explicit reproduction steps?

[O] links to id:

I've moved my .org-id-locations file into cloud storage (similar to a dropbox folder). I set the org-id-locations-file to point to that file. I set up a link to the id. It works fine for that one session of emacs. After I quit and restart, then I click on the link it says it can't be found and a

Re: [O] links-9.0 v3

Sounds good. Thanks for your patience, I learned a lot doing this! I look forward to using it in the wild ;) Nicolas Goaziou writes: > John Kitchin writes: > >> Ok. I have attached 20 patches with the updates below. > > Applied, with minor tweaks (trailing white spaces and too wide lines). > Tha

Re: [O] links-9.0 v3

John Kitchin writes: > Ok. I have attached 20 patches with the updates below. Applied, with minor tweaks (trailing white spaces and too wide lines). Thank you for all this work. Ultimately, I removed `org--open-file-link' altogether since default behaviour for file+apps links DTRT. I also start

Re: [O] links-9.0 v3

Nicolas Goaziou writes: > John Kitchin writes: > >> I am not sure what you mean for this. Let me know if it isn't fixed in >> the attached patches. I thought I had squashed everything into a concise >> history. > > No worries. Let's just apply the 21 patches. Ok. I have attached 20 patches with

Re: [O] links-9.0 v3

John Kitchin writes: > I am not sure what you mean for this. Let me know if it isn't fixed in > the attached patches. I thought I had squashed everything into a concise > history. No worries. Let's just apply the 21 patches. > I think this code below (which should be in the patches) handles the

Re: [O] links-9.0 v3

Nicolas Goaziou writes: > Hello, > > John Kitchin writes: > >> Here are my current suggestions for the org-link 9.0. > > Thank you. I think I fixed the points you made in the previous email. > >> Let me know what the best way to send these might be. It looks like it >> might be 21 patches righ

Re: [O] links-9.0 v3

John Kitchin writes: > What do you think of this approach: > > (defcustom org-link-parameters > - '(("file" :complete 'org-file-complete-link) > -("file+emacs" :follow (lambda (path) (org-open-file path '(4 > -("file+sys" :follow (lambda (path) (org-open-file path 'system))) > + '

Re: [O] links-9.0 v3

Hello, John Kitchin writes: > Here are my current suggestions for the org-link 9.0. Thank you. > Let me know what the best way to send these might be. It looks like it > might be 21 patches right now. AFAIU, many among them introduce code that no longer exists in the final draft. It would be

Re: [O] links-9.0 v3

Here are my current suggestions for the org-link 9.0. Let me know what the best way to send these might be. It looks like it might be 21 patches right now. Thanks, 17 files changed, 187 insertions(+), 87 deletions(-) contrib/orgmanual.org | 27 + doc/org.texi | 27 + etc/O

Re: [O] links-9.0 v3

What do you think of this approach: (defcustom org-link-parameters - '(("file" :complete 'org-file-complete-link) -("file+emacs" :follow (lambda (path) (org-open-file path '(4 -("file+sys" :follow (lambda (path) (org-open-file path 'system))) + '(("file" :complete #'org-file-compl

Re: [O] links-9.0 v3

K On Friday, July 8, 2016, Nicolas Goaziou wrote: > John Kitchin > writes: > > > Here are the new revisions that implement the previous solution you > > suggested and that incorporate the commit merges as far as I can see. > > Thank you. > > > +(defcustom org-link-parameters > > + '(("file" :c

Re: [O] links-9.0 v3

John Kitchin writes: > Here are the new revisions that implement the previous solution you > suggested and that incorporate the commit merges as far as I can see. Thank you. > +(defcustom org-link-parameters > + '(("file" :complete 'org-file-complete-link) #'org-file-complete-link > +("

Re: [O] links-9.0 v3

Hello, John Kitchin writes: > I don't understand what you mean here. The contents of org-link > protocols (in master) looks a lot like a list of (link-type :follow > :export), e.g. You're right. Keys in `org-link-protocols' are types. >> (nth 1 (assoc app org-link-protocols)) > > I see that

Re: [O] links-9.0 v3

Here are the new revisions that implement the previous solution you suggested and that incorporate the commit merges as far as I can see. WDYT? commit 290213ef3eee86175d5a6b15c7b6173afd0c1616 Author: John Kitchin Date: Tue Jul 5 10:38:42 2016 -0400 Update the contrib manual diff --git a/

Re: [O] links-9.0 v3

Let me preface my reply that I think your last suggestion: > (org-link-get-parameter (if app (concat type "+" app) type) :follow) Is the thing to do for this set of changes for now. I think it would wrap up this set of changes. I will send a new set of diffs that implement this shortly after th

Re: [O] links-9.0 v3

John Kitchin writes: >> Here is the gotcha. `type' is "file", not "file+sys" or "file+emacs", >> so, when checking `dedicated-function' first, we cannot tell the >> difference between "file+sys" and "file+emacs". > > I don't follow this. Why can't these be three types? The type is "file". "sys"

Re: [O] links-9.0 v3

> > That's great. I realized there's one gotcha left. > >>(let* ((option (org-element-property :search-option link)) >> (app (org-element-property :application link)) >> (dedicated-function >> - (nth 1 (assoc app org-l

Re: [O] links-9.0 v3

Hello, John Kitchin writes: > I think I have addressed these. Revised commits appended and at > https://github.com/jkitchin/org-mode/tree/link-9.0-v3. > > The new org-link-set-parameters function you suggested works fine as far > as I can tell. WDYT? That's great. I realized there's one gotcha

Re: [O] links-9.0 v3

I think I have addressed these. Revised commits appended and at https://github.com/jkitchin/org-mode/tree/link-9.0-v3. The new org-link-set-parameters function you suggested works fine as far as I can tell. WDYT? commit f8bb180150514b92535506601c747001da305610 Author: John Kitchin Date: Tue J

Re: [O] links-9.0 v3

Thanks. I responded to some below. I didn't respond to all of them. I will revise the commits accordingly and send a new version. Nicolas Goaziou writes: > Hello, > > John Kitchin writes: > >> Your version doesn't let you add properties to links with no >> existing properties, e.g. ("http") > >

Re: [O] links-9.0 v3

Hello, John Kitchin writes: > Your version doesn't let you add properties to links with no > existing properties, e.g. ("http") There was a typo (spurious `cdr'), the correct version is (defun org-link-set-parameters (type &rest parameters) "Set link TYPE properties to PARAMETERS. PARA

[O] links-9.0 v3

I found some difficulties with the org-link-set-parameters you suggested Nick. Your version doesn't let you add properties to links with no existing properties, e.g. ("http") and it also didn't work as expected to set properties to nil. The current function is one you didn't like earlier with setf

Re: [O] links in headlines and org-bbdb-anniversaries

Kyle> I believe this is the same issue as Kyle> http://thread.gmane.org/gmane.emacs.orgmode/104539. Kyle> It's been fixed and will be available in the next ELPA build. Whoops; thanks -- I missed that. -gm -- =---= George McNinch =---= http://gmc

Re: [O] links in headlines and org-bbdb-anniversaries

Hello, George McNinch writes: > Hi-- > > I use org via ELPA. This week, the packages > > org-20160118 > org-plus-contrib-20160118 > > were replaced by > > org-20160125 > org-plus-contrib-20160125 > > After update, org began complaining about links in the headlines > which appear in my *Agend

[O] links in headlines and org-bbdb-anniversaries

Hi-- I use org via ELPA. This week, the packages org-20160118 org-plus-contrib-20160118 were replaced by org-20160125 org-plus-contrib-20160125 After update, org began complaining about links in the headlines which appear in my *Agenda*. More precisely, this was reported: > org-agenda

Re: [O] Links in headings are broken

Hello, Bruno Bigras writes: > 2016-01-26 14:58 GMT-05:00 Titus von der Malsburg : >> I think Bruno means that the TODO keywords are *not* highlighted. > > You're right. Sorry for the confusion. This was fixed yesterday. Regards, -- Nicolas Goaziou

Re: [O] Links in headings are broken

2016-01-26 14:58 GMT-05:00 Titus von der Malsburg : > I think Bruno means that the TODO keywords are *not* highlighted. You're right. Sorry for the confusion.

Re: [O] Links in headings are broken

On 2016-01-26 Tue 11:35, Bruno Bigras wrote: > I think I have the same problem. Also some "TODO" keywords are now > highlighted in some headings but it could be related. I can confirm the error messages. Also, I think Bruno means that the TODO keywords are *not* highlighted. This also affects o

Re: [O] Links in headings are broken

I think I have the same problem. Also some "TODO" keywords are now highlighted in some headings but it could be related. In the "*messages*" buffer I have: font-lock-fontify-keywords-region: Wrong type argument: listp, org-level-1Error during redisplay: (jit-lock-function 240) signaled (wrong-type

[O] Links in headings are broken

I just updated org-mode from Elpa and since then links in headings are not anymore interpreted as links. Example: * [[http://www.google.com][Google]] I’d expect to see * Google with “Google” being clickable but instead I see the complete code for the link. Links in normal text work as usual

Re: [O] Links in comments

(highlight-regexp org-ts-regexp3 'org-date)

Re: [O] Links in comments

On 10/28/15, John Kitchin wrote: > Your mileage may vary, but this seems to show links in comments for me: > > #+BEGIN_EXAMPLE > (highlight-regexp org-any-link-re 'org-link) > #+END_EXAMPLE nice workaround! thanks! it's a matter of perspective. comments mean two separate things: 1] "comment

Re: [O] Links in comments

On Wednesday, 28 Oct 2015 at 07:07, Kaushal Modi wrote: > Hi John, Eric, > > Thanks for the replies. > > I will try out the highlight-regexp trick today. > > The point I was trying to make was not that we should highlight links even > in comments (though that was my suggested alternative). The main

Re: [O] Links in comments

Hi John, Eric, Thanks for the replies. I will try out the highlight-regexp trick today. The point I was trying to make was not that we should highlight links even in comments (though that was my suggested alternative). The main point I wanted to make was that links should not get hidden in comme

Re: [O] Links in comments

Your mileage may vary, but this seems to show links in comments for me: #+BEGIN_EXAMPLE (highlight-regexp org-any-link-re 'org-link) #+END_EXAMPLE Eric S Fraga writes: > On Monday, 26 Oct 2015 at 14:13, Kaushal Modi wrote: >> Hi all, >> >> I am sending this out again in the event someone knowin

Re: [O] Links in comments

On Monday, 26 Oct 2015 at 14:13, Kaushal Modi wrote: > Hi all, > > I am sending this out again in the event someone knowing a solution to it > can comment. I don't know a solution. If I do C-u C-x = with the cursor on the link in a comment line, there is only one face shown. Semantically, the li

Re: [O] Links in comments

Hi all, I am sending this out again in the event someone knowing a solution to it can comment. -- Kaushal Modi On Mon, Oct 19, 2015 at 6:54 PM, Kaushal Modi wrote: > Hi, > > This question has come up a few times on emacs.stackexchange so I was > curious if the more experienced org-mode users

[O] Links in comments

Hi, This question has come up a few times on emacs.stackexchange so I was curious if the more experienced org-mode users had a solution to this.. or if a fix is needed to resolve this issue. Referenced emacs.stackexchange questions: - http://emacs.stackexchange.com/q/17505/115 - http://emacs.sta

Re: [O] links with italic descriptions are broken in maint

Samuel Wales writes: > please set RET to follow links and try RET. OK. This is clearer now. Fixed. Thank you. Regards,

Re: [O] links with italic descriptions are broken in maint

please set RET to follow links and try RET.

Re: [O] links with italic descriptions are broken in maint

Hello, Samuel Wales writes: > * NEXT /links with italics break/ > SCHEDULED: <2015-10-10 Sat> > :PROPERTIES: > :ID: 6fb16bf3-1e92-4ec0-b35a-0cfb2b19cd21 > :END: > > [[id:6fb16bf3-1e92-4ec0-b35a-0cfb2b19cd21][/links with italics break/]] > [[id:6fb16bf3-1e92-4ec0-b35a-0cfb2b19cd21][

[O] links with italic descriptions are broken in maint

* NEXT /links with italics break/ SCHEDULED: <2015-10-10 Sat> :PROPERTIES: :ID: 6fb16bf3-1e92-4ec0-b35a-0cfb2b19cd21 :END: [[id:6fb16bf3-1e92-4ec0-b35a-0cfb2b19cd21][/links with italics break/]] [[id:6fb16bf3-1e92-4ec0-b35a-0cfb2b19cd21][links with italics break]] -- The Kafka Pan

Re: [O] Links to Info manuals in exported HTML/LaTeX

On Thu, Aug 27, 2015 at 10:19:40AM +0200, Marcin Borkowski wrote: > Hi all, > > it seems that links to Info manuals are broken in HTML and LaTeX export > (and possibly in other backends, too). > > Would it make sense to make them work, i.e., link to the official web > versions, at least for stand

Re: [O] Links to Info manuals in exported HTML/LaTeX

Marcin Borkowski writes: > Hi all, > > it seems that links to Info manuals are broken in HTML and LaTeX export > (and possibly in other backends, too). > > Would it make sense to make them work, i.e., link to the official web > versions, at least for standard Info manuals, like Emacs manual, Elis

[O] Links to Info manuals in exported HTML/LaTeX

Hi all, it seems that links to Info manuals are broken in HTML and LaTeX export (and possibly in other backends, too). Would it make sense to make them work, i.e., link to the official web versions, at least for standard Info manuals, like Emacs manual, Elisp reference or Org manual? Best, --

Re: [O] Links

On Wed, Jun 17, 2015 at 11:47:38AM +0200, Nicolas Goaziou wrote: [... description of the issues trimmed ...] > > Although, you still have to handle the ambiguous case for existing Org > > files. Unless this double maintenance is cumbersome, I would vote for > > introducing such a scheme. > > T

Re: [O] Links, exporter

2015-06-17 12:42 GMT+02:00 Nicolas Goaziou : > Hello, > > Fabrice Popineau writes: > > > If I try to export the "Second Blog entry" subtree by C-C C-e C-s C-b h > H, > > I get a user-error because the exporter can't resolve the link which > points > > outside of the exported subtree. > > > > Is t

Re: [O] Links, exporter

Hello, Fabrice Popineau writes: > If I try to export the "Second Blog entry" subtree by C-C C-e C-s C-b h H, > I get a user-error because the exporter can't resolve the link which points > outside of the exported subtree. > > Is this expected? Yes, unresolved links/footnotes/whatever throw erro

[O] Links, exporter

Hi, I have another problem/question with links related to the exporter. I lost track of what was the behavior months ago. Assume I have something like this : * BAR :PROPERTIES: :PAGE: bar.html :END: ** First link :first: :PROPERTIES: :CUSTOM_ID: First%20link :END: Lorem ipsum dolor

Re: [O] Links

Hello, Suvayu Ali writes: > Would it make sense to "promote" these kind of encoded links to almost > their own sub-types? I would guess, almost no one enters these encoded > links by hand. It's either via copy paste in the prompt from > org-insert-link, or by entering [[encoded-link][descripti

Re: [O] Links

Hi Nicolas, Fabrice, On Tue, Jun 16, 2015 at 11:30:06PM +0200, Nicolas Goaziou wrote: > Fabrice Popineau writes: > > > Ideally, url encoded links should have been prefixed with some kind of uri > > syntax. > > This way, you could know what to decode and what not. > > The encoded link could be c

Re: [O] Links

Fabrice Popineau writes: > Ideally, url encoded links should have been prefixed with some kind of uri > syntax. > This way, you could know what to decode and what not. The encoded link could be copied from somewhere else. Also, there are numerous links in the wild without this prefix. > Now, I

Re: [O] Links

2015-06-16 14:50 GMT+02:00 Nicolas Goaziou : > Hello, > > > So, export process doesn't url-decode links, and cannot handle the link > above. This is what I was missing :-) > At this point, it seems that all is left are cheesy approaches. E.g, > when a path matches "%[A-Za-z0-9]\\{2\\}", decode

Re: [O] Links

Hello, Fabrice Popineau writes: > Assume the following file : [...] > ** First link [...] > ** Second link > [2015-06-16 mar. 13:58] > > - [[First%20link][First link]] [...] > The exporter fails to resolve the (fuzzy) link "First%20link". > However, if I click on the link, I jump to the ri

[O] Links

Hi, I think I need some refresh on what's valid and what is not. Assume the following file : #+TITLE: Foo #+DATE: 2014-11-19 01:10:58 * FOO [2015-06-16 mar. 13:58] Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec hendrerit tempor tellus. Donec pretium posuere tellus. Proin quam

Re: [O] Links in #+caption: lines

Nicolas Goaziou writes: > Rasmus writes: > >> Would it be possible to specify inheritance priority? So that e.g. link >> would retain the blue coloring? > > One solution would be to split fontification of raw keywords and blocks > OTOH and blocks that can contain Org data OTOH, as suggested by

Re: [O] Links in #+caption: lines

Rasmus writes: > Would it be possible to specify inheritance priority? So that e.g. link > would retain the blue coloring? One solution would be to split fontification of raw keywords and blocks OTOH and blocks that can contain Org data OTOH, as suggested by Kaushal (

Re: [O] Links in #+caption: lines

Nicolas Goaziou writes: > Hello, > > Rasmus writes: > >> Try the attached patch. >> >> I have done 20 second of testing (I'm traveling) so there may be adverse >> effects. But it looked OK. > > With this patch, you remove fontification from caption contents, which > is not desirable. Caption is

Re: [O] Links in #+caption: lines

Nicolas Goaziou writes: > Hello, > > Rasmus writes: > >> Try the attached patch. >> >> I have done 20 second of testing (I'm traveling) so there may be adverse >> effects. But it looked OK. > > With this patch, you remove fontification from caption contents, which > is not desirable. Caption is

Re: [O] Links in #+caption: lines

Hello, Rasmus writes: > Try the attached patch. > > I have done 20 second of testing (I'm traveling) so there may be adverse > effects. But it looked OK. With this patch, you remove fontification from caption contents, which is not desirable. Caption is an affiliated keyword and should be mark

Re: [O] Links in #+caption: lines

Hi, t...@tsdye.com (Thomas S. Dye) writes: >> In the patch I guess this is the passage you disagree with: >> >> + ((equal dc1 "+caption:") >> + (org-remove-flyspell-overlays-in (match-end 2) (match-end 0)) >> + (remove-text-properties (match-beginning 0) (match-end 0)

Re: [O] Links in #+caption: lines

Rasmus writes: > In the patch I guess this is the passage you disagree with: > > + ((equal dc1 "+caption:") > + (org-remove-flyspell-overlays-in (match-end 2) (match-end 0)) > + (remove-text-properties (match-beginning 0) (match-end 0) > +

Re: [O] Links in #+caption: lines

Hi, t...@tsdye.com (Thomas S. Dye) writes: > I don't know if it is an effect of 37d2a2d. I just tested it against 50a0e712cceeef02c0d6a7c41b619b308ea1b15c. 37d2a2d seems critical here. > I'm also seeing a different background for captions, similar to the > background the emacs 24 starter kit gi

Re: [O] Links in #+caption: lines

Aloha Rasmus, Rasmus writes: > t...@tsdye.com (Thomas S. Dye) writes: > >> Aloha all, >> >> Links in #+caption: lines are shown as literal links. IIRC, they used >> to show as descriptive links. Has this changed, or is my memory faulty? >> >> In any case, I'd like them to be descriptive links

Re: [O] Links in #+caption: lines

t...@tsdye.com (Thomas S. Dye) writes: > Aloha all, > > Links in #+caption: lines are shown as literal links. IIRC, they used > to show as descriptive links. Has this changed, or is my memory faulty? > > In any case, I'd like them to be descriptive links to keep the > > #+caption: lines as short

[O] Links in #+caption: lines

Aloha all, Links in #+caption: lines are shown as literal links. IIRC, they used to show as descriptive links. Has this changed, or is my memory faulty? In any case, I'd like them to be descriptive links to keep the #+caption: lines as short as possible. All the best, Tom -- T.S. Dye & Colle

[O] Links Drawer

Hi all, In a few functions that I use for organizing my research, I use links drawers. This enables me to write functions that automatically insert links in all entries matching particular criteria, or insert links directly from the headline or anywhere else in the entry. To do this I wrote a coupl

Re: [O] Links in tables: could the plain text also look good?

On 3/6/14 2:00 PM, Oleh wrote: I was just committing a single line change to an org-mode table into git, and the diff isn't good at all: the whole table appears to have changed. Well, not really - just a few spaces were added on each table line because the single new line caused a need to re-ali

Re: [O] Links in tables: could the plain text also look good?

Hi Oleh On Thu, Mar 6, 2014 at 8:00 PM, Oleh wrote: > I was just committing a single line change to an org-mode table into > git, and the diff isn't good at all: the whole table appears to have > changed. Well, not really - just a few spaces were added on each table > line because the single new

[O] Links in tables: could the plain text also look good?

Hi all, I don't know if this issue has been raised before (it's a bit difficult to google it). I was just committing a single line change to an org-mode table into git, and the diff isn't good at all: the whole table appears to have changed. Well, not really - just a few spaces were added on each

Re: [O] Links in node-property

Bastien writes: > Believe me, there *are* links in comments, I can see them :) > > Right now, hitting C-c C-o on this link > > # http://orgmode.org > > in an org-mode buffer produces the attached backtrace, which is > a problem /per se/ (easily fixable, I guess.) My bad. This should now be fixed

Re: [O] Links in node-property

Hi Nicolas, Nicolas Goaziou writes: > Michael Brand writes: > >> Will org-open-at-point still support links in node-property? > > No. According to Org syntax, there are no links in property drawers. > There are also no links in comments, example blocks, fixed-width > areas... Believe me, there

Re: [O] Links in node-property

Hello, Michael Brand writes: > Will org-open-at-point still support links in node-property? No. According to Org syntax, there are no links in property drawers. There are also no links in comments, example blocks, fixed-width areas... Regards, -- Nicolas Goaziou

[O] Links in node-property

Hi Nicolas Will org-open-at-point still support links in node-property? :PROPERTIES: :ID: 24ac0164-3c4f-4792-93ac-aaae68a19632 :related: [[id:15763c8f-f022-486e-9449-bac56f7aa028]] :features: http://orgmode.org/features.html :doc: http://orgmode.org/org.html :END: Michael

Re: [O] Links sorting and exporting.

Hi Matthew, Matthew Sauer writes: > What I am thinking is of a way to save a web bookmark in a file or > two and then based on meta-tag have them exported into a html file. >  In other words, if I have a file with bookmarks that has tags: > apple, fruit, orange, dog, horse, pet, animal, etc then

Re: [O] Links sorting and exporting.

Bastien, What I am thinking is of a way to save a web bookmark in a file or two and then based on meta-tag have them exported into a html file. In other words, if I have a file with bookmarks that has tags: apple, fruit, orange, dog, horse, pet, animal, etc then it would create a html page named

Re: [O] Links sorting and exporting.

Hi Matthew, Matthew Sauer writes: > Thoughts on this? I didn't get the idea. Can you restate it with a few words? Thanks! -- Bastien

[O] Links sorting and exporting.

I have conceived of an idea that I want to build into the ORG framework. The problem I am trying to solve: I have a variety of links that I use on a regular basis. I am wanting to be able to invoke a link generation command that will store them in a bookmarks.org file (or it could be a user defin

Re: [O] links and anchors

On Fri, Dec 27, 2013 at 4:59 PM, Nicolas Goaziou wrote: > Hello, > > Rustom Mody writes: > >> Context is html export >> >> I have a file of quotes like the following >> -- >> * Declarative vs Imperative >> Never tell people how to do things. Tell them what to do and they will >>

Re: [O] links and anchors

Hello, Rustom Mody writes: > Context is html export > > I have a file of quotes like the following > -- > * Declarative vs Imperative > Never tell people how to do things. Tell them what to do and they will > surprise you with their ingenuity \\ > General G.S.Patton (1941) > --

[O] links and anchors

Context is html export I have a file of quotes like the following -- * Declarative vs Imperative Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity \\ General G.S.Patton (1941) - which I link from another file

Re: [O] Links to headings not generated in Tables

Ok. I feel quite quite silly now. Thanks /Luke On Thu, Dec 19, 2013 at 12:48 PM, Nicolas Goaziou wrote: > Hello, > > Luke Crook writes: > > > What about the following code. In the following, <<1>> and <<2>> are not > > appearing in the HTML or the Latex exorts. > > > > > > > > * test > >

Re: [O] Links to headings not generated in Tables

Hello, Luke Crook writes: > What about the following code. In the following, <<1>> and <<2>> are not > appearing in the HTML or the Latex exorts. > > > > * test > One, [[1]] and two, [[2]]. > > > * blee > > | ID| Descr | Descr | > |---+---+---| > | <<1>> | One | One | > |

Re: [O] Links to headings not generated in Tables

Here is the html export. The anchor is generated, but with no text. ID Descr Descr One One Two Two On Thu, Dec 19, 2013 at 11:12 AM, Luke Crook wrote: > Hi Nicolas, > > What about the following code. In the following, <<1>> and <<2>> are not > appearing in the HTML or the La

Re: [O] Links to headings not generated in Tables

Hi Nicolas, What about the following code. In the following, <<1>> and <<2>> are not appearing in the HTML or the Latex exorts. * test One, [[1]] and two, [[2]]. * blee | ID| Descr | Descr | |---+---+---| | <<1>> | One | One | | <<2>> | Two | Two | On Thu, Nov 2

  1   2   >