Re: [O] Git repository error

[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

Same here. I've noticed that when I use my web browser to try and access 
http://orgmode.org/org-mode.git I get a "403 Forbidden" response.


However, I *can* view http://orgmode.org/w/org-mode.git (note the extra 
"w" in the address). Has the repo location changed?


--
Luke

Re: [O] :placement documentation imprecise

[Nicolas Goaziou]

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,

-- 
Nicolas Goaziou

[O] syncing with Emacs (was: Fix org.el compilation warnings)

[Kyle Meyer]

Kaushal Modi  writes:

> (About that, I'd like to help syncing the org on emacs master with org
> 9.0.7 if I can.)

Rasmus was working on it the last time it came up.  I'm not sure what
the status of that is.

Each Org release, I've been updating the emacs-sync branch.  This branch
is a superset of the last release, with a few changes that I think are
appropriate for syncing with Emacs.  You can see these with

git log --oneline --no-merges release_9.0.7..origin/emacs-sync

As far as backports, maint should be up to date, though I haven't
checked since last Sunday.  And based on the output of

git log --oneline release_9.0.7..origin/maint

it seems that the last release includes all of the backports.

-- 
Kyle

Re: [O] Fix org.el compilation warnings

[Kaushal Modi]

On Fri, May 26, 2017, 4:45 PM Kyle Meyer  wrote:

>
> When I run byte-compile-file on org.el (no Org loaded, with master's Org
> first on the load-path), I don't see any of the above warnings aside
> from the one for org-agenda-include-inactive-timestamps, which is fixed
> by the patch.  And because running byte-compile-file from an Emacs
> instance is affected by what's already been loaded, I think it's better
> to focus on the output of 'make single'.
>

I thought that mixed org versions on load path could cause this. So I
checked the old org that ships with emacs master (About that, I'd like to
help syncing the org on emacs master with org 9.0.7 if I can.), but I didnt
find the function signature discrepancy as the warnings indicate.

So just for understanding, would like to know the root cause of those
warnings.

But yes, for true compilation checks, I'll start using make single.

Thanks.

> --

Kaushal Modi

Re: [O] Fix org.el compilation warnings

[Kyle Meyer]

Kaushal Modi  writes:

>> Ah, right ... 'make compile' uses a single Emacs instance, while 'make
>> single' uses a separate Emacs instance for each file.
>
> I wasn't even doing that. I was doing M-x byte-compile-file and selecting
> org.el.

Sure, I was just noting why I didn't see the
org-agenda-include-inactive-timestamps warning when I ran 'make
compile'.  .

> That gives me (without applying your patch):
>
> Compiling file
> /home/kmodi/stow/pub_dotfiles/emacs/dot-emacs.d/elisp/org-mode/lisp/org.el
> at Fri May 26 14:04:52 2017
>
> In org-goto-map:
> org.el:7412:9:Warning: function org-goto-map used to take 0+ arguments, now
> takes 0
>
> In org-todo:
> org.el:12398:12:Warning: function org-todo used to take 0+ arguments, now
> takes 0-1
>
> In org-store-log-note:
> org.el:13635:8:Warning: function org-store-log-note used to take 0+
> arguments,
> now takes 0
>
> In org-at-timestamp-p:
> org.el:17909:40:Warning: reference to free variable
> ‘org-agenda-include-inactive-timestamps’
>
> In org-self-insert-command:
> org.el:19910:32:Warning: function org-self-insert-command used to take 0+
> arguments, now takes 1
>
> So.. should we consider the warnings output by simple byte-compile-file?

When I run byte-compile-file on org.el (no Org loaded, with master's Org
first on the load-path), I don't see any of the above warnings aside
from the one for org-agenda-include-inactive-timestamps, which is fixed
by the patch.  And because running byte-compile-file from an Emacs
instance is affected by what's already been loaded, I think it's better
to focus on the output of 'make single'.

-- 
Kyle

Re: [O] Allow #+SETUPFILE to point to an URL for the org file

[Kaushal Modi]

Thanks for another round of review.

I have attached a patch, rebased to master and with all suggestions
implemented.

There are some additional changes in the patch this time:
- Prevent org-edit-special from attempting to open the "file" for editing
if the value is a URL.
- Silence byte-compiler for ffap-url-regexp. We do a require, but the
byte-compiler still complains of a free variable.
- Update org.texi at few places (first time editing a texi)

On Fri, May 26, 2017 at 3:47 AM Nicolas Goaziou 
wrote:

> I understand the use case for `org-file-clear-cache'. My suggestion is
> to remove that need by clearing cache automatically. Of course, the
> drawback is the cache is cleared more often than necessary. Users could
> get very surprising results if they forget to call this function. So it
> might be a good idea to call it from time to time, on user's behalf.
>

I liked your C-c C-c idea below! :)


> `org-file-contents' is a developer-facing function. I don't really see
> a good place in the manual for it. That's the problem of
> `org-file-clear-cache', which is really an implementation detail users
> shouldn't care about.
>

Understood.


> Here's another idea: call it from `org-mode-restart'. So cache is reset
> whenever `C-c C-c' is pressed on a keyword. So we don't need to document
> the function anymore. Instead, we could drop a note about the cache in
> (info "(org) The very busy C-c C-c key").
>

Done!


> OK. Then the following at least doesn't have the overhead of creating
> a string:
>

Integrated. Thanks!

Also, mind the full stop at the end of the comments.
>

Will do.
-- 

Kaushal Modi


0001-Allow-org-file-contents-to-fetch-file-contents-from-.patch
Description: Binary data

Re: [O] Warnings while installing org-ref

[John Kitchin]

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.

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'
> org-ref-helm-bibtex.el:715:68:Warning: reference to free
> variable
> `count-key-pos'
>
> Compiling file
> /home/tstl/.emacs.d/elpa/org-ref-20170523.1821/org-ref-helm.el a\
> t Fri May 26 14:59:58 2017
>
> In org-ref:
> org-ref-helm.el:289:78:Error: `add-to-list' can't use lexical var
> `matches';
> use `push' or `cl-pushnew'
> org-ref-helm.el:317:54:Error: `add-to-list' can't use lexical var
> `matches';
> use `push' or `cl-pushnew'
> org-ref-helm.el:306:39:Error: `add-to-list' can't use lexical
> var `matches';
> use `push' or `cl-pu

Re: [O] Fix org.el compilation warnings

[Kaushal Modi]

Below update is after I updated to the latest org master:

On Thu, May 25, 2017 at 10:53 PM Kyle Meyer  wrote:

> Ah, right ... 'make compile' uses a single Emacs instance, while 'make
> single' uses a separate Emacs instance for each file.
>

I wasn't even doing that. I was doing M-x byte-compile-file and selecting
org.el.

That gives me (without applying your patch):

Compiling file
/home/kmodi/stow/pub_dotfiles/emacs/dot-emacs.d/elisp/org-mode/lisp/org.el
at Fri May 26 14:04:52 2017

In org-goto-map:
org.el:7412:9:Warning: function org-goto-map used to take 0+ arguments, now
takes 0

In org-todo:
org.el:12398:12:Warning: function org-todo used to take 0+ arguments, now
takes 0-1

In org-store-log-note:
org.el:13635:8:Warning: function org-store-log-note used to take 0+
arguments,
now takes 0

In org-at-timestamp-p:
org.el:17909:40:Warning: reference to free variable
‘org-agenda-include-inactive-timestamps’

In org-self-insert-command:
org.el:19910:32:Warning: function org-self-insert-command used to take 0+
arguments, now takes 1

With 'make single' on master, I get a compile error due to the
> eval-when-compile's added in 53ee147f4 (Add support for new switches to
> org-get-heading, 2017-01-17) and 6dc6eb3b0 (Fix failing test,
> 2017-01-19).


> In toplevel form:
> org.el:7914:51:Error: Symbol’s value as variable is void:
> org-comment-string
>

I get that too.


> Your patch is only the appropriate fix if we're confident that
> org-agenda will be loaded at the time that the
> org-agenda-include-inactive-timestamps code path of org-at-timestamp-p
> is executed.  Otherwise, we're just silencing a warning about a possible
> run-time void variable error.  Have you looked this?


No, I didn't.. your bound-and-true-p patch makes more sense.

So.. should we consider the warnings output by simple byte-compile-file?
Even if not, the warnings do not make sense.. just taking this example:

In org-goto-map:
org.el:7412:9:Warning: function org-goto-map used to take 0+ arguments, now
takes 0

Nowhere is org-goto-map defined to take 0+ arguments (meaning have
"&optional arg" as signature) and then redefined to have 0 arguments (which
is the actual case). Wondering why the compiler thinks that. I had a quick
look at byte-compile-arglist-warn function that outputs this warning.. but
couldn't understand the logic for sig1 in there.
-- 

Kaushal Modi

Re: [O] clock-table property column empty

[Nikolay Kudryavtsev]

Is there any way to get the old behavior back? I think it made more sense.

Also, I got to the reason why I was getting those cryptic prompts. It's 
actually a bug in icicles package, that for some reason misfires 
functionality meant for integrating the anything package, which I don't 
even use. Gonna go report that...


--
Best Regards,
Nikolay Kudryavtsev

Re: [O] Git repository error

[Marcin Borkowski]

On 2017-05-26, at 14:08, Charles Millar  wrote:

> HI,
>
>>> On 26/05/17 01:10, Vicente Vera wrote:

 fatal: read error: Connection reset by peer
>>>
> Same here - since yesterday morning.

Me too.

-- 
Marcin Borkowski

Re: [O] Warnings while installing org-ref

[John Kitchin]

I don't think any of those are critical.

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'
> org-ref-helm-bibtex.el:715:68:Warning: reference to free
> variable
> `count-key-pos'
>
> Compiling file
> /home/tstl/.emacs.d/elpa/org-ref-20170523.1821/org-ref-helm.el a\
> t Fri May 26 14:59:58 2017
>
> In org-ref:
> org-ref-helm.el:289:78:Error: `add-to-list' can't use lexical var
> `matches';
> use `push' or `cl-pushnew'
> org-ref-helm.el:317:54:Error: `add-to-list' can't use lexical var
> `matches';
> use `push' or `cl-pushnew'
> org-ref-helm.el:306:39:Error: `add-to-list' can't use lexical
> var `matches';
> use `push' or `cl-pushnew'
> org-ref-helm.el:380:47:Warning: reference to free variable
> `org-latex-prefer-user

[O] A possibly useful thing

[Tom Hinton]

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

[O] Warnings while installing org-ref

[Lars Bjørndal]

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'
org-ref-helm-bibtex.el:715:68:Warning: reference to free
variable
`count-key-pos'

Compiling file
/home/tstl/.emacs.d/elpa/org-ref-20170523.1821/org-ref-helm.el a\
t Fri May 26 14:59:58 2017

In org-ref:
org-ref-helm.el:289:78:Error: `add-to-list' can't use lexical var
`matches';
use `push' or `cl-pushnew'
org-ref-helm.el:317:54:Error: `add-to-list' can't use lexical var
`matches';
use `push' or `cl-pushnew'
org-ref-helm.el:306:39:Error: `add-to-list' can't use lexical
var `matches';
use `push' or `cl-pushnew'
org-ref-helm.el:380:47:Warning: reference to free variable
`org-latex-prefer-user-labels'

Compiling file
/home/tstl/.emacs.d/elpa/org-ref-20170523.1821/org-ref-pdf.el at\
 Fri May 26 14:59:59 2017

In end of data:
org-ref-pdf.el:248:1:Warning: the following functions are not known to
be defin\
ed:
pdf-view-assert-active-region, pdf-view-active-region-text,
pdf-view-deactivate-region

Lars

[O] :placement documentation imprecise

[edgar]

Hello,

I have this in the documentation (M-x org-info)

#+BEGIN_QUOTE
`:float'
`:placement'
 The table environments by default are not floats in LaTeX.  To
 make them floating objects use `:float' with one of the following
 options: `sideways', `multicolumn', `t', and `nil'.  Note that
 `sidewaystable' has been deprecated since Org 8.3.  LaTeX floats
 can also have additional layout `:placement' attributes.  These
 are the usual `[h t b p ! H]' permissions specified in square
 brackets.  Note that for `:float sideways' tables, the LaTeX
 export back-end ignores `:placement' attributes.
#+END_QUOTE

But, if I use sideways alone (not sidewaystable), the table is not 
rotated.


I don't think that this is very important, but I wanted to let you know 
in case that there is some intention to fix it :) .


Thanks for Org-mode!

-

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] Git repository error

[Charles Millar]

HI,

On 05/26/17 06:35, Gregor Zattler wrote:

Hi org-mode developers,
* claude fuhrer  [2017-05-26; 09:39]:

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



Same here - since yesterday morning.

Charlie Millar

Re: [O] Citations with org-ref in apa style

[Lars Bjørndal]

On Thu, May 25, 2017 at 08:36:28PM -0400, John Kitchin wrote:
> I guess you should change
> #+LATEX_HEADER:
>  \usepackage[citestyle=authoryear-icomp,bibstyle=authoryear,
>  hyperref=true,backref=false,maxcitenames=3,url=true,
> backend=biber,natbib=true]
>  {biblatex}
> to
> #+LATEX_HEADER: \usepackage[american]{babel}
> #+LATEX_HEADER: \usepackage{csquotes}
> #+LATEX_HEADER: \usepackage[style=apa]{biblatex}
> #+LATEX_HEADER: \DeclareLanguageMapping{american}{american-apa}

Thank you very much!

After a bit of fiddling, I got it. The headers I have now, and which
work, are:

#+LANGUAGE: no
#+OPTIONS: toc:nil timestamp:nil time:nil
#+LATEX_CLASS: article
#+LaTeX_CLASS_OPTIONS: [a4paper,norsk,12pt,listings-bw,microtype]
#+LATEX_HEADER: \usepackage{babel}
#+LATEX_HEADER: \usepackage{fancyhdr}
#+LATEX_HEADER: \usepackage{csquotes}
#+LATEX_HEADER: \usepackage[backend=biber,style=apa]{biblatex}
#+LATEX_HEADER: \DeclareLanguageMapping{norsk}{norsk-apa}

#+LATEX_HEADER: \usepackage{lastpage}
#+LATEX_HEADER: \usepackage{hyperref}
#+LATEX_HEADER: \usepackage{url}
#+Latex_header: \addbibresource{~/mydoc/smartlaring/ref.bib}
#+BIBLIOGRAPHY: ~/mydoc/smartlaring/ref apa
#+Latex_header: \linespread{1.4}

Again, thank you!

Lars

>   On Thu, May 25, 2017 at 05:36:07PM +0100, Eric S Fraga wrote:
>   > On Thursday, 25 May 2017 at 11:47, Lars Bjørndal wrote:
>   > > Hi, list!
>   > >
>   > > I'm currently writing an exam in org-mode with org-ref,
>   installed from
>   > > elpa. I think the institution expects to get the referances in
>   apa
>   > > style. So I wonder if I can do that, and how I can do it.
>   >
>   > Have you tried?  What happens?
>   Well, to be honest, I don't know what to replace the line in
>   question
>   with. I'm a novice both in LaTeX and in org-mode/org-ref.
>   Lars
> 
> References
> 
> 1. 
> http://mirrors.ibiblio.org/CTAN/macros/latex/contrib/biblatex-contrib/biblatex-apa/biblatex-apa.pdf
> 2. http://kitchingroup.cheme.cmu.edu/
> 3. mailto:l...@lamasti.net

Re: [O] Git repository error

[Gregor Zattler]

Hi org-mode developers,
* claude fuhrer  [2017-05-26; 09:39]:
> 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 ?

me too, while at the sane time I see several commits every day
via http://orgmode.org/cgit.cgi/org-mode.git/log/

My org-mode.git/config seems ok to me:

[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = git://orgmode.org/org-mode.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
[branch "maint"]
remote = origin
merge = refs/heads/maint



Ciao; Gregor 

Re: [O] Bug: link formating problem [9.0.5 (9.0.5-elpaplus @ /Users/mistkafka/.emacs.d/elpa/org-plus-contrib-20170210/)]

[Nicolas Goaziou]

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.

Regards,

-- 
Nicolas Goaziou

Re: [O] org-publish-attachment doesn't follow symbolic links anymore

[Julien Cubizolles]

Nicolas Goaziou  writes:

> Hello,
>
> Julien Cubizolles  writes:
>
>> I'm using symbolic links in a directory managed by
>> org-publish-attachment. As of a few weeks ago, org-publish-attachment
>> doesn't upload the files linked to to the ftp server like it used
>> to. There is no error message, only:
>>
>> Copying filename.pdf to /ftp:login@ftpserver:/dir/...done
>>
>> but the file isn't uploaded.
>
> Fixed. Thank you.

Thanks.

Julien.

Re: [O] Bug: link formating problem [9.0.5 (9.0.5-elpaplus @ /Users/mistkafka/.emacs.d/elpa/org-plus-contrib-20170210/)]

[Chunyang Xu]

I changed `org-plain-link-re' to make it not longer think "[" and "]"
are valid characters in a URL, which solves the problem.

diff -u --label 
/Users/xcy/.emacs.d/elpa-25.2.1/org-plus-contrib-20170515/org.el --label 
\#\ 
/Users/xcy/.emacs.d/elpa-25.2.1/org-plus-contrib-20170515/org.el 
/var/folders/7f/s191h4q97p90374yw15ssrs0gn/T/buffer-content-71053Vt
--- /Users/xcy/.emacs.d/elpa-25.2.1/org-plus-contrib-20170515/org.el
+++ #
@@ -5847,7 +5847,7 @@
  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
  "\\[\\[\\([^][]+\\)\\]\\(\\[\\([^][]+\\)\\]\\)?\\]"

Diff finished.  Fri May 26 16:01:30 2017

林镇国  writes:

> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen.  You don't know how to make a good report?  See
>
>  http://orgmode.org/manual/Feedback.html#Feedback
>
> Your bug report will be posted to the Org mailing list.
> 
>
> Hi!
>
> When I insert a link to my note, such as“这是一个[[link][链接]]啦~”，
> the text after the link, "啦~", will be formatting as link style.
>
> Space participe is not work in some language, such as Chinese and
> Japanese. If I use a space to participe the link the the text after
> it, that's really ugly in Chinese.
>
> And I wonder even in English, must we add a space after a link?
>
> By the way, it just a formatting problem(with org-hide-emphasis-markers
> is t), not export problem, the link export to html is ok!
>
> Emacs  : GNU Emacs 25.2.1 (x86_64-apple-darwin13.4.0, Carbon Version 157 
> AppKit 1265.21)
> of 2017-02-06
> Package: Org mode version 9.0.5 (9.0.5-elpaplus @ 
> /Users/mistkafka/.emacs.d/elpa/org-plus-contrib-20170210/)
>
> current state:
> ==
> (setq
> org-id-locations-file "/Users/mistkafka/.emacs.d/.cache/.org-id-locations"
> org-tab-first-hook '(org-babel-hide-result-toggle-maybe 
> org-babel-header-arg-expand)
> org-clock-persist-file "/Users/mistkafka/.emacs.d/.cache/org-clock-save.el"
> org-speed-command-hook '(org-speed-command-default-hook 
> org-babel-speed-command-hook)
> org-time-clocksum-format '(:hours "%d" :require-hours t :minutes ":%02d" 
> :require-minutes t)
> org-occur-hook '(org-first-headline-recenter)
> org-imenu-depth 8
> org-metaup-hook '(org-babel-load-in-session-maybe)
> org-html-format-drawer-function '(closure
>(htmlize-buffer-places 
> org-html-format-table-no-css htmlize-css-name-prefix htmlize-output-type 
> htmlize-output-type
> htmlize-css-name-prefix t)
>(_name contents) contents)
> org-log-done t
> org-latex-format-inlinetask-function 
> 'org-latex-format-inlinetask-default-function
> org-confirm-shell-link-function 'yes-or-no-p
> org-image-actual-width nil
> org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
> org-link-translation-function 'toc-org-unhrefify
> org-present-mode-hook '(spacemacs//org-present-start)
> org-agenda-restore-windows-after-quit t
> org-latex-format-headline-function 'org-latex-format-headline-default-function
> org-default-notes-file "notes.org"
> org-todo-keyword-faces '(("NEXT" :inherit warning) ("PROJECT" :inherit 
> font-lock-string-face))
> org-after-todo-state-change-hook '(org-clock-out-if-current)
> org-latex-format-drawer-function '(closure (t) (_ contents) contents)
> org-odt-format-headline-function 'org-odt-format-headline-default-function
> org-todo-repeat-to-state "NEXT"
> org-src-mode-hook '(org-src-babel-configure-edit-buffer 
> org-src-mode-configure-edit-buffer)
> org-agenda-before-write-hook '(org-agenda-add-entry-text)
> org-babel-pre-tangle-hook '(save-buffer)
> org-mode-hook '(#[0 "\300\301\302\303\304$\207" [add-hook 
> change-major-mode-hook org-show-block-all append local] 5]
>  #[0 "\300\301\302\303\304$\207" [add-hook 
> change-major-mode-hook org-babel-show-result-all append local] 5] 
> org-babel-result-hide-spec
>  org-babel-hide-all-hashes spacemacs/load-yasnippet 
> toc-org-enable org-download-enable org-bullets-mode 
> spacemacs//org-babel-do-load-languages flyspell-mode
>  spacemacs/add-org-surrounds evil-org-mode org-eldoc-load 
> spacemacs//init-company-org-mode company-mode)
> org-archive-hook '(org-attach-archive-delete-maybe)
> org-ascii-format-drawer-function '(closure (t) (_name contents _width) 
> contents)
> org-odt-format-inlinetask-function 'org-odt-format-inlinetask-default-function
> org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers 
> org-cycle-show-empty-lines org-optimize-window-after-visibility-change)
> org-publish-tim

Re: [O] Bug: link formating problem [9.0.5 (9.0.5-elpaplus @ /Users/mistkafka/.emacs.d/elpa/org-plus-contrib-20170210/)]

[Chunyang Xu]

Kaushal Modi  writes:

> On Wed, May 24, 2017 at 9:50 AM Chunyang Xu  wrote:
>
>>
>> Nicolas Goaziou writes:
>>
>> > Hello,
>> >
>> > 林镇国  writes:
>> >
>> >> When I insert a link to my note, such as“这是一个[[link][链接]]啦~”，
>> >> the text after the link, "啦~", will be formatting as link style.
>> >
>> > FWIW, I cannot reproduce it, i.e., only "链接" appears with a link face.
>>
>> I can reproduce if "link" is a real link and "description" doesn't
>> contain white space, for example,
>>
>> [[http://example.com/][Example]]blah
>> 
>> Also under the org-link face
>>
>> It looks like `org-plain-link-re' doesn't think a link is end unless
>> a punctuation character is found:
>>
>> org-plain-link-re
>> (concat
>>  "\\<" types-re ":"
>>  "\\([^ \t\n()<>]+\\(?:([[:word:]0-9_]+)\\|\\([^[:punct:]
>> \t\n]\\|/\\)\\)\\)")
>>   ^
>>
>> It is a reasonable assumption for English, but not for Chinese.
>>
>
> I actually stumbled across this few days back, and when using English
> language :)
>
> Here's a solution that might work for you too (and my notes on why I set
> this):
>
> ;; The default value of `org-highlight-links' contains `plain' too.
> ;; - "plain" links are links in normal text, no whitespace, like
> http://foo.com.
> ;; Here's why I remove "plain" from this list:
> ;; - If I have two bracketed links next to each-other in org-mode (like
> below),
> ;; [[http://google.com][1]],[[http://orgmode.org][2]]
> ;; - and, if `plain' is in the `org-highlight-links' list,
> ;;  the "," in there will also be highlighted as a link. So it would look
> ;;  as if the "1,2" string pointed to a single link!
> ;;But without `plain' as part of this list, the "1" and "2" strings will
> ;; look like separate links (as should be the case), as the "," will not be
> ;; highlighted as a link.
> (setq org-highlight-links (delete 'plain org-highlight-links))

Oh, I didn't know the user option, I just added it to my init file.
Thanks.

>
> -- 
>
> Kaushal Modi

Re: [O] Allow #+SETUPFILE to point to an URL for the org file

[Nicolas Goaziou]

Hello,

Kaushal Modi  writes:

> I have attached an updated and rebased patch with most of your suggestions
> implemented.

Thank you.

>> Here is my use case for org-file-clear-cache:
>>
>> Let's say I have a file where I have a SETUPFILE retrieved from a URL. Now
>> the upstream version changes but my cache is still on the older version. So
>> I need to clear the hash. The org-file-clear-cache simply does that.

I understand the use case for `org-file-clear-cache'. My suggestion is
to remove that need by clearing cache automatically. Of course, the
drawback is the cache is cleared more often than necessary. Users could
get very surprising results if they forget to call this function. So it
might be a good idea to call it from time to time, on user's behalf.

> I grepped org.texi but found no reference of org-file-contents. So may be
> we need to add a section for that, and there I can explain
> org-file-clear-cache in more detail. What would be a good node for
> that?

`org-file-contents' is a developer-facing function. I don't really see
a good place in the manual for it. That's the problem of
`org-file-clear-cache', which is really an implementation detail users
shouldn't care about.

Here's another idea: call it from `org-mode-restart'. So cache is reset
whenever `C-c C-c' is pressed on a keyword. So we don't need to document
the function anymore. Instead, we could drop a note about the cache in
(info "(org) The very busy C-c C-c key").

>>   (if (re-search-forward "HTTP.*\\s-+200\\s-OK" nil t)
>>>   ;; URL retrieved correctly.  Move point to after the
>>>   ;; url-retrieve header, update the cache `org--file-cache'
>>>   ;; and return contents.
>>>   (progn
>>> (search-forward "\n\n" nil 'move)
>>
>>
> I have integrated most of your refactored version except for this portion.
> Above will do a false match if that "HTTP.." string is present in the FILE
> body too! I have retained my version of only that part where the search
> happens only inside the url-retrieve header. The search is also faster in
> the case of failure as it does not have to search through the whole file
> before declaring a fail.. as only the header is searched.

OK. Then the following at least doesn't have the overhead of creating
a string:


(with-current-buffer (url-retrieve-synchronously file)
  (goto-char (point-min))
  ;; Move point to after the url-retrieve header.
  (search-forward "\n\n" nil 'move)
  ;; Search for the success code only in the url-retrieve header.
  (if (save-excursion (re-search-backward "HTTP.*\\s-+200\\s-OK" nil t))
  ;; Update the cache `org--file-cache' and return contents.
  (puthash file
   (buffer-substring-no-properties (point) (point-max))
   org--file-cache)
(funcall (if noerror #'message #'user-error)
 "Unable to fetch file from %S"
 file)))

Also, mind the full stop at the end of the comments.

Regards,

-- 
Nicolas Goaziou

Re: [O] Git repository error

[claude fuhrer]

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

Re: [O] Cross references that output both section number and section name

[Nicolas Goaziou]

Hello,

Aaron Wenner  writes:

> Does anyone know if it’s possible to create cross-references to sections in 
> org-mode that contain (or export as) both the section number and the link 
> text? For example:  
>
> * This is heading 1
> ** This is heading 1.1
>
> * New heading
> [[*This is heading 1.1]] # Outputs as 1.1
> [[*This is heading 1.1][This is heading 1.1]] # Outputs as "This is 
> heading 1.1"
> Is there any way to create a link that outputs both examples at the
> same time: Eg: 1.1 This is heading 1.1

  [[*This is heading 1.1]] [[*This is heading 1.1][This is heading 1.1]]

Regards,

-- 
Nicolas Goaziou