[O] [PATCH] * contrib/manual.org: Add org-capture-templates to Variable Index

[Xu Chunyang]

---

I notice 'C-h S' ('info-lookup-symbol') can't find
'org-capture-templates', adding the variable to (info "(org) Variable
Index") should fix this issue.

I don't know if I should change org.texi instead or both of them.

 contrib/manual.org | 1 +
 1 file changed, 1 insertion(+)

diff --git a/contrib/manual.org b/contrib/manual.org
index a9c546ebc..a57114401 100644
--- a/contrib/manual.org
+++ b/contrib/manual.org
@@ -7114,6 +7114,7 @@ is through the customize interface.
 - {{{kbd(C-c c C)}}} ::
 
  #+kindex: C-c c C
+ #+vindex: org-capture-templates
  Customize the variable ~org-capture-templates~.
 
 Before we give the formal description of template definitions, let's
-- 
2.15.1

[O] Invalid links in Worg

[Kaushal Modi]

Hello,

Using the W3C Invalid Link checker[1], I found the following invalid (404)
links on Worg.

https://orgmode.org/worg/code/
https://orgmode.org/worg/code/latex/fr-orgcard.tex
https://orgmode.org/worg/code/org-info-js/index.html
https://orgmode.org/worg/sources/
https://orgmode.org/worg/orgguide/orgguide.es.texi
https://orgmode.org/worg/sitemap.html

I don't know how to fix those (especially the code/ and sources/ subdirs).

[1]:
https://validator.w3.org/checklink?uri=https%3A%2F%2Forgmode.org%2Fworg_type=all==Check


-- 

Kaushal Modi

Re: [O] Broken links in worg

[Kaushal Modi]

On Wed, Jan 3, 2018 at 3:29 PM Nick Dokos  wrote:

> There are a few links in the babel area of worg
> (https://orgmode.org/worg/org-contrib/babel/index.html) that seem to
> be broken:
>
> o
> http://orgmode.org/manual/Working-With-Source-Code.html#Working-With-Source-Code
>   (this seems to be an http vs https problem).
>

It was letter casing problem.. I have committed the fix.

o https://orgmode.org/worg/org-contrib/babel/header-args.html


I see that the header-args.org is moved to FIXME..
https://code.orgmode.org/bzg/worg/raw/master/FIXME/header-args.org

My guess would be that the move to FIXME would have been made as the Local
Variables section in that code block was trying to actually get evaluated:

=
: #+Title: Example of default file and language session
:
: The value in this buffer is...
: #+begin_src emacs-lisp
:   org-babel-default-header-args:Python
: #+end_src
:
: #+RESULTS:
: | (:session . foo) |
:
: # Local Variables:
: # eval: (setq-local org-babel-default-header-args:Python '((:session .
"foo")))
: # End:
=

I tried a bit, but cannot figure out how to *not* make Local Variables
section in a code block from getting evaluated.

o https://orgmode.org/worg/org-contrib/babel/languages.html
>

This one is perplexing.. if I build the Worg site locally using this[1]..
that languages.html page is created fine. But that languages.html (and the
complete org-contrib/babel/languages/ section) is not published on the Worg
site. May be Bastien, Nicolas or someone else can chime in to help with
this and the above FIXME.

[1]: https://gist.github.com/1932834fa33f72ff44eea476f15cad08 and then
running "emacs --batch -l ~/e/misc/worg/worg-setup.el -f org-publish-all"
(Emacs 26.0.90 and latest Org master).


-- 

Kaushal Modi

Re: [O] Probably broke the Worg build?

[Kaushal Modi]

On Fri, Jan 5, 2018 at 9:05 PM Kaushal Modi  wrote:

>
> Thanks! I just pushed one more commit (
> https://code.orgmode.org/bzg/worg/commit/4feac9160363279653a3d19cf68619e6a9c02fee
> ).. let's see if that freezes up the build again.
>

My commits seem to have frozen Worg builds again.. sorry. But I don't know
what I am doing wrong.

I also noticed below, which should help debug this.

My "git push origin master" commands always "fail".. but they seem to work
i.e. the commits do reach the remote fine.

For example, this commit[1] got pushed fine, but the log shows this:

=
Counting objects: 5, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 478 bytes | 478.00 KiB/s, done.
Total 5 (delta 4), reused 0 (delta 0)
error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504
Gateway Time-out
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date
=

[1]:
https://code.orgmode.org/bzg/worg/commit/397cb3c0bd0e33ba6b6522c28bf6fd0b3e461d04


-- 

Kaushal Modi

Re: [O] Probably broke the Worg build?

[Kaushal Modi]

On Fri, Jan 5, 2018 at 8:55 PM Bastien  wrote:

> Hi Kaushal,
>
> I republished Worg manually and things went fine.  But I had to kill
> a stuck process before running this new one.  I'll try to understand
> what happened when I have more time at end.
>

Thanks! I just pushed one more commit (
https://code.orgmode.org/bzg/worg/commit/4feac9160363279653a3d19cf68619e6a9c02fee
).. let's see if that freezes up the build again. I am using https to push
the commits. That shouldn't matter, right? Because the commits do end up
showing fine on code.orgmode.org.

Thanks for the fixes!
>

My pleasure.


-- 

Kaushal Modi

Re: [O] Probably broke the Worg build?

[Bastien]

Hi Kaushal,

I republished Worg manually and things went fine.  But I had to kill
a stuck process before running this new one.  I'll try to understand
what happened when I have more time at end.

Thanks for the fixes!

-- 
 Bastien

Re: [O] Bug in Sticky Agendas

[Ian Dunn]

> "Ian" == Ian Dunn  writes:

Ian> I've got a few tasks that I don't want appearing in the
Ian> daily agenda, so I tag them with agenda_exclude and set
Ian> org-agenda-skip-function to skip any entries with that tag for
Ian> my daily agenda:

Ian> (defun id/org-skip-by-tag ( tags) (if (not (apply
Ian> 'org-entry-has-tags-p tags)) nil (save-excursion
Ian> (outline-next-visible-heading 1) (point

Ian> (let* ((agenda-skip '(org-agenda-skip-function (lambda nil
Ian> (id/org-skip-by-tag "agenda_exclude") (setq
Ian> org-agenda-custom-commands `(("d" "Day View" agenda ""
Ian> ((org-agenda-span 'day) ,agenda-skip)) ("T" . "Tags View")
Ian> ("Tn" "Nightly" tags-todo "nightly==\"TODO\""

Ian> As you can see, I've got a second agenda view for my nightly
Ian> checklist.  So here's my problem: the skip-function is unset if
Ian> I try using the nightly view.

I went ahead and looked into this myself.  Looks like the issue is that the 
properties (lprops) are set using symbol properties with 
org-agenda-redo-command, which is buffer-local.  However, according to the 
elisp manual (at least for the upcoming 26.1 release), symbol properties aren't 
buffer-local; only the value itself is.  Thus, lprops are overridden by a new 
agenda.

I've created the following patch to address this.  The symbol property is used 
as a temporary variable, but the actual lprops are stored as a buffer-local 
variable to each agenda buffer.

diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index a9ebb793b..5226ef486 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -2142,6 +2142,7 @@ When nil, `q' will kill the single agenda buffer."
 (defvar org-agenda-this-buffer-is-sticky nil)
 (defvar org-agenda-last-indirect-buffer nil
   "Last buffer loaded by `org-agenda-tree-to-indirect-buffer'.")
+(defvar org-agenda-lprops nil)
 
 (defconst org-agenda-local-vars
   '(org-agenda-this-buffer-name
@@ -2170,6 +2171,7 @@ When nil, `q' will kill the single agenda buffer."
 org-agenda-filtered-by-category
 org-agenda-filter-form
 org-agenda-cycle-counter
+org-agenda-lprops
 org-agenda-last-prefix-arg)
   "Variables that must be local in agenda buffers to allow multiple buffers.")
 
@@ -3749,6 +3751,10 @@ FILTER-ALIST is an alist of filters we need to apply when
 	  (org-uniquify org-done-keywords-for-agenda))
 	(setq org-agenda-last-prefix-arg current-prefix-arg)
 	(setq org-agenda-this-buffer-name org-agenda-buffer-name)
+	;; Don't set these until we know we're in the agenda buffer,
+	;; and we know they're valid.
+	(setq org-agenda-lprops (or org-agenda-lprops
+(get 'org-agenda-redo-command 'org-lprops)))
 	(and name (not org-agenda-name)
 	 (setq-local org-agenda-name name)))
   (setq buffer-read-only nil
@@ -7312,7 +7318,7 @@ in the agenda."
 	 (cols org-agenda-columns-active)
 	 (line (org-current-line))
 	 (window-line (- line (org-current-line (window-start
-	 (lprops (get 'org-agenda-redo-command 'org-lprops))
+	 (lprops org-agenda-lprops)
 	 (redo-cmd (get-text-property p 'org-redo-cmd))
 	 (last-args (get-text-property p 'org-last-args))
 	 (org-agenda-overriding-cmd (get-text-property p 'org-series-cmd))

-- 
Ian Dunn

Re: [O] Org citations, CSL and citeproc-el

[Nicolas Goaziou]

Hell,

Richard Lawrence  writes:

> Simonyi András  writes:
>
>> a few days ago I've released the first public version of citeproc-el
>> (https://github.com/andras-simonyi/citeproc-el), a CSL 1.01 citation
>> processor library for Emacs.

Excellent! Thank you for this work.

>> The resulting link syntax is rather cumbersome so I'd like to ask
>> your opinion about introducing an alternative org-mode citation
>> syntax that handles all of these elements.  One option would be to
>> use something very similar to pandoc's citation syntax (which
>> I tried to follow as much as possible in the cite link descriptions
>> of citeproc-orgref). 

[...]

> The upshot was that we came to agreement on quite a few points about
> what citation syntax should look like, and those points have been
> implemented in Org syntax in the wip-cite branch of the Org repo.
> (This branch is now long out of date and at the very least in need of
> a rebase onto current master, I suspect.)

The "wip-cite" branch is up-to-date with master (give or take last
commits). It implements a good basis for a citation syntax in Org (tests
included).

Also, there is "wip-cite-awe" branch from Aaron Ecay (Cc'ed) which
implements some support for exporting citations. "wip-cite-awe" is
up-to-date and base on top of "wip-cite".

> There are other aspects of the syntax we agreed on that are not
> implemented yet; as I recall, the idea was to get a minimal agreeable
> subset working, and then add to it based on real-world experience and
> feedback.

AFAIR, everything we agreed on is implemented in "wip-cite" branch.

That's a good thing to know that citations may move forward. Let us know
if you need help. Meanwhile, as Richard suggests, please have a look at
"wip-cite" branch.

Regards,

-- 
Nicolas Goaziou

Re: [O] [IT] Broken support for links to text files (both internal & external)

[Tim Cross]

Eric has provided the 'manual' solution for setting that variable. At
the risk of 'muddying the waters', I just wanted to mention a couple of
things which might help clarify matters.

- The built-in 'customize' facility of emacs means that you do not need
to do anything 'by hand' to customize the setting. It should be possible
for you to use customize and not do anything else.

- The block from your .emacs file is the customize system code block and
it is meant to be completely managed by the customize system. The one
you have posted is a vanilla block with no customisation settings.

- When you make a change via the customise interface, you have multiple
choices for how Emacs will use/interpret that change. This is referred
to as 'state' in the custom interface. There are a number of options,
all explained in the manual, but the two most common are 'Set for
current session' and 'Save for future sessions'.

- It is important to realise that the custom interface does basically
two things. First, it sets any current variables representing the value
being customised. This is essentially the 'Set for current session'
part. Second, assuming you select a state option which preserves your
changes, it will write the setting to the custom block in your .emacs
file so that your changes persist across emacs sessions. This is
essentially the 'Save for future sessions' part.

The benefit of the set for current session option is that it give the
the opportunity to try out a custom setting. If it doesn't work or it
breaks things, you can just quit emacs and re-start and everything is
back to the pre-custom setting. The downside of this option is that if
you don't later in the same session re-run the custom interface and
select the 'Save for future sessions' option, your changes will be lost
when you re-start.

Given that you noted the custom interface was able to re-indent your
.emacs custom block, we know that custom is working and can access your
.emacs file ok. Therefore, the next thing I would check is that when you
run the customize interface you are selecting Save for future sessions
option. This should see the setting updated in your .emacs 'custom'
block. (I suspect you may have selected 'set for current session' which
will not update the custom block in your .emacs file).

I would highly recommend reading the customisation section of the Emacs
manual. The custom interface has been implemented precisely for people
who don't know emacs lisp and just want to perform basic editor or mode
customisation. Using that interface, you don't need to know any Emacs
lisp and don't need to do anything by hand. There are also a number of
different ways to initiate a customisation session. I find that

M-x customize-group  [mode]

to be very useful. For example,

M-x customize-group  org

HTH

Tim



Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ)  writes:

> On 05/01/2018 13:27, Eric S Fraga wrote:
>> On Friday,  5 Jan 2018 at 13:10, Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ) wrote:
>> 
>> [...]
>> 

> [...]
> I've done this but only changed the indentation of the
> custom-set-variables block and added nothing new.
>
> And if I start from an empty ~/.emacs I got this ew block, but again, it
> does not mention org-link-search-must-match-exact-headline variable:
>
> (custom-set-variables
>   ;; custom-set-variables was added by Custom.
>   ;; If you edit it by hand, you could mess it up, so be careful.
>   ;; Your init file should contain only one such instance.
>   ;; If there is more than one, they won't work right.
>   )
> (custom-set-faces
>   ;; custom-set-faces was added by Custom.
>   ;; If you edit it by hand, you could mess it up, so be careful.
>   ;; Your init file should contain only one such instance.
>   ;; If there is more than one, they won't work right.
>   )
>
> What should I add *by hand* in ~/.emacs?
> I'm sorry, it is just a matter of very basic elisp syntax (but I never
> took the time to dig into elisp yet!).
>



-- 
Tim Cross

Re: [O] Org citations, CSL and citeproc-el

[Eric S Fraga]

On Friday,  5 Jan 2018 at 08:52, Richard Lawrence wrote:

[...]

As Richard says, wow!  This would seem to fit nicely with what we
(i.e. the mailing list as I don't think I actually said anything...)
did discuss about what was needed going forward.

> Here's my two cents on this. From what I recall about the discussion
> (it's hard to believe it's already been almost three years...), I
> would focus on two things:

> 2) org-bibtex support.  Org-bibtex is a library that represents

+1

All of my references are in org-bibtex format and supporting this
would be really welcome.  At present, I export these to bibtex files
for use with org->PDF via LaTeX but it would be great to have:

1. an easy to use citing mechanism in org that knows org-bibtex and
2. export to ODT and/or html with citations.

thanks,
eric

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6


signature.asc
Description: PGP signature

Re: [O] [IT] Broken support for links to text files (both internal & external)

[Eric S Fraga]

On Friday,  5 Jan 2018 at 17:15, Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ) wrote:
> On 05/01/2018 13:27, Eric S Fraga wrote:

[...]

>> Easy: describe the variable
>>
>>C-h v org-link-search-must-match-exact-headline RET
>>
>> and then click on the "customize" link near the end of the
>> description.  Make sure to "Apply and set" the change you make.
>>
>
> I've done this but only changed the indentation of the
> custom-set-variables block and added nothing new.

Strange.

> What should I add *by hand* in ~/.emacs?

Try

  (setq org-link-search-must-match-exact-headline nil)
  
> I'm sorry, it is just a matter of very basic elisp syntax (but I never
> took the time to dig into elisp yet!).

No worries.  None of us is born known lisp...  However, no time like
the present to start learning. ;-)

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6


signature.asc
Description: PGP signature

[O] Probably broke the Worg build? (Was: Re: [IMPORTANT] Server migration..)

[Kaushal Modi]

Hello,

Looks like my recent commits broke the Worg build? Is the Worg build log
available publicly so that I can look at the errors and possibly fix this?

My changes involved basically replaced non-working links with working
links.. so not sure how that could have broken this..

The last commit on Worg master was about 25 minutes back, but the changes
are not yet live on the site.

On Fri, Jan 5, 2018 at 12:31 PM Kaushal Modi  wrote:

> On Thu, Jan 4, 2018 at 1:52 PM Kaushal Modi 
> wrote:
>
>>
>> I'll fix Worg tonight if no one else has done that by then :)
>>
>
> Phew! Done in [1], [2] and [3].
>
> Now the only things pending fixing are:
>
> 1. Commit search links like these (1700+) in worg/doc.org
>
> ag --nogroup --line-number --column --color --color-match 30\;43
> --color-path 1\;32 --nogroup --skip-vcs-ignores --numbers --smart-case
> --follow --ignore \#\*\# --stats -- orgmode.org/w/ .
> doc.org:44:13:- [[
> https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-checkbox-statistics-hook=1][Find
> modifications in git logs]]
> doc.org:57:13:- [[
> https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-todo-setup-filter-hook=1][Find
> modifications in git logs]]
> doc.org:68:13:- [[
> https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-timer-continue-hook=1][Find
> modifications in git logs]]
> doc.org:77:13:- [[
> https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-clock-in-hook=1][Find
> modifications in git logs]]
> doc.org:86:13:- [[
> https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-clock-before-select-task-hook=1][Find
> modifications in git logs]]
> doc.org:95:13:- [[
> https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-property-allowed-value-functions=1][Find
> modifications in git logs]]
> doc.org:110:13:- [[
> https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-after-todo-state-change-hook=1][Find
> modifications in git logs]]
>
> 2. Git repos directly under orgmode.org as mentioned in
> worg/org-contrib/gsoc2012/student-projects. @Bastien: Do you know where
> those git repos now live? For now, I have marked them as TODO's:
> https://code.orgmode.org/bzg/worg/commit/d4005f04f66bc0ed148212e104b571bed5573516#diff-ab154bcc2783f79b789825d4b9a2b5d63d4bcd5R17
>
>
> As a plus of this repo move, I don't need to jump to hoops to commit my
> stuff as committing via https just works, yay! (git: is blocked on my
> regular machine, so earlier had to commit via https to gitlab, pull that on
> phone, and commit to Org/Worg repo via git: using my phone :P) :D
>
> [1]:
> https://code.orgmode.org/bzg/worg/commit/f6299f7e9a58a032c8474a5e552f6536202b2b29
> [2]:
> https://code.orgmode.org/bzg/worg/commit/503c34f0a16e504ddad54f4d265f92eb0ac9213f
> [3]:
> https://code.orgmode.org/bzg/worg/commit/d4005f04f66bc0ed148212e104b571bed5573516
>
>
>
> --
>
> Kaushal Modi
>


-- 

Kaushal Modi

Re: [O] [IMPORTANT] Server migration: please update your git repositories before 31/12/2017

[Kaushal Modi]

On Thu, Jan 4, 2018 at 1:52 PM Kaushal Modi  wrote:

>
> I'll fix Worg tonight if no one else has done that by then :)
>

Phew! Done in [1], [2] and [3].

Now the only things pending fixing are:

1. Commit search links like these (1700+) in worg/doc.org

ag --nogroup --line-number --column --color --color-match 30\;43
--color-path 1\;32 --nogroup --skip-vcs-ignores --numbers --smart-case
--follow --ignore \#\*\# --stats -- orgmode.org/w/ .
doc.org:44:13:- [[
https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-checkbox-statistics-hook=1][Find
modifications in git logs]]
doc.org:57:13:- [[
https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-todo-setup-filter-hook=1][Find
modifications in git logs]]
doc.org:68:13:- [[
https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-timer-continue-hook=1][Find
modifications in git logs]]
doc.org:77:13:- [[
https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-clock-in-hook=1][Find
modifications in git logs]]
doc.org:86:13:- [[
https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-clock-before-select-task-hook=1][Find
modifications in git logs]]
doc.org:95:13:- [[
https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-property-allowed-value-functions=1][Find
modifications in git logs]]
doc.org:110:13:- [[
https://orgmode.org/w/?p=org-mode.git=search=HEAD=commit=org-after-todo-state-change-hook=1][Find
modifications in git logs]]

2. Git repos directly under orgmode.org as mentioned in
worg/org-contrib/gsoc2012/student-projects. @Bastien: Do you know where
those git repos now live? For now, I have marked them as TODO's:
https://code.orgmode.org/bzg/worg/commit/d4005f04f66bc0ed148212e104b571bed5573516#diff-ab154bcc2783f79b789825d4b9a2b5d63d4bcd5R17


As a plus of this repo move, I don't need to jump to hoops to commit my
stuff as committing via https just works, yay! (git: is blocked on my
regular machine, so earlier had to commit via https to gitlab, pull that on
phone, and commit to Org/Worg repo via git: using my phone :P) :D

[1]:
https://code.orgmode.org/bzg/worg/commit/f6299f7e9a58a032c8474a5e552f6536202b2b29
[2]:
https://code.orgmode.org/bzg/worg/commit/503c34f0a16e504ddad54f4d265f92eb0ac9213f
[3]:
https://code.orgmode.org/bzg/worg/commit/d4005f04f66bc0ed148212e104b571bed5573516



-- 

Kaushal Modi

Re: [O] Org citations, CSL and citeproc-el

[Christian Moe]

This is exciting news, and I look forward to trying it out.

Regarding syntax:

1. A couple of years back, there was an active discussion on this list to
flesh out a native citation syntax for Org. I fell off the discussion,
but I think it resulted in a non-link-based, feature-rich syntax spec,
but not much code to make use of it. Perhaps someone could comment?

2. Not many people liked my proposal: a link-based syntax similar to yours
but also including author and date in the link description. The idea was
to have descriptions that are both (1) human-readable even though the
citekeys are hidden away in the link path and (2) machine-readable to
determine the form of the citation (parenthetical or not, date-only or
not, etc.). I have used one to work with Zotero, and have a simple
parser for it, if you're interested in pursuing something similar.

Yours,
Christian

Simonyi András writes:

> Dear List Members,
>
> a few days ago I've released the first public version of citeproc-el
> (https://github.com/andras-simonyi/citeproc-el), a CSL 1.01 citation
> processor library for Emacs. Since the main motivation of my work was to
> contribute to org-mode's citation rendering I also implemented a "proof
> of concept" add-on to org-ref that uses citeproc-el to render org-ref
> citation links for non-LaTeX (and optionally even LaTeX) export backends
> (see https://github.com/andras-simonyi/citeproc-orgref).
>
> Both packages are in a relatively early stage of their development so
> I'd be grateful to receive any feedback on them. In particular, in
> citeproc-orgref I had to abuse the cite link descriptions to an even
> greater degree than they were by org-ref to accommodate the full CSL
> representation of citations (citations consist of cites and each cite
> can have a prefix, postfix and a locator). The resulting link syntax is
> rather cumbersome so I'd like to ask your opinion about introducing an
> alternative org-mode citation syntax that handles all of these elements.
> One option would be to use something very similar to pandoc's citation
> syntax (which I tried to follow as much as possible in the cite link
> descriptions of citeproc-orgref).
>
> A more general question I'd like to raise how (or whether) you see
> citeproc-el's (and CSL's) potential place in the org-mode ecosystem.
> There are a lot of directions which the further development could take
> (BibLaTeX support, citeproc-YAML bibliographies, CSL editing and CSL
> extensions etc.) and I'd be grateful to receive your input on which ones
> I should focus on.
>
> thanks in advance & best wishes,
>
> András Simonyi

Re: [O] Org citations, CSL and citeproc-el

[Tory S. Anderson]

Just a second on this; it's a fantastic and useful idea. 


Richard Lawrence  writes:


Dear Simonyi,

Simonyi András  writes:

a few days ago I've released the first public version of 
citeproc-el (https://github.com/andras-simonyi/citeproc-el), a 
CSL 1.01 citation processor library for Emacs.


Wow!  I don't know if you are aware, but we had discussed the 
possibility of building something like this on the list a few 
years back.  At the time it seemed like a lot more work than 
anyone was willing to do, and so the effort stalled.  Thanks so 
much for working on this -- it looks like you've done a ton of 
work!


The resulting link syntax is rather cumbersome so I'd like to 
ask your opinion about introducing an alternative org-mode 
citation syntax that handles all of these elements.  One option 
would be to use something very similar to pandoc's citation 
syntax (which I tried to follow as much as possible in the cite 
link descriptions of citeproc-orgref). 


We had a (very) long discussion about implementing a new 
citation syntax for Org in the spring of 2015.  Most of it took 
place in February and March; see:


https://lists.gnu.org/archive/html/emacs-orgmode/2015-02/threads.html
https://lists.gnu.org/archive/html/emacs-orgmode/2015-03/threads.html 

And here is how I summarized the state of that discussion in 
June:


https://lists.gnu.org/archive/html/emacs-orgmode/2015-06/msg00426.html

The upshot was that we came to agreement on quite a few points 
about what citation syntax should look like, and those points 
have been implemented in Org syntax in the wip-cite branch of 
the Org repo.  (This branch is now long out of date and at the 
very least in need of a rebase onto current master, I suspect.) 
It would be really great to get things moving again.  Using your 
code to provide citation processing during Org export for the 
syntax that's already been implemented would be the place to 
start.


There are other aspects of the syntax we agreed on that are not 
implemented yet; as I recall, the idea was to get a minimal 
agreeable subset working, and then add to it based on real-world 
experience and feedback.


A more general question I'd like to raise how (or whether) you 
see citeproc-el's (and CSL's) potential place in the org-mode 
ecosystem.  There are a lot of directions which the further 
development could take (BibLaTeX support, citeproc-YAML 
bibliographies, CSL editing and CSL extensions etc.) and I'd be 
grateful to receive your input on which ones I should focus 
on. 


Here's my two cents on this. From what I recall about the 
discussion (it's hard to believe it's already been almost three 
years...), I would focus on two things:


1) BibLaTeX support.  Most Org users who want citation support 
want it primarily for LaTeX export, and BibLaTeX provides a good 
model of what we should try to achieve in Org citation support.


2) org-bibtex support.  Org-bibtex is a library that represents 
citation data via Org's property syntax.  Some people use this 
and it would be great to have it integrated with the new 
citation syntax and export.  That would provide an end-to-end 
citation solution that is completely native to Org and Emacs. 

Again, thanks for jump-starting this effort!  I look forward to 
contributing to it this spring.

Re: [O] Org citations, CSL and citeproc-el

[Richard Lawrence]

Dear Simonyi,

Simonyi András  writes:

a few days ago I've released the first public version of 
citeproc-el (https://github.com/andras-simonyi/citeproc-el), a 
CSL 1.01 citation processor library for Emacs.


Wow!  I don't know if you are aware, but we had discussed the 
possibility of building something like this on the list a few 
years back.  At the time it seemed like a lot more work than 
anyone was willing to do, and so the effort stalled.  Thanks so 
much for working on this -- it looks like you've done a ton of 
work!


The resulting link syntax is rather cumbersome so I'd like to 
ask your opinion about introducing an alternative org-mode 
citation syntax that handles all of these elements.  One option 
would be to use something very similar to pandoc's citation 
syntax (which I tried to follow as much as possible in the cite 
link descriptions of citeproc-orgref). 


We had a (very) long discussion about implementing a new citation 
syntax for Org in the spring of 2015.  Most of it took place in 
February and March; see:


https://lists.gnu.org/archive/html/emacs-orgmode/2015-02/threads.html
https://lists.gnu.org/archive/html/emacs-orgmode/2015-03/threads.html 


And here is how I summarized the state of that discussion in June:

https://lists.gnu.org/archive/html/emacs-orgmode/2015-06/msg00426.html

The upshot was that we came to agreement on quite a few points 
about what citation syntax should look like, and those points have 
been implemented in Org syntax in the wip-cite branch of the Org 
repo.  (This branch is now long out of date and at the very least 
in need of a rebase onto current master, I suspect.)  It would be 
really great to get things moving again.  Using your code to 
provide citation processing during Org export for the syntax 
that's already been implemented would be the place to start.


There are other aspects of the syntax we agreed on that are not 
implemented yet; as I recall, the idea was to get a minimal 
agreeable subset working, and then add to it based on real-world 
experience and feedback.


A more general question I'd like to raise how (or whether) you 
see citeproc-el's (and CSL's) potential place in the org-mode 
ecosystem.  There are a lot of directions which the further 
development could take (BibLaTeX support, citeproc-YAML 
bibliographies, CSL editing and CSL extensions etc.) and I'd be 
grateful to receive your input on which ones I should focus on. 


Here's my two cents on this. From what I recall about the 
discussion (it's hard to believe it's already been almost three 
years...), I would focus on two things:


1) BibLaTeX support.  Most Org users who want citation support 
want it primarily for LaTeX export, and BibLaTeX provides a good 
model of what we should try to achieve in Org citation support.


2) org-bibtex support.  Org-bibtex is a library that represents 
citation data via Org's property syntax.  Some people use this and 
it would be great to have it integrated with the new citation 
syntax and export.  That would provide an end-to-end citation 
solution that is completely native to Org and Emacs. 

Again, thanks for jump-starting this effort!  I look forward to 
contributing to it this spring.


--
Best,
Richard

Re: [O] [IT] Broken support for links to text files (both internal & external)

[Aʟᴏɴɢ-Tʀᴀᴄᴋ]

On 05/01/2018 13:27, Eric S Fraga wrote:

On Friday,  5 Jan 2018 at 13:10, Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ) wrote:

[...]


Is it possible that this setting is set by Debian packagers?
I ask this because I reproduced this bug with and without my
  ~/.emacs[.d/] files.


It's the default for org (at least now, as far as I can tell).


But I ashamedly don't know how to set it permanently in my  ~/.emacs!
Would you please help me on this?


Easy: describe the variable

   C-h v org-link-search-must-match-exact-headline RET

and then click on the "customize" link near the end of the
description.  Make sure to "Apply and set" the change you make.



I've done this but only changed the indentation of the
custom-set-variables block and added nothing new.

And if I start from an empty ~/.emacs I got this ew block, but again, it
does not mention org-link-search-must-match-exact-headline variable:

(custom-set-variables
 ;; custom-set-variables was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 )
(custom-set-faces
 ;; custom-set-faces was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 )

What should I add *by hand* in ~/.emacs?
I'm sorry, it is just a matter of very basic elisp syntax (but I never
took the time to dig into elisp yet!).

Thank you,
Nicolas

[O] Org citations, CSL and citeproc-el

[Simonyi András]

Dear List Members,

a few days ago I've released the first public version of citeproc-el
(https://github.com/andras-simonyi/citeproc-el), a CSL 1.01 citation
processor library for Emacs. Since the main motivation of my work was to
contribute to org-mode's citation rendering I also implemented a "proof
of concept" add-on to org-ref that uses citeproc-el to render org-ref
citation links for non-LaTeX (and optionally even LaTeX) export backends
(see https://github.com/andras-simonyi/citeproc-orgref).

Both packages are in a relatively early stage of their development so
I'd be grateful to receive any feedback on them. In particular, in
citeproc-orgref I had to abuse the cite link descriptions to an even
greater degree than they were by org-ref to accommodate the full CSL
representation of citations (citations consist of cites and each cite
can have a prefix, postfix and a locator). The resulting link syntax is
rather cumbersome so I'd like to ask your opinion about introducing an
alternative org-mode citation syntax that handles all of these elements.
One option would be to use something very similar to pandoc's citation
syntax (which I tried to follow as much as possible in the cite link
descriptions of citeproc-orgref).

A more general question I'd like to raise how (or whether) you see
citeproc-el's (and CSL's) potential place in the org-mode ecosystem.
There are a lot of directions which the further development could take
(BibLaTeX support, citeproc-YAML bibliographies, CSL editing and CSL
extensions etc.) and I'd be grateful to receive your input on which ones
I should focus on.

thanks in advance & best wishes,

András Simonyi

Re: [O] problem with empty column

[Eric S Fraga]

On Friday,  5 Jan 2018 at 13:44, Uwe Brauer wrote:
> What I meant is this.

I understood what you meant and your code is working properly.  You
are checking the second column which is the column labelled E1, not
the one labelled E2 which is actually the third column... change your
if statement to check $3, not $2.

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6


signature.asc
Description: PGP signature

Re: [O] problem with empty column

[Michael Brand]

Hi Uwe

On Fri, Jan 5, 2018 at 1:44 PM, Uwe Brauer  wrote:

> But fails if there is a row like this
>
> | Name   | E1 | E2 | E3 | E4 | Res |
> |+++++-|
> | Entry1 |||||  NP |
> | Entry2 | 10 | 20 | 30 | 40 |  10 |
> | Entry3 | 10 || 20 | 30 | nan |
> #+TBLFM: $6=if("$2" == "nan", string("NP"),($2+$3+$4+$5)/10);E

I think you are looking for this:

| Name   | E1 | E2 | E3 | E4 | Res |
|+++++-|
| Entry1 ||||| NP  |
| Entry2 | 10 | 20 | 30 | 40 | 10  |
| Entry3 | 10 || 20 | 30 | NP  |
#+TBLFM: $6 = if(typeof(vsum($2..$5)) == 12 , string("NP"),
vsum($2..$5) / 10); E

See the example

if(typeof(vmean($1..$7)) == 12, string(""), vmean($1..$7); E

in the manual.

Michael

Re: [O] New git url

[Rustom Mody]

On Fri, Jan 5, 2018 at 1:33 PM, Rustom Mody  wrote:

> Ive changed .git/config thusly:
>
>
> $ diff config .git/config
> 7c7
> < url = git://orgmode.org/org-mode.git
> ---
> > url = https://code.orgmode.org/bzg/org-mode.git
>
>
Dunno why thats garbling

It is

< url = gitCOLONSLASHSLASHorgmode.org/org-mode.git
---
> url = httpsCOLONSLASHSLASHcode.orgmode.org/bzg/org-mode.git


Replace the COLONSLASHSLASH by the 3 chars '://'

Re: [O] problem with empty column

[Uwe Brauer]

"Eric" == Eric S Fraga  writes: 


   > On Friday,  5 Jan 2018 at 09:28, Uwe Brauer wrote: [...] 

   >> The last row behaves strangely the cell in the second 
   >> column is *not* empty but the cell in the third one is, 
   >> nevertheless the cell in the last column contains the 
   >> string nan, which I don't understand. 

   > But the second column is *not* empty; maybe you meant 3rd 
   > column? 


What I meant is this.

Take the following simple table

| Name   | E1 | E2 | E3 | E4 | Res | 
|+++++-| Entry1 | 10 | 30 | 40 | 50 | 
|| Entry2 | 10 | 20 | 30 | 40 | | #+TBLFM: $6=($2+$3+$4+$5)/10 


C-u C-u C-c C-c
leads to 

| Name   | E1 | E2 | E3 | E4 | Res | 
|+++++-| Entry1 | 10 | 30 | 40 | 50 | 
|13 | Entry2 | 10 | 20 | 30 | 40 |  10 | #+TBLFM: 
|$6=($2+$3+$4+$5)/10 

Now for any new entry I want to have in the 6th column NP if the 
entry in the second column (not the whole column) is empty.


| Name   | E1 | E2 | E3 | E4 | Res | 
|+++++-| Entry1 | 10 | 30 | 40 | 50 | 
|13 | Entry2 | 10 | 20 | 30 | 40 |  10 | Entry3 |||| 
|| | 


Should lead to
| Name   | E1 | E2 | E3 | E4 | Res | 
|+++++-| Entry1 | 10 | 30 | 40 | 50 | 
|13 | Entry2 | 10 | 20 | 30 | 40 |  10 | Entry3 |||| 
||  NP | 



How can I achieve that?

The following works well

| Name   | E1 | E2 | E3 | E4 | Res | 
|+++++-| Entry1 ||||| 
|NP  | Entry2 | 10 | 20 | 30 | 40 | 10  | #+TBLFM: $6=if("$2" == 
|"nan" , string("NP"),($2+$3+$4+$5)/10);E 

although the second column is *not* empty, but it is empty for 
Entry 1. 


But fails if there is a row like this


| Name   | E1 | E2 | E3 | E4 | Res | 
|+++++-| Entry1 ||||| 
|NP | Entry2 | 10 | 20 | 30 | 40 |  10 | Entry3 | 10 || 20 | 
|30 | nan | #+TBLFM: $6=if("$2" == "nan" , 
|string("NP"),($2+$3+$4+$5)/10);E 

Uwe 

Re: [O] [IT] Broken support for links to text files (both internal & external)

[Eric S Fraga]

On Friday,  5 Jan 2018 at 13:10, Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ) wrote:

[...]

> Is it possible that this setting is set by Debian packagers?
> I ask this because I reproduced this bug with and without my
>  ~/.emacs[.d/] files.

It's the default for org (at least now, as far as I can tell).

> But I ashamedly don't know how to set it permanently in my  ~/.emacs!
> Would you please help me on this?

Easy: describe the variable

  C-h v org-link-search-must-match-exact-headline RET

and then click on the "customize" link near the end of the
description.  Make sure to "Apply and set" the change you make.

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6


signature.asc
Description: PGP signature

Re: [O] [IT] Broken support for links to text files (both internal & external)

[Aʟᴏɴɢ-Tʀᴀᴄᴋ]

On 05/01/2018 08:32, Nicolas Goaziou wrote:

Hello,

"Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ)"  writes:


The regression makes several some kinds of org-mode links not to work
anymore.

Examples:

This should be a [[%5B2018-01-03%20mer.%2016:29%5D][valid link]] to
log's headline but Org can't find it
anymore and asks for the creation of a new headline:

   "No match - create this as a new heading? (yes or no)"

Also, the following links are broken:

  - [[the following links are broken][link to internal text in this
file]] (but equivalent to the
timestamped broken link reported above), reports:

"No match - create this as a new heading? (yes or no)"

  - [[should point here][link to internal text from an external
org-mode file]] (same issue
than above) which _should point here_, but reports

"No match for fuzzy expression: should point here"

The following links still work well:
  - link to a [[*headline][*headline]]
  - link to a [[* headline][* headline with space]]
  - external [[http://www.example.com/][links to the www]]

* [2018-01-03 mer. 16:29] A time stamped log headline
* headline


You probably have `org-link-search-must-match-exact-headline' set to
a non-nil value (default setting is non-nil).

Note that such links do not export correctly. For this use case, it's
better to use targets.

Regards,



Dear Nicolas,

Thank you a lot for your help.
Is it possible that this setting is set by Debian packagers?
I ask this because I reproduced this bug with and without my 
 ~/.emacs[.d/] files.


OK, I've tried and it does the trick:

  M-x set-variable RET
  org-link-search-must-match-exact-headline RET
  nil RET

But I ashamedly don't know how to set it permanently in my  ~/.emacs!
Would you please help me on this?

Nicolas

--
Nicolas Bercher
Aʟᴏɴɢ-Tʀᴀᴄᴋ
Mob: +33 651 792 011
Tel: +33 952 550 210
Fax: +33 957 550 210
http://www.along-track.com/

Re: [O] problem with empty column

[Eric S Fraga]

On Friday,  5 Jan 2018 at 09:28, Uwe Brauer wrote:

[...]

> The last row behaves strangely the cell in the second column is *not*
> empty but the cell in the third one is, nevertheless the cell in the
> last column contains the string nan, which I don't understand.

But the second column is *not* empty; maybe you meant 3rd column?

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6


signature.asc
Description: PGP signature

Re: [O] problem with empty column

[Loris Bennett]

Uwe Brauer  writes:

> Hi
>
> Consider please the following table
>
>
>
> | Name   | E1 | E2 | E3 | E4 | Res |
> |+++++-|
> | Entry1 ||||| NP  |
> | Entry2 | 10 | 20 | 30 | 40 | 10  |
>
> #+TBLFM: $6=if("$2" == "nan" , string("NP"),($2+$3+$4+$5)/10);E
>
> The last column contains a string NP if the corresponding cell in the
> second column is empty.
>
> However when   I consider
>
> | Name   | E1 | E2 | E3 | E4 | Res |
> |+++++-|
> | Entry1 |||||  NP |
> | Entry2 | 10 | 20 | 30 | 40 |  10 |
> | Entry3 | 10 || 20 | 30 | nan |
>
> #+TBLFM: $6=if("$2" == "nan" , string("NP"),($2+$3+$4+$5)/10);E
>
> The last row behaves strangely the cell in the second column is *not*
> empty but the cell in the third one is, nevertheless the cell in the
> last column contains the string nan, which I don't understand.
>
> Any help would be appreciated
>
> Thanks
>
> Uwe Brauer 

The empty column for Entry3 is in column 3 and not column 2.  Try
toggling the Col/Row numbers.

Cheers

Loris

-- 
This signature is currently under construction.

[O] problem with empty column

[Uwe Brauer]

Hi

Consider please the following table



| Name   | E1 | E2 | E3 | E4 | Res |
|+++++-|
| Entry1 ||||| NP  |
| Entry2 | 10 | 20 | 30 | 40 | 10  |
#+TBLFM: $6=if("$2" == "nan" , string("NP"),($2+$3+$4+$5)/10);E

The last column contains a string NP if the corresponding cell in the
second column is empty.

However when   I consider

| Name   | E1 | E2 | E3 | E4 | Res |
|+++++-|
| Entry1 |||||  NP |
| Entry2 | 10 | 20 | 30 | 40 |  10 |
| Entry3 | 10 || 20 | 30 | nan |
#+TBLFM: $6=if("$2" == "nan" , string("NP"),($2+$3+$4+$5)/10);E


The last row behaves strangely the cell in the second column is *not*
empty but the cell in the third one is, nevertheless the cell in the
last column contains the string nan, which I don't understand.

Any help would be appreciated

Thanks

Uwe Brauer 

[O] New git url

[Rustom Mody]

Ive changed .git/config thusly:


$ diff config .git/config
7c7
< url = git://orgmode.org/org-mode.git
---
> url = https://code.orgmode.org/bzg/org-mode.git

As best as I can see its working!

Questions

1. Is this right?
2. This change should probably go up on the main web-page somewhere since
the mailing list hides mail-addresses. So we can make out that something
needs change but not exactly what!