Re: [O] Some projects

On Sun, Oct 25, 2015 at 3:02 PM, Rasmus wrote: > Hi, > > First, thanks for writing this up, Nicolas. Org has been a bit slow > lately, at least for my part. > ditto. and thanks to eveyrone in the thread for their input. > > > > > ** Citations > > > > Development apparently stopped for some re

[O] org-crypt & multiple recipients

I was playing with org-crypt today and it's pretty nifty. While encrypting things for myself is the primary use case, I have other team members that also use org-mode. It occurred to me that it would be neat if I could specify a list of users to encrypt a node for. Then we could share an org file

Re: [O] Some projects

Hi Nicolas, Thanks for writing this up. It is important to think about, and ultimately solve, all the issues you raise. 2015ko urriak 25an, Nicolas Goaziou-ek idatzi zuen: > > Hello, > > I'd like to see some features moving forward, and some important issues > fixed, hopefully, in the next mon

Re: [O] org-reveal questions

On Sun, Oct 25, 2015 at 4:46 PM, Eric S Fraga wrote: > Hello all, > > So, I decided I would play with org-reveal some more, just to see if I > could get some of the functionality that Xebar wanted fairly > easily. It turns out that I could use a web based presentation for a > small PR exercise..

Re: [O] Some projects

Anders Johansson gmail.com> writes: > I hacked together something like this a while ago when I needed to add > inline-comments that would later be exported as odt-comments (but I also > made it work for latex). > > I chose to implement it via a unicode-bracket ❰❙❱, like this: > > ❰Simple commen

Re: [O] Some projects

Marcin Borkowski mbork.pl> writes: > > > On 2015-10-25, at 19:12, Nicolas Goaziou nicolasgoaziou.fr> wrote: > > > Fabrice Popineau supelec.fr> writes: > > > >> 2015-10-25 18:57 GMT+01:00 Thomas S. Dye tsdye.com>: > >> > >> > >>> would suggest an alternate wording. In this case, it would be

Re: [O] org-reveal questions

Hello all, So, I decided I would play with org-reveal some more, just to see if I could get some of the functionality that Xebar wanted fairly easily. It turns out that I could use a web based presentation for a small PR exercise... I've run into two stumbling blocks using org-reveal. First, th

Re: [O] Some projects

naturally, long-form emphasis can look like $[emphasis ...].

Re: [O] Some projects

i like some of these ideas, particularly lexical. org already has a lot of syntax. i am leery of introducing yet more heterogenous syntax to org. key word heterogenous. i don't mind more features if it is always using the same syntax framework and thus can take advantage of everything else that

[O] How can I call the exporter from function?

I want to call the exporter in a certain way, so I don't have to type the same options every time. Basically I want to do first this: (re-search-backward "^\\*\\* ") (org-mark-subtree) Then I want to export the marked subtree as odt. With command keys it becomes something like: c-c c-e c

Re: [O] Some projects

Nicolas Goaziou writes: > Thomas S. Dye writes: > >> Nicolas Goaziou writes: >> >>> The full proposal was at >>> but it didn't get >>> much positive feedback. Therefore I suggested a simplified version, with >>> a single author. >> >> In m

Re: [O] Some projects

Thomas S. Dye writes: > Would tangling honor #+OPTIONS: :student1? #+OPTIONS: @:... is for export, so I guess not. Though, it can be implemented later. Regards,

Re: [O] Some projects

Thomas S. Dye writes: > Nicolas Goaziou writes: > >> The full proposal was at >> but it didn't get >> much positive feedback. Therefore I suggested a simplified version, with >> a single author. > > In my case, the lack of positive feedback

Re: [O] Some projects

Nicolas Goaziou writes: > The full proposal was at > but it didn't get > much positive feedback. Therefore I suggested a simplified version, with > a single author. In my case, the lack of positive feedback was "too much org, too little tim

Re: [O] Some projects

On 2015-10-25, at 20:02, Rasmus wrote: >> ** Backslash escaping > > Would be nice at times. > > I strongly disagree with introducing XML or LaTeX like syntax as is > suggested a bit further down in the thread. Since it seems I'm the only one that proposed (and liked) that idea, let me reiterate

Re: [O] Some projects

On 2015-10-25, at 19:22, Eric S Fraga wrote: > By the way, I personally would like inline annotations, along the lines > of inline footnotes. Just saying... +1 -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz Unive

Re: [O] Some projects

On 2015-10-25, at 19:12, Nicolas Goaziou wrote: > Fabrice Popineau writes: > >> 2015-10-25 18:57 GMT+01:00 Thomas S. Dye : >> >> >>> would suggest an alternate wording. In this case, it would be super >>> helpful to have a function that replaced annotated text with the >>> annotation, so the a

Re: [O] Some projects

Hi, First, thanks for writing this up, Nicolas. Org has been a bit slow lately, at least for my part. Perhaps, we should keep a file in org-mode.git which links back to discussions (TODO.org). There’s a couple of other things that we discussed recently. > ** Citations > > Development apparentl

Re: [O] Bug: Regressions from 8.2.10 (8.2.10-35-g19a7d6-elpaplus) to master/maint

Nicolas Goaziou writes: > Could you provide an ECM with appropriate CLOCK lines? Attached. * Other files: ** init.el: #+BEGIN_SRC emacs-lisp (add-to-list 'load-path "~/repo/org-mode/lisp") (add-to-list 'load-path "~/repo/org-mode/contrib/lisp") (require 'org) (setq org-directory "~/org"

Re: [O] Some projects

Marcin Borkowski writes: > On 2015-10-25, at 17:37, Nicolas Goaziou wrote: > >> I cannot think of any bad consequence if we tailor "border" in >> `org-emphasis-regexp-components' to allow everything but white spaces. > > I don't know, I guess I would welcome such change! Done in b4af3f0. We'll

Re: [O] Some projects

On Sunday, 25 Oct 2015 at 19:12, Nicolas Goaziou wrote: > The full proposal was at > but it didn't get > much positive feedback. Therefore I suggested a simplified version, with > a single author. It's a start and that's infinitely better than

Re: [O] Org-mode reinvented?

On 2015-10-25, at 16:55, Ken Mankoff wrote: > On 2015-10-25 at 07:12, John Kitchin wrote: >> Interesting. One day I imagine something like this, or sharelatex >> exists for collaborating on org-files with people who don't like >> Emacs... > > One can hope, but unfortunately it seems Markdown is

Re: [O] Some projects

On 2015-10-25, at 17:37, Nicolas Goaziou wrote: > Marcin Borkowski writes: > >> Since your point is quite valid - and OTOH, I would like to put anything >> (or almost anything) in =code= markup, for instance (my use case: Emacs >> keybindings, try =C-x ,= - Org won't recognize it as code!). I

Re: [O] Some projects

Fabrice Popineau writes: > 2015-10-25 18:57 GMT+01:00 Thomas S. Dye : > > >> would suggest an alternate wording. In this case, it would be super >> helpful to have a function that replaced annotated text with the >> annotation, so the author could easily accept the editor's suggestion. >> >> > I

Re: [O] Some projects

2015-10-25 18:57 GMT+01:00 Thomas S. Dye : > would suggest an alternate wording. In this case, it would be super > helpful to have a function that replaced annotated text with the > annotation, so the author could easily accept the editor's suggestion. > > In this case, it would be nice if annot

Re: [O] Some projects

Nicolas Goaziou writes: > Hello, > > I'd like to see some features moving forward, and some important issues > fixed, hopefully, in the next months. I'm sharing them here so that > anyone interested can help. > > ** Annotations > > It would be nice to allow annotating text in Org. I already made

Re: [O] Org-agenda-leaders

Nick Dokos writes: > Oops - sorry: I didn't realize that. I didn't even notice the CLOCK > defconst. As a matter of curiosity, what's the back story here? Backward compatibility. What else? A defconst prevent anyone from using anything else than "DEADLINE:" and "SCHEDULED:" (I cannot remember ex

Re: [O] Bug: Regressions from 8.2.10 (8.2.10-35-g19a7d6-elpaplus) to master/maint

Jan Malakhovski writes: > Nicolas Goaziou writes: > >>> * Pressing on an entry in org-agenda-list moves the cursor to the >>> corresponding node. >>> >>> Previously it moved the cursor to the corresponding CLOCK: line and I >>> used that a lot. >> >> According to `org-agenda-goto''s docst

Re: [O] [PATCH] make org-clock-time% respect org-effort-durations and related

Hello, Jan Malakhovski writes: > Hi. > > The first patch here is a must, because it fixes a bug I stumble upoon > daily. Middle two are just to make the names consistent. While doing > all those changes I read quite a lot of code and the last patch adds a > FIXME for a particularly ugly place I'

Re: [O] org-agenda-scheduled-leaders and repeating tasks

Nicolas Goaziou writes: > Matt Lundin writes: > >> In short, org-habit seems to want a + notation for the purposes of the >> agenda display and a .+ notation for the purposes of resetting the >> timestamp. What is the best solution? > > Still looking for it. > > Meanwhile, I reverted the opinion

Re: [O] [PATCH] Fix `org-capture-templates' type declaration

Nicolas Goaziou writes: > Grégoire Jadi writes: > >> With my patch, the customization interface looks like this >> - for a file : >> Target location: Value Menu File: >> File: Value Menu File: ~/org/notes.org >> >> - for a variable : >> Target location: Value Menu File: >> File: Value Menu V

[O] Behaviour of org-open-at-point and org-return (was commit 4e864643 breaks org-return)

Mail von Stefan-W. Hahn, Sat, 24 Oct 2015 at 08:48:47 +0200: Hello, as I observed there is a change in behaviour of org-return from on commit 4e864643bdb6bba3e000ea51fb746a26e40b1f77 Author: Nicolas Goaziou Date: Sun Oct 18 09:36:15 2015 +0200 for timestamps, date ranges and any link. The s

Re: [O] Some projects

Marcin Borkowski writes: > Since your point is quite valid - and OTOH, I would like to put anything > (or almost anything) in =code= markup, for instance (my use case: Emacs > keybindings, try =C-x ,= - Org won't recognize it as code!). I could > mess up with org-emphasis-regexp-components in e.

Re: [O] Some projects

On 2015-10-25, at 16:45, Eric S Fraga wrote: > On Sunday, 25 Oct 2015 at 14:08, Nicolas Goaziou wrote: >> Hello, >> >> I'd like to see some features moving forward, and some important issues >> fixed, hopefully, in the next months. I'm sharing them here so that >> anyone interested can help. > >

Re: [O] org-agenda-scheduled-leaders and repeating tasks

Matt Lundin writes: > In short, org-habit seems to want a + notation for the purposes of the > agenda display and a .+ notation for the purposes of resetting the > timestamp. What is the best solution? Still looking for it. Meanwhile, I reverted the opinionated change in a427098b57c747ecc76feb0

Re: [O] Some projects

Eric S Fraga writes: > I'm concerned that it will make typing normal text more onerous. Right > now, org is quite non-intrusive in most of my writing yet is quite rich > in what it can encode. Having to backslash symbols that I use in text > quite often (especially square brackets) would be ann

Re: [O] Some projects

Marcin Borkowski writes: > That sounds interesting, though I don't really see much difference > between this and plain simple comments. 1. you cannot simply inline comments (you need to create a new link type or some such); 2. you cannot mark exactly where the comment applies. >> ** Ba

Re: [O] Org-mode reinvented?

On 2015-10-25 at 07:12, John Kitchin wrote: > Interesting. One day I imagine something like this, or sharelatex > exists for collaborating on org-files with people who don't like > Emacs... One can hope, but unfortunately it seems Markdown is the default implementation for people supporting a s

Re: [O] Some projects

On Sunday, 25 Oct 2015 at 14:08, Nicolas Goaziou wrote: > Hello, > > I'd like to see some features moving forward, and some important issues > fixed, hopefully, in the next months. I'm sharing them here so that > anyone interested can help. Nicolas, I look forward to all the advances you have pro

Re: [O] [PATCH] Fix `org-capture-templates' type declaration

Grégoire Jadi writes: > With my patch, the customization interface looks like this > - for a file : > Target location: Value Menu File: > File: Value Menu File: ~/org/notes.org > > - for a variable : > Target location: Value Menu File: > File: Value Menu Variable: nil > > - for a function : >

Re: [O] Bug: Regressions from 8.2.10 (8.2.10-35-g19a7d6-elpaplus) to master/maint

Nicolas Goaziou writes: >> * Pressing on an entry in org-agenda-list moves the cursor to the >> corresponding node. >> >> Previously it moved the cursor to the corresponding CLOCK: line and I >> used that a lot. > > According to `org-agenda-goto''s docstring, this doesn't look like > a fea

Re: [O] Bug: Regressions from 8.2.10 (8.2.10-35-g19a7d6-elpaplus) to master/maint

Hello, Jan Malakhovski writes: > * C-c C-x C-i clocks in into a wrong node. > Instead of clocking-in into the node under cursor it clock-ins into the > next one. Fixed. Thank you. > * Pressing on an entry in org-agenda-list moves the cursor to the > corresponding node. > > Previously

Re: [O] Some projects

On 2015-10-25, at 14:08, Nicolas Goaziou wrote: > Hello, > > I'd like to see some features moving forward, and some important issues > fixed, hopefully, in the next months. I'm sharing them here so that > anyone interested can help. > > > * Features > > ** Citations > > Development apparently st

[O] Bug: Regressions from 8.2.10 (8.2.10-35-g19a7d6-elpaplus) to master/maint

Hi. Emacs : GNU Emacs 24.5.2 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.28) of 2015-10-05 on localhost Current package: Org-mode version 8.3.2 (release_8.3.2-209-gba4d33 @ /home/oxij/repo/org-mode/lisp/) (actually, both master and maint) Previous package: Org-mode version 8.2.10 (8.

[O] [PATCH 1/2] factor out date-timestamp* calculations to org-store-link-props

--- contrib/lisp/org-mew.el | 11 +-- contrib/lisp/org-vm.el | 11 +-- contrib/lisp/org-wl.el | 10 +- doc/org.texi| 4 ++-- lisp/org-gnus.el| 15 +-- lisp/org-mhe.el | 10 +- lisp/org-rmail.el | 11 +-- lisp/

[O] [PATCH] remove some copy-paste and add date support to org-notmuch-store-link

Cheers, Jan Jan Malakhovski (2): factor out date-timestamp* calculations to org-store-link-props org-notmuch: add date support to org-notmuch-store-link contrib/lisp/org-mew.el | 11 +-- contrib/lisp/org-notmuch.el | 7 --- contrib/lisp/org-vm.el | 11 +-- con

[O] [PATCH 2/2] org-notmuch: add date support to org-notmuch-store-link

--- contrib/lisp/org-notmuch.el | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/contrib/lisp/org-notmuch.el b/contrib/lisp/org-notmuch.el index 712ec5a..265742e 100644 --- a/contrib/lisp/org-notmuch.el +++ b/contrib/lisp/org-notmuch.el @@ -71,15 +71,16 @@ Should accept a

Re: [O] [PATCH] Fix `org-capture-templates' type declaration

Nicolas Goaziou writes: > Hello, Hi, Thanks for the reply. > Grégoire Jadi writes: > >> The attached patch fix the type declaration of org-capture-templates by >> allowing the user to use file, variable, function and sexp as target's >> file to match the documentation > > Thank you. > >> -

[O] Some projects

Hello, I'd like to see some features moving forward, and some important issues fixed, hopefully, in the next months. I'm sharing them here so that anyone interested can help. * Features ** Citations Development apparently stopped for some reason. We have a citation syntax for Org in wip-cite a

[O] [PATCH 4/4] org-colview: add a FIXME

--- lisp/org-colview.el | 3 +++ 1 file changed, 3 insertions(+) diff --git a/lisp/org-colview.el b/lisp/org-colview.el index 1113adc..4f09766 100644 --- a/lisp/org-colview.el +++ b/lisp/org-colview.el @@ -1113,6 +1113,9 @@ display, or in the #+COLUMNS line of the current buffer." ((memq

[O] [PATCH 2/4] org: move org-duration-string-to-minutes to a better place

--- lisp/org.el | 40 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 088913c..453ed37 100755 --- a/lisp/org.el +++ b/lisp/org.el @@ -18329,6 +18329,26 @@ If no number is found, the return value is 0." (s

[O] [PATCH 1/4] org-clock: make org-clock-time% respect org-effort-durations

This also fixes a bug with time percents looking pretty much random and adding to a number that is less than 100% when a clock report has long intervals (e.g. days). --- lisp/org-clock.el | 29 +++-- 1 file changed, 11 insertions(+), 18 deletions(-) diff --git a/lisp/org-c

[O] [PATCH] make org-clock-time% respect org-effort-durations and related

Hi. The first patch here is a must, because it fixes a bug I stumble upoon daily. Middle two are just to make the names consistent. While doing all those changes I read quite a lot of code and the last patch adds a FIXME for a particularly ugly place I'm not sure how to fix (I think don't ever con

[O] [PATCH 3/4] rename org-duration-string-to-minutes to org-clocksum-string-to-minutes everywhere

--- contrib/lisp/org-depend.el | 2 +- contrib/lisp/ox-taskjuggler.el | 2 +- lisp/org-agenda.el | 2 +- lisp/org-clock.el | 14 +++--- lisp/org-colview.el| 2 +- lisp/org.el| 14 +- 6 files changed, 20 insertions

Re: [O] Macro question

On Sunday, 25 Oct 2015 at 10:45, Fabrice Popineau wrote: [...] > In this case, the parameter that has to be made easily editable > is the width of the column. (Thinking about a common interface for > beamer and reveal) Column mode is great for editing such things. However, we would need (as has

Re: [O] [PATCH] org-id-goto doesn't work if buffer is narrowed.

Hi Puneeth, Puneeth Chaganti writes: >> However, you need to make sure that it only widens if ID is in the same >> buffer and outside of the narrow. In particular, when ID is in another >> file you shouldn’t widen. When it’s within the scope of the narrow it >> shouldn’t widen. This ALREADY s

Re: [O] Org-mode reinvented?

Interesting. One day I imagine something like this, or sharelatex exists for collaborating on org-files with people who don't like Emacs... Marcin Borkowski writes: > Hi all, > > I've just stumbled over this: https://gingkoapp.com/ . From a cursory > glance it seems like a web-based, proprietary

Re: [O] [PATCH] org-id-goto doesn't work if buffer is narrowed.

In my solution I do store the buffer. Maybe for some reason the id is in another buffer with narrowing, and you want to preserve that narrowing when you return. I originally did that with a marker, so you could restore point to, but I decided to take that out. I wasn't aware you could have dangling

Re: [O] [PATCH] org-id-goto doesn't work if buffer is narrowed.

> If CMD raises an error, you have a dangling marker in the buffer, which > is not a great idea. I suggest to wrap everything into > a `unwind-protect' and add (set-marker m nil) as an unwindform, i.e., Fixed. Thanks! From 8ec4f777a2e1078e1fadc48a7c91366200a0d37b Mon Sep 17 00:00:00 2001 From: Pun

Re: [O] Macro question

2015-10-24 19:02 GMT+02:00 Eric S Fraga : > On Saturday, 24 Oct 2015 at 13:37, Fabrice Popineau wrote: > > [...] > > > I find that using headers as in beamer is not pleasant (maybe that is > just > > me ?) > > Just to help you understand the positive aspect of headlines for > structure in beamer,

Re: [O] [PATCH] org-id-goto doesn't work if buffer is narrowed.

Puneeth Chaganti writes: > Thanks for your careful review and detailed comments. I've attached > an updated patch. Thank you. I have another suggestion about it. > +(defun org-id-show (id cmd) > + "Show an entry with id ID by buffer-switching using CMD. > +CMD is a function that takes a buffe

Re: [O] [PATCH] org-id-goto doesn't work if buffer is narrowed.

Hi Nicolas, On Sun, Oct 25, 2015 at 2:08 PM, Nicolas Goaziou wrote: > Hello, > > Puneeth Chaganti writes: > >> Here is a patch that works for the case you describe. > > Thank you. Some comments follow. Thanks for your careful review and detailed comments. I've attached an updated patch. -- Pu

Re: [O] Bug: horizontal lines in tables [8.2.10 (release_8.2.10 @ /usr/local/share/emacs/24.5/lisp/org/)]

Guido Kraemer writes: > If you do |- TAB and the table does not have to be realigned, then the > horizontal line will not show up until the next time the table has to > be realigned. Could you show an example? Regards,

Re: [O] [PATCH] Fix `org-capture-templates' type declaration

Hello, Grégoire Jadi writes: > The attached patch fix the type declaration of org-capture-templates by > allowing the user to use file, variable, function and sexp as target's > file to match the documentation Thank you. > - (file :tag " File")) > +

Re: [O] [PATCH] org-id-goto doesn't work if buffer is narrowed.

Hello, Puneeth Chaganti writes: > Here is a patch that works for the case you describe. Thank you. Some comments follow. > + (org-id-show id 'org-pop-to-buffer-same-window)) (org-id-show id #'org-pop-to-buffer-same-window) > +(defun org-id-show (id cmd) > + "Show an entry with id ID by b