Re: [O] Bug: link formating problem [9.0.5 (9.0.5-elpaplus @ /Users/mistkafka/.emacs.d/elpa/org-plus-contrib-20170210/)]
Nicolas Goaziou writes: > Hello, > > Chunyang Xu writes: > >> I changed `org-plain-link-re' to make it not longer think "[" and "]" >> are valid characters in a URL, which solves the problem. > > Thank you. > > I solved the problem differently, but your suggestion still makes sense. > Would you mind making it a proper patch, using "git format-patch", with > a proper commit message? Don't forget to add TINYCHANGE cookie at the > end if you haven't signed papers yet. Here is the patch. >From c0b86176dc99f63385bcebc1ccbcb5d41f062a2c Mon Sep 17 00:00:00 2001 From: Chunyang Xu Date: Sun, 28 May 2017 12:10:58 +0800 Subject: [PATCH] Exclude '[' and ']' in `org-plain-link-re' * lisp/org.el (org-make-link-regexps): Do it. TINYCHANGE --- lisp/org.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/org.el b/lisp/org.el index 102a9b265..c2818299e 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -5687,7 +5687,7 @@ This should be called after the variable `org-link-parameters' has changed." org-plain-link-re (concat "\\<" types-re ":" - "\\([^ \t\n()<>]+\\(?:([[:word:]0-9_]+)\\|\\([^[:punct:] \t\n]\\|/\\)\\)\\)") + "\\([^][ \t\n()<>]+\\(?:([[:word:]0-9_]+)\\|\\([^[:punct:] \t\n]\\|/\\)\\)\\)") ;; "\\([^]\t\n\r<>() ]+[^]\t\n\r<>,.;() ]\\)") org-bracket-link-regexp "\\[\\[\\([^][]+\\)\\]\\(\\[\\([^][]+\\)\\]\\)?\\]" -- 2.13.0 > Regards, > > -- > Nicolas Goaziou
Re: [O] Git repository error
I'm not sure why, but I was being redirected to port 443 when cloning over the git:// protocol. $ git clone -v git://orgmode.org/org-mode.git Cloning into 'org-mode'... fatal: unable to access 'https://orgmode.org/org-mode.git/': Failed to connect to orgmode.org port 443: Connection timed out I enabled port 443. Please see if it works now. If you're behind a restrictive firewall, you can use http://orgmode.org/org-mode.git Regards, Jason On Sat, May 27, 2017 at 5:47 PM, Leslie Watter wrote: > I can reproduce the same behaviour here: > > leslie@colossus:~/scm$ git clone git://orgmode.org/w/org-mode.git org-git > Cloning into 'org-git'... > fatal: read error: Conexão fechada pela outra ponta > > leslie@colossus:~/scm$ git clone git://orgmode.org/org-mode.git org-git > Cloning into 'org-git'... > fatal: read error: Conexão fechada pela outra ponta > > leslie@colossus:~/scm$ git clone git://repo.or.cz/org-mode.git org-git > Cloning into 'org-git'... > remote: Counting objects: 106847, done. > Receiving objects: 5% (6155/106847), 1.57 MiB | 27.00 KiB/s > . > > > > Cheers > > Leslie > > > On Sat, May 27, 2017 at 5:50 PM, John Hendy wrote: > >> On Thu, May 25, 2017 at 6:10 PM, Vicente Vera >> wrote: >> > Hi. For a while i've been getting this error upon running 'make up0' >> > from my local Org repository: >> > >> > fatal: read error: Connection reset by peer >> >> I pulled just the other day and it worked, but I use http because git >> doesn't work for me behind my corporate firewall. >> >> $ git remote -v >> origin http://orgmode.org/org-mode.git (fetch) >> origin http://orgmode.org/org-mode.git (push) >> >> I just cloned via http successfully, but get the "reset by peer" >> message via git protocol (with or without the /w/ in the URL other's >> have mentioned): >> >> $ git clone git://orgmode.org/w/org-mode.git org-git >> Cloning into 'org-git'... >> fatal: read error: Connection reset by peer >> >> $ git clone git://orgmode.org/org-mode.git org-git >> Cloning into 'org-git'... >> fatal: read error: Connection reset by peer >> >> Something must be up with the main site. The mirror works: >> >> $ git clone git://repo.or.cz/org-mode.git org-git >> Cloning into 'org-git'... >> remote: Counting objects: 106847, done. >> remote: Total 106847 (delta 0), reused 0 (delta 0) >> Receiving objects: 100% (106847/106847), 80.33 MiB | 572.00 KiB/s, done. >> Resolving deltas: 100% (83923/83923), done. >> >> >> >> John >> >> > > > -- > Leslie H. Watter >
Re: [O] Git repository error
I can reproduce the same behaviour here: leslie@colossus:~/scm$ git clone git://orgmode.org/w/org-mode.git org-git Cloning into 'org-git'... fatal: read error: Conexão fechada pela outra ponta leslie@colossus:~/scm$ git clone git://orgmode.org/org-mode.git org-git Cloning into 'org-git'... fatal: read error: Conexão fechada pela outra ponta leslie@colossus:~/scm$ git clone git://repo.or.cz/org-mode.git org-git Cloning into 'org-git'... remote: Counting objects: 106847, done. Receiving objects: 5% (6155/106847), 1.57 MiB | 27.00 KiB/s . Cheers Leslie On Sat, May 27, 2017 at 5:50 PM, John Hendy wrote: > On Thu, May 25, 2017 at 6:10 PM, Vicente Vera > wrote: > > Hi. For a while i've been getting this error upon running 'make up0' > > from my local Org repository: > > > > fatal: read error: Connection reset by peer > > I pulled just the other day and it worked, but I use http because git > doesn't work for me behind my corporate firewall. > > $ git remote -v > origin http://orgmode.org/org-mode.git (fetch) > origin http://orgmode.org/org-mode.git (push) > > I just cloned via http successfully, but get the "reset by peer" > message via git protocol (with or without the /w/ in the URL other's > have mentioned): > > $ git clone git://orgmode.org/w/org-mode.git org-git > Cloning into 'org-git'... > fatal: read error: Connection reset by peer > > $ git clone git://orgmode.org/org-mode.git org-git > Cloning into 'org-git'... > fatal: read error: Connection reset by peer > > Something must be up with the main site. The mirror works: > > $ git clone git://repo.or.cz/org-mode.git org-git > Cloning into 'org-git'... > remote: Counting objects: 106847, done. > remote: Total 106847 (delta 0), reused 0 (delta 0) > Receiving objects: 100% (106847/106847), 80.33 MiB | 572.00 KiB/s, done. > Resolving deltas: 100% (83923/83923), done. > > > > John > > -- Leslie H. Watter
Re: [O] Git repository error
Dear Luke, > "Luke" == Luke writes: Luke> On 26/05/17 15:39, claude fuhrer wrote: >> Hello everybody >> >> >> On 26/05/17 01:10, Vicente Vera wrote: >>> Hi. For a while i've been getting this error upon running 'make >>> up0' from my local Org repository: >>> >>> fatal: read error: Connection reset by peer >> I have the same error for every pull, fetch or clone operation. I >> don't think that it is a problem with my network connection since >> I can easily sync other project on github.What have I done wrong >> ? >> >> thank you in advance for your help >> Luke> Same here. I've noticed that when I use my web browser to try Luke> and access http://orgmode.org/org-mode.git I get a "403 Luke> Forbidden" response. Luke> However, I *can* view http://orgmode.org/w/org-mode.git (note Luke> the extra "w" in the address). Has the repo location changed? Probably not. An attempted git clone into orgmode.org/w/org-mode.git gives the same type of error, as reported here, as we are getting from a git pull from git://orgmode.org/org-mode.git. Best wishes, Colin. -- -- Colin Baxter m43...@yandex.com GnuPG fingerprint: 68A8 799C 0230 16E7 BF68 2A27 BBFA 2492 91F5 41C8
Re: [O] Error exporting org-ref.org to LaTeX (was: Re: Warnings while installing org-ref)
You might have to require org-id and a few other org-ref libs for wos, Scopus and arxiv links. See the notes near the end of that document. I am traveling sans emacs right now so I don't have the exact place to look, but it is in a section on alternate builds I think. On Sat, May 27, 2017 at 4:52 PM Lars Bjørndal wrote: > On Fri, May 26, 2017 at 04:06:52PM -0400, John Kitchin wrote: > > I pushed a bunch of commits today to clean up a lot of these. There are > > still a few that I don't know how to get rid of, but it should be a lot > > cleaner now. > > Thanks a lot. > > To learn Org, Org-ref and exports, I tried to export the org-ref.org > to LaTeX. The .tex file is produced, but I get the following error > message: > > user-error: Unable to resolve link: > "id:212B487E-CC38-4BDF-9F0E-6993845AF49B" > > What does that mean? > > Thanks and regards, Lars > > > Lars Bjørndal writes: > > > > > I installed org-ref from Elpa, and I got some warnings. Emacs version: > > > > > > GNU Emacs 25.2.1 (x86_64-redhat-linux-gnu, GTK+ Version 3.20.10) of > 2017-05-02 > > > > > > I'm not sure how critical these error messages are. > > > > > > Fri May 26 14:59:37 2017 > > > Entering directory `/home/tstl/.emacs.d/elpa/key-chord-20160227.438/' > > > > > > In key-chord-input-method: > > > key-chord.el:341:16:Warning: sit-for called with 3 arguments, but > > > accepts only > > > 1-2 > > > i May 26 14:59:45 2017 > > > Entering directory `/home/tstl/.emacs.d/elpa/helm-core-20170526.36/' > > > > > > In helm-position: > > > helm-lib.el:388:14:Warning: macro `helm-position' defined too late > > > > > > In end of data: > > > helm-lib.el:1006:1:Warning: the following functions are not known to be > > > defined\ > > > : > > > helm-interpret-value, helm-get-current-source > > > > > > Compiling file > > > /home/tstl/.emacs.d/elpa/helm-bibtex-20170321.1306/bibtex-comple\ > > > tion.el at Fri May 26 14:59:54 2017 > > > Entering directory > `/home/tstl/.emacs.d/elpa/helm-bibtex-20170321.1306/' > > > > > > In end of data: > > > bibtex-completion.el:1210:1:Warning: the following functions are not > > > known to b\ > > > e defined: > > > reftex-what-macro, org-find-property, > > > reftex-locate-bibliography-files > > > > > > Entering directory `/home/tstl/.emacs.d/elpa/org-ref-20170523.1821/' > > > > > > In end of data: > > > doi-utils.el:1361:1:Warning: the following functions are not known to > be > > > define\ > > > d: > > > org-ref-find-bibliography, reftex-get-bib-field, > > > org-ref-bib-citation > > > > > > Compiling file > > > /home/tstl/.emacs.d/elpa/org-ref-20170523.1821/org-ref-bibtex.el\ > > > at Fri May 26 14:59:57 2017 > > > > > > In org-ref-bibtex-assoc-pdf-with-entry: > > > org-ref-bibtex.el:728:25:Warning: reference to free variable > > > `org-ref-pdf-directory' > > > > > > In orhc-bibtex-field-formatter: > > > org-ref-bibtex.el:1092:27:Warning: reference to free variable > > > `org-ref-pdf-directory' > > > org-ref-bibtex.el:1098:27:Warning: reference to free variable > > > `org-ref-notes-directory' > > > > > > In end of data: > > > org-ref-bibtex.el:1324:1:Warning: the following functions are not known > > > to be d\ > > > efined: > > > reftex-get-bib-field, org-ref-find-bibliography > > > > > > Compiling file > > > /home/tstl/.emacs.d/elpa/org-ref-20170523.1821/org-ref-citeproc.\ > > > el at Fri May 26 14:59:57 2017 > > > > > > In end of data: > > > org-ref-citeproc.el:919:1:Warning: the function > > > `org-ref-get-bibtex-key-and-file' is not known to be defined. > > > > > > Compiling file > > > /home/tstl/.emacs.d/elpa/org-ref-20170523.1821/org-ref-core.el a\ > > > t Fri May 26 14:59:57 2017 > > > > > > In org-ref-update-pre-post-text: > > > org-ref-core.el:3259:16:Warning: `delete-backward-char' is for > > > interactive use > > > only; use `delete-char' instead. > > > org-ref-core.el:3260:12:Warning: `delete-backward-char' is for > > > interactive use > > > only; use `delete-char' instead. > > > > > > In end of data: > > > org-ref-core.el:3498:1:Warning: the following functions are not known > to > > > be def\ > > > ined: > > > org-ref-match-next-cite-link, org-ref-match-next-label-link, > > > org-ref-match-next-ref-link, > > > org-ref-make-org-link-cite-key-visible, > > > org-in-commented-heading-p > > > > > > Compiling file > > > /home/tstl/.emacs.d/elpa/org-ref-20170523.1821/org-ref-helm-bibt\ > > > ex.el at Fri May 26 14:59:58 2017 > > > > > > In org-ref-format-citation: > > > org-ref-helm-bibtex.el:308:22:Warning: assignment to free variable > `end' > > > org-ref-helm-bibtex.el:313:37:Warning: assignment to free variable > > > `path' > > > org-ref-helm-bibtex.el:313:37:Warning: reference to free variable `end' > > > org-ref-helm-bibtex.el:311:16:Warning: looking-back called with 1 > > > argument, > > > but requires 2-3 > > > org-ref-helm-bibtex.el:313:18:Warning: reference to free variable
[O] Error exporting org-ref.org to LaTeX (was: Re: Warnings while installing org-ref)
On Fri, May 26, 2017 at 04:06:52PM -0400, John Kitchin wrote: > I pushed a bunch of commits today to clean up a lot of these. There are > still a few that I don't know how to get rid of, but it should be a lot > cleaner now. Thanks a lot. To learn Org, Org-ref and exports, I tried to export the org-ref.org to LaTeX. The .tex file is produced, but I get the following error message: user-error: Unable to resolve link: "id:212B487E-CC38-4BDF-9F0E-6993845AF49B" What does that mean? Thanks and regards, Lars > Lars Bjørndal writes: > > > I installed org-ref from Elpa, and I got some warnings. Emacs version: > > > > GNU Emacs 25.2.1 (x86_64-redhat-linux-gnu, GTK+ Version 3.20.10) of > > 2017-05-02 > > > > I'm not sure how critical these error messages are. > > > > Fri May 26 14:59:37 2017 > > Entering directory `/home/tstl/.emacs.d/elpa/key-chord-20160227.438/' > > > > In key-chord-input-method: > > key-chord.el:341:16:Warning: sit-for called with 3 arguments, but > > accepts only > > 1-2 > > i May 26 14:59:45 2017 > > Entering directory `/home/tstl/.emacs.d/elpa/helm-core-20170526.36/' > > > > In helm-position: > > helm-lib.el:388:14:Warning: macro `helm-position' defined too late > > > > In end of data: > > helm-lib.el:1006:1:Warning: the following functions are not known to be > > defined\ > > : > > helm-interpret-value, helm-get-current-source > > > > Compiling file > > /home/tstl/.emacs.d/elpa/helm-bibtex-20170321.1306/bibtex-comple\ > > tion.el at Fri May 26 14:59:54 2017 > > Entering directory `/home/tstl/.emacs.d/elpa/helm-bibtex-20170321.1306/' > > > > In end of data: > > bibtex-completion.el:1210:1:Warning: the following functions are not > > known to b\ > > e defined: > > reftex-what-macro, org-find-property, > > reftex-locate-bibliography-files > > > > Entering directory `/home/tstl/.emacs.d/elpa/org-ref-20170523.1821/' > > > > In end of data: > > doi-utils.el:1361:1:Warning: the following functions are not known to be > > define\ > > d: > > org-ref-find-bibliography, reftex-get-bib-field, > > org-ref-bib-citation > > > > Compiling file > > /home/tstl/.emacs.d/elpa/org-ref-20170523.1821/org-ref-bibtex.el\ > > at Fri May 26 14:59:57 2017 > > > > In org-ref-bibtex-assoc-pdf-with-entry: > > org-ref-bibtex.el:728:25:Warning: reference to free variable > > `org-ref-pdf-directory' > > > > In orhc-bibtex-field-formatter: > > org-ref-bibtex.el:1092:27:Warning: reference to free variable > > `org-ref-pdf-directory' > > org-ref-bibtex.el:1098:27:Warning: reference to free variable > > `org-ref-notes-directory' > > > > In end of data: > > org-ref-bibtex.el:1324:1:Warning: the following functions are not known > > to be d\ > > efined: > > reftex-get-bib-field, org-ref-find-bibliography > > > > Compiling file > > /home/tstl/.emacs.d/elpa/org-ref-20170523.1821/org-ref-citeproc.\ > > el at Fri May 26 14:59:57 2017 > > > > In end of data: > > org-ref-citeproc.el:919:1:Warning: the function > > `org-ref-get-bibtex-key-and-file' is not known to be defined. > > > > Compiling file > > /home/tstl/.emacs.d/elpa/org-ref-20170523.1821/org-ref-core.el a\ > > t Fri May 26 14:59:57 2017 > > > > In org-ref-update-pre-post-text: > > org-ref-core.el:3259:16:Warning: `delete-backward-char' is for > > interactive use > > only; use `delete-char' instead. > > org-ref-core.el:3260:12:Warning: `delete-backward-char' is for > > interactive use > > only; use `delete-char' instead. > > > > In end of data: > > org-ref-core.el:3498:1:Warning: the following functions are not known to > > be def\ > > ined: > > org-ref-match-next-cite-link, org-ref-match-next-label-link, > > org-ref-match-next-ref-link, > > org-ref-make-org-link-cite-key-visible, > > org-in-commented-heading-p > > > > Compiling file > > /home/tstl/.emacs.d/elpa/org-ref-20170523.1821/org-ref-helm-bibt\ > > ex.el at Fri May 26 14:59:58 2017 > > > > In org-ref-format-citation: > > org-ref-helm-bibtex.el:308:22:Warning: assignment to free variable `end' > > org-ref-helm-bibtex.el:313:37:Warning: assignment to free variable > > `path' > > org-ref-helm-bibtex.el:313:37:Warning: reference to free variable `end' > > org-ref-helm-bibtex.el:311:16:Warning: looking-back called with 1 > > argument, > > but requires 2-3 > > org-ref-helm-bibtex.el:313:18:Warning: reference to free variable > > `path' > > > > In org-ref-helm-load-completions-async: > > org-ref-helm-bibtex.el:367:22:Warning: assignment to free variable > > `bibtex-completion-cached-candidates' > > org-ref-helm-bibtex.el:371:20:Warning: assignment to free variable > > `bibtex-completion-bibliography-hash' > > > > In org-ref-browser: > > org-ref-helm-bibtex.el:681:20:Warning: `show-all' is an obsolete > > function (as > > of 25.1); use `outline-show-all' instead. > > org-ref-helm-bibtex.el:712:61:Warning: assignment to free variable > > `count-key-pos' > >
Re: [O] Git repository error
On Thu, May 25, 2017 at 6:10 PM, Vicente Vera wrote: > Hi. For a while i've been getting this error upon running 'make up0' > from my local Org repository: > > fatal: read error: Connection reset by peer I pulled just the other day and it worked, but I use http because git doesn't work for me behind my corporate firewall. $ git remote -v origin http://orgmode.org/org-mode.git (fetch) origin http://orgmode.org/org-mode.git (push) I just cloned via http successfully, but get the "reset by peer" message via git protocol (with or without the /w/ in the URL other's have mentioned): $ git clone git://orgmode.org/w/org-mode.git org-git Cloning into 'org-git'... fatal: read error: Connection reset by peer $ git clone git://orgmode.org/org-mode.git org-git Cloning into 'org-git'... fatal: read error: Connection reset by peer Something must be up with the main site. The mirror works: $ git clone git://repo.or.cz/org-mode.git org-git Cloning into 'org-git'... remote: Counting objects: 106847, done. remote: Total 106847 (delta 0), reused 0 (delta 0) Receiving objects: 100% (106847/106847), 80.33 MiB | 572.00 KiB/s, done. Resolving deltas: 100% (83923/83923), done. John
Re: [O] Bug: link formating problem [9.0.5 (9.0.5-elpaplus @ /Users/mistkafka/.emacs.d/elpa/org-plus-contrib-20170210/)]
Chunyang Xu writes: > Sure, I will do that when it is possible (Right now, I can not git-clone > org-mode's repository, > > ~$ git clone git://orgmode.org/org-mode.git > Cloning into 'org-mode'... > fatal: read error: Connection reset by peer Cloning via http still works, so try that instead. > and the mirror at http://repo.or.cz/w/org-mode.git is also outdated for > about 4 days). That most likely hits the same problem, which seems to be with the orgmode.org server. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
Re: [O] Bug: link formating problem [9.0.5 (9.0.5-elpaplus @ /Users/mistkafka/.emacs.d/elpa/org-plus-contrib-20170210/)]
Nicolas Goaziou writes: > Hello, > > Chunyang Xu writes: > >> I changed `org-plain-link-re' to make it not longer think "[" and "]" >> are valid characters in a URL, which solves the problem. > > Thank you. > > I solved the problem differently, but your suggestion still makes sense. > Would you mind making it a proper patch, using "git format-patch", with > a proper commit message? Don't forget to add TINYCHANGE cookie at the > end if you haven't signed papers yet. Sure, I will do that when it is possible (Right now, I can not git-clone org-mode's repository, ~$ git clone git://orgmode.org/org-mode.git Cloning into 'org-mode'... fatal: read error: Connection reset by peer and the mirror at http://repo.or.cz/w/org-mode.git is also outdated for about 4 days). > Regards, > > -- > Nicolas Goaziou
Re: [O] :placement documentation imprecise
You are right. I'm sorry. It works with :float, but not with :placement. I misread the documentation. Thanks for the answer! On 2017-05-26 23:52, Nicolas Goaziou wrote: Hello, ed...@openmail.cc writes: But, if I use sideways alone (not sidewaystable), the table is not rotated. I cannot reproduce it. With the following document #+attr_latex: :float sideways | a | b | the table is rotated, according to the following code: \begin{sidewaystable}[htbp] \centering \begin{tabular}{ll} \toprule a & b\\ \bottomrule \end{tabular} Regards, - ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!
Re: [O] clock-table property column empty
Hello, Nikolay Kudryavtsev writes: > Is there any way to get the old behavior back? I think it made more sense. The old behavior was buggy and inconsistent, but I understand what you mean. I fixed this in maint. Thank you. Regards, -- Nicolas Goaziou
Re: [O] Bug: link formating problem [9.0.5 (9.0.5-elpaplus @ /Users/mistkafka/.emacs.d/elpa/org-plus-contrib-20170210/)]
On Fri, May 26, 2017 at 6:04 AM Nicolas Goaziou wrote: > I solved the problem differently, but your suggestion still makes sense. > Would you mind making it a proper patch, using "git format-patch", with > a proper commit message? Don't forget to add TINYCHANGE cookie at the > end if you haven't signed papers yet. > Thanks. After the fix in http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=2d29269bb1b9af08011e091913798b6598e4b156, I don't need that org-highlight-links workaround any more. -- Kaushal Modi
Re: [O] A possibly useful thing
You can make it a minor-mode and publish on MELPA. I found it on Emacs Planet some days ago. I use it. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Fri, May 26, 2017 at 9:08 PM, Tom Hinton wrote: > Hi, > > I made a thing, visible here: > > https://github.com/larkery/emacs/blob/master/site-lisp/ > org-numbers-overlay.el > > Which adds overlays to headings in org-mode to display section numbering > in the buffer, and keeps it up to date as you edit. This helps me when > relating exported PDF output (or people's comments on it) back to the > original org file. > > Anyway it turns out it was helpful to some other people too, and one of > them suggested that I contribute it directly and that to do so I should > email this address, and now here we are. > > Let me know if this fits into the org development master plan. > > Thanks, > > Tom Hinton > >