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

[Michael Welle]

Hello,

thank you all, who are involved in keeping Org going. Not only the
people, who provide infrastructure, but also the people, who do the daily
work, who provide patches and the people, who use Org.

Bastien Guerry  writes:

> Dear all,
>
> thanks to Jason Dunsmore, we were able to have our orgmode.org server
> sponsored by Rackspace.  Their OSS hosting program ends by the end of
> the year¹.  Thanks a lot to Rackspace for this program, it saved us a
> lot of money!  And to Jason for letting us know about it.
>
> I have configured a new server: a vultr.com Debian 9 x64 with 1024 MB
> at 5$ per month -- for a start.
Is there a way to throw a bit of money on the project, not using the
company behind the support button on the web page?

Regards
hmw

Re: [O] Preventing noweb substitution during export

[Nicolas Goaziou]

Hello,

"Thomas S. Dye"  writes:

> Good news. When will the switch from doc/org.texi to
> contrib/manual.org take place?

I don't know. I was only anticipating the ineluctable ;)

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: List does not fold correctly with inline tasks in the middle [9.1.4 (9.1.4-13-g84cb63-elpa @ /home/yantar92/.emacs.d/elpa/org-20171218/)]

[Nicolas Goaziou]

Hello,

Marco Wahl  writes:

> I just committed your suggestion of org-inlinetask-goto-end.  I also
> edited the respective test section.  LGTM for now.

Thank you!

Regards,

-- 
Nicolas Goaziou

Re: [O] Can export the files with bibliography only to LaTeX

[Melleus]

Accidentally I've found that until there are no "Online" type of
references Org exports both to text and html. When there is at least one
"Online" reference, I got "Wrong type argument: stringp, nil" error. I
don't know whether this is a bug or some misconfiguration. But might
someone will check out if this is reproducible. One-liner with
cite:cite-to-online-kind-source is enough for my system to get the
error.

Re: [O] Preventing noweb substitution during export

[Thomas S. Dye]

Patches welcome! Org manual is now an Org file, it should be 
much more

pleasant to edit. :)


Good news. When will the switch from doc/org.texi to 
contrib/manual.org take place?


All the best,
Tom

--
Thomas S. Dye
http://www.tsdye.com

Re: [O] Bug: List does not fold correctly with inline tasks in the middle [9.1.4 (9.1.4-13-g84cb63-elpa @ /home/yantar92/.emacs.d/elpa/org-20171218/)]

[Marco Wahl]

Hi!

> 'Ihor Radchenko'  writes:
>
>> 1. Create the following same org file:
>> * Test
>>   - blah
>> - a
>> - b
>> - c
>> *** List folding stops here
>>  :PROPERTIES:
>>  :ID:   27eb85b6-114f-437f-9424-b28d400f6aa9
>>  :END:
>> *** END
>> - everything here and below folds on tab at =**...END=
>> - f
>>
>> 2. Try to fold at =-blah=. Everything started from inline task is not
>> folded, while should.
>>
>> 3. Try to fold at =*... END=. Everything below *is* folded, while should
>> not.
>
> Confirmed.
>
> This is related to:
>
> commit a426abffa55f3b74d0c5fb09e148c1dd0d2a0e7a
> Author: Marco Wahl 
> Date:   Fri Dec 4 19:25:36 2015 +0100
>
> org-inlinetask: Fix folding inlinetask children
> 
> * org-inlinetask.el(org-inlinetask-goto-end): Position point just at the
>   end.  Do not forward-line.
> 
> Fixes org-cycle for state CHILDREN when the children are inlinetasks
> which have immediate neigbors.
>
> Marco, I think there is something wrong in the patch above.
> `org-inlinetask-goto-end' should move point to the beginning of the next
> line, not to the end of the last one. IOW, it should something like this:
>
> (defun org-inlinetask-goto-end ()
>   "Go to the end of the inline task at point.
> Return point."
>   (save-match-data
> (beginning-of-line)
> (let* ((case-fold-search t)
>(inlinetask-re (org-inlinetask-outline-regexp))
>(task-end-re (concat inlinetask-re "END[ \t]*$")))
>   (cond
>((looking-at-p task-end-re)
> (forward-line))
>((looking-at-p inlinetask-re)
> (forward-line)
> (cond
>  ((looking-at-p task-end-re) (forward-line))
>  ((looking-at-p inlinetask-re))
>  ((org-inlinetask-in-task-p)
>   (re-search-forward inlinetask-re nil t)
>   (forward-line))
>  (t nil)))
>(t
> (re-search-forward inlinetask-re nil t)
> (forward-line)
>   (point))
>
> The bug your patch is fixing probably lies in `org-cycle'.
>
> WDYT?

Thanks!

I just committed your suggestion of org-inlinetask-goto-end.  I also
edited the respective test section.  LGTM for now.


Sorry for the disturbance in the Org and best regards
 Marco

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

[Bastien Guerry]

Dear all,

thanks to Jason Dunsmore, we were able to have our orgmode.org server
sponsored by Rackspace.  Their OSS hosting program ends by the end of
the year¹.  Thanks a lot to Rackspace for this program, it saved us a
lot of money!  And to Jason for letting us know about it.

I have configured a new server: a vultr.com Debian 9 x64 with 1024 MB
at 5$ per month -- for a start.

I will make the DNS switch to the new server on the 30/12/2017 between
8pm CET and midnight CET.

**IF YOU USE GIT FOR ORG/WORG, YOU NEED TO UPDATE YOUR REPOSITORIES!**

If you don't use Git for Org, you can jump directly to the end of this
email, where I explain the purpose of code.orgmode.org.


For Org/Worg USERS who use Git to clone Org/Worg
=

After 31/12/2017 (leaving a 24h window for DNS propagation), the only
way to clone the Org git repository will be through our Gogs instance:

  https://code.orgmode.org/bzg/org-mode

If you cloned from the old server, your current .git/config file has:

[remote "origin"]
url = orgm...@orgmode.org:org-mode.git
fetch = +refs/heads/*:refs/remotes/origin/*

You can clone Org from the new server with one of these commands:

~$ git clone g...@code.orgmode.org:bzg/org-mode.git
~$ git clone https://code.orgmode.org/bzg/org-mode.git

In the newly created repository, your .git/config file will now read:

[remote "origin"]
url = g...@code.orgmode.org:bzg/org-mode.git
fetch = +refs/heads/*:refs/remotes/origin/*

or

[remote "origin"]
url = https://code.orgmode.org/bzg/org-mode.git
fetch = +refs/heads/*:refs/remotes/origin/*

You can also use https instead of git, see the repository page.

Instructions are similar for Worg.


For Org and Worg COMMITTERS


You will need to create a new user on https://code.orgmode.org in
order to push commits to org-mode.git or worg.git:

1. Create a user on https://code.orgmode.org
2. Add your ssh public key
3. Send me an email to be added as a collaborator on Org/Worg


Why code.orgmode.org ?
===

The https://code.orgmode.org gogs instance is intended as being a home
for every Org developers, whether they are contributing to Org's core,
Worg documentation - or any other Org-related package.  The idea is to
create a place for code that we collectively take care of.

New Org packages are already welcome.

Mirrors for active Org packages are welcome.

Also, I would like to migrate Elisp files currently in Org's contrib/
directory as separate packages on https://code.orgmode.org.


Testing the new server
===

You can test the new website here: https://beta.orgmode.org

If someone asks anywhere about a broken Org repository, please refer
to this email.

Happy hacking and *thanks*!

¹ 
https://www.theregister.co.uk/2017/10/20/rackspace_ends_discount_hosting_for_open_source_projects/

-- 
 Bastien

Re: [O] Tags aliases

[Eduardo Mercovich]

Hello Ihor.

I am not aware about aliases explicitly, but you can use tag 
hierarchy in your use case:

http://orgmode.org/manual/Tag-hierarchy.html#Tag-hierarchy [...]


That was exactly what I was searching for, thank you very much. :)

Have a great day... 


--
eduardo mercovich

Donde se cruzan tus talentos 
con las necesidades del mundo, 
ahí está tu vocación. 
(Anónimo)

[O] [SOLVED] Re: babel header argument :var is not expanded when tangling

[stardiviner]

   tangles to

   (let ((x (quote "hi")))
   (message x))


This is what I want. Problem solved.

On 12/28/2017 09:20 AM, Grant Rettke wrote:

They work differently. Try this example:

#+BEGIN_SRC emacs-lisp :var x="hi"
(message x)
#+END_SRC

tangles to

(let ((x (quote "hi")))
(message x))

but this

#+NAME: x
#+BEGIN_SRC emacs-lisp
"hi"
#+END_SRC

#+BEGIN_SRC emacs-lisp
(message «x»)
#+END_SRC

tangles to this

(message "hi"


Sincerely,

Grant Rettke

On Mon, Dec 25, 2017 at 6:45 AM, numbch...@gmail.com 
 > wrote:



I see. I will use noweb style for now.
But should tangle expand :var variables when tangling? I think
this is the correct behaviour.

[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 Sun, Dec 24, 2017 at 11:40 PM, Grant Rettke
> wrote:

> Here is a quick test:
>
> * Test tangle will auto expand and substitute :var
>
> #+begin_src js :tangle kk.js
> console.log("hello, world!");
> #+end_src
>
> #+begin_src js :var name="chris" :tangle require-kk.js
> // require("kk.js");
> console.log("Hi, ", name);
> #+end_src
>
> #+RESULTS:
> : Hi,  chris
>
> #+NAME: check whether tangle expand and substitute :var
> #+begin_src shell
> cat require-kk.js
> #+end_src
>
> #+RESULTS: check whether tangle expand and substitute :var
> : var name="chris";
> : console.log("Hi, ", name);
>
> The upper result should be: ~console.log("Hi, ", "chris");~.

Here are your two source blocks. They each do literate
programming,
one with Variable style and the other with Noweb style. When you
evaluate them you get an identical result. When you tangle
them you
get two different pieces of code, that generate the same
result. You
can peek at what the tangled code will look like by calling
org-babel-expand-src-block inside the source block. That is how it
will look in the tangled file. I think that want Noweb style.

When I use the Variable approach like this

#+begin_src js :var name="chris" :tangle kk.js
console.log("Hi, ", name);
#+end_src

I get this in the tangled output file

var name="chris";
console.log("Hi, ", name);

When I use the the Noweb approach like this

#+NAME: name
#+BEGIN_SRC emacs-lisp
chris
#+END_SRC

#+NAME:
org_gcr_2017-12-23_mara_3D887FDD-163D-4BE1-80E8-464BF29DABEA
#+BEGIN_SRC js :tangle noweb-kk.js :comments no
console.log("Hi, ", "«name»");
#+END_SRC

I get this in the tangled  output file

console.log("Hi, ", "chris");

WDYT?

Re: [O] Tags aliases

[Ihor Radchenko]

Dear Eduardo,

I am not aware about aliases explicitly, but you can use tag hierarchy
in your use case:
http://orgmode.org/manual/Tag-hierarchy.html#Tag-hierarchy

It will be something like

#+TAGS: [ food : vegetables snack ]

Regards,
Ihor


Eduardo Mercovich  writes:

> Dear Orgers.
>
> Orgmode has extensive support for tags. However, even after some 
> extensive search (maybe I used the wrong keywords) I couldn't 
> found info on how to create tags aliases.
>
> As an example, lets assume we have a heading with the tag :snack: 
> and another with :vegetables:. And I'd like to be able to find 
> them both when searching for :food:.
> How can we do this?
>
> As always, thanks a lot for your time and attention... :)
>
>
> -- 
> eduardo mercovich
>
>  Donde se cruzan tus talentos 
>  con las necesidades del mundo, 
>  ahí está tu vocación. 
>  (Anónimo)
>

-- 
Ihor Radchenko,
PhD Student
Singapore University of Technology and Design,
8 Somapah Road Singapore 487372
Email: yanta...@gmail.com, ihor_radche...@mymail.sutd.edu.sg
Tel: +6584017977


signature.asc
Description: PGP signature

[O] Tags aliases

[Eduardo Mercovich]

Dear Orgers.

Orgmode has extensive support for tags. However, even after some 
extensive search (maybe I used the wrong keywords) I couldn't 
found info on how to create tags aliases.


As an example, lets assume we have a heading with the tag :snack: 
and another with :vegetables:. And I'd like to be able to find 
them both when searching for :food:.

How can we do this?

As always, thanks a lot for your time and attention... :)


--
eduardo mercovich

Donde se cruzan tus talentos 
con las necesidades del mundo, 
ahí está tu vocación. 
(Anónimo)

Re: [O] Preventing noweb substitution during export

[Nicolas Goaziou]

Hello,

swfl...@flintfam.org (Samuel W. Flint) writes:

> Nicolas, my apologies for sending this twice.
>> Nicolas Goaziou writes:
>
> NG> Hello, swfl...@flintfam.org (Samuel W. Flint) writes:
>
> >> I used to be able to prevent noweb substitution during export by
> >> setting noweb to tangle, now it's only a yes/no option.  When was
> >> this feature removed, and what can I do to get it back?
>
> NG> I don't think that was intended. Would you have an ECM
> NG> demonstrating the issue?
>
> It didn't get removed, though no-export is now the correct value.
> Neither, however, are currently documented in the manual.

Patches welcome! Org manual is now an Org file, it should be much more
pleasant to edit. :)

> And the following should demonstrate how they currently behave:
>
> #+BEGIN_EXAMPLE
> #+PROPERTY: :noweb tangle

This should be:

  #+property: header-args :noweb tangle

> #+name: a
> #+begin_src python
>   def foo():
>   print "foo"
> #+end_src
>
> #+name: b
> #+begin_src python
>
>
>   <>
>
>   foo() #+end_src
>
> #+name: c
> #+begin_src python :tangle "test.py"
>
>   import bar
>   <>
> #+end_src
> #+END_EXAMPLE
>
> The file 'test.py' will contain:
>
> import bar
> <>
>
> foo()
>
> If noweb is set to no-export, the <> will be resolved.  However, with
> tangle, the block is included during export.

I cannot reproduce it. The following document:

--8<---cut here---start->8---
#+PROPERTY: header-args :noweb tangle

#+name: a
#+begin_src python
  def foo():
  print "foo"
#+end_src

#+name: b
#+begin_src python


  <>

  foo()
 #+end_src

#+name: c
#+begin_src python :tangle "test.py"

  import bar
  <>
#+end_src
--8<---cut here---end--->8---

becomes

--8<---cut here---start->8---
┌
│ def foo():
│ print "foo"
└

┌
│ 
│ 
│ <>
│ 
│ foo()
└

┌
│ 
│ import bar
│ <>
└
--8<---cut here---end--->8---

when exported to UTF-8.

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: org-table-separator-space breaks alignment of existing tables [9.1.5 (9.1.5-1-gb3ddb0-elpaplus @ /home/il/.emacs.d/elpa/org-plus-contrib-20171225/)]

[Nicolas Goaziou]

Hello,

Ingo Lohmar  writes:

> Here's a simple table example that breaks (info and columns lost etc) on
> `org-table-align`.  I traced it down to org-table-separator-space ---
> setting it to a plain " " (effectively the situation before the last
> 9.1.5 commit) works for me, but I do not understand why the change
> breaks that.  Or is this "breakage" expected?
>
> | No | Name| cpr1 | drv1 | ?ch1 | fla1 | xt12 | enh   | pit1 
> | mtd1 | dly1 | xt11 | xt1 (2) | Amp [sd0 but def.3]  | Cab   
>|   Rev | Comment|| WIP/TODO   
>|
> || |  |  |  |  |  | rt/ph/trm |  
> |  |  |  | |  |   
>|   |||
>|
> |+-+--+--+--+--+--+---+--+--+--+--+-+--+--+---+++---|
> |  0 | JC 120  |4 |  |8 |2 |  |   |  
> |4 |2 | DlyIn 30-100% | | brt m10  | 94 2x12 slv 
> alnico   |   sm room | 102bpm; orig ~CE-1 (more shimmer etc) |
> |   |

Confirmed. There is an issue in maint, but not in master, as far as my
testing goes.

Since we are close to Emacs release, I'd rather postpone this change, so
I reverted it in maint branch while keeping it in master.

Regards,

-- 
Nicolas Goaziou