Hi Rainer,
The presence of the file column in the clocktable depends on the scope.
Removing the headline column is not an option, I don't see many cases
were it would be useful, except corner-cases.
Rainer Stengele writes:
> In the past I just copied the org-clocktable-write-default and
> modi
Hi Grant,
Grant Rettke writes:
> Here is how it works, the same way as the other ones:
If needed, don't hesitate to advertize this in the comment section
of the code.
Thanks!
--
Bastien
Hi Grant,
Grant Rettke writes:
> This patch adds from-logo support to ox-koma-letter.el.
Applied, thanks!
--
Bastien
Hi Charles,
Charles Millar writes:
> I update org using the https:// access to the git repo.
Did you run ~$ make autoloads or ~$ make after you cloned?
You may need to compile a freshly cloned Org.
--
Bastien
Hi Charles,
Charles Millar writes:
> It is not clear to me - is it possible to write my own, fairly simple
> template with a few modifications that are a result of some recent
> changes or, for example, are elements such as those in
> tempo-define-template now required?
you would need to use `t
Hi Bernt,
Bernt Hansen writes:
> Hi Bastien! I have been away from this list for far too long -- hoping
> to correct that.
I hope too!
As Org keeps moving forward with rewritten and new functionalities,
it's essential to get tests and feedback from long-time power users.
--
Bastien
Hi Nicolas and Eric,
Nicolas Goaziou writes:
> I don't know, but I would suggest to use Yasnippet or some other
> specialized package for advanced templates like this one.
Thanks.
Eric Abrahamsen writes:
> I think more complicated templating has gone into org-tempo.el, which
> can be loaded
On Fri, Apr 27, 2018 at 11:30 PM, Grant Rettke wrote:
> Tested it manually with Elisp and also in buffer properties. There are
> four combinations (both in properties, both in Elisp, and then the two
> permutations).
Here is how it works, the same way as the other ones:
#+name:
org_gcr_2018-04-
Hi,
This patch adds from-logo support to ox-koma-letter.el.
Tested it manually with Elisp and also in buffer properties. There are
four combinations (both in properties, both in Elisp, and then the two
permutations).
It was a copy-and-paste job so I marked it as a tinychange even though
it was m
Hello,
On 04/26/2018 11:13 PM, Nick Dokos wrote:
Charles Millar writes:
Hi Nicholas,
On 04/26/2018 07:34 PM, Bastien wrote:
Hi Charles,
Charles Millar writes:
Attached --debug-init when starting -
is this with emacs -Q? If not, can you bisect you
Hi, again,
On 04/27/2018 07:09 PM, Bastien wrote:
Hi Charles,
Charles Millar writes:
Is this correct of has the format changed?
The format slightly changed, please check this option's docstring.
Also see ORG-NEWS here, which I just updated:
https://code.orgmode.org/bzg/org-mode/src/master
Hello,
Bernt Hansen writes:
> With the below org file tags handling behaves in a surprising way.
>
>
> * TODO Test Parent :PRODUCTION:MISC:
> ** TODO foo :BAR:
> ** keys to reproduce
>
>
> 1) At
Bastien writes:
> Hi Nicolas,
>
> Nicolas Goaziou writes:
>
>> In master branch, the format has changed.
>
> With the new template mechanism, can we have rich templates like the
> one Charles quotes?
>
> (add-to-list 'org-structure-template-alist '("r" "#+begin_src rec :data?
> :type \n#+end_
Hello,
András Simonyi writes:
> > [cite:author @Jones2018]
>
> > Again, maybe it's worth having some shortcuts here for the common cases,
> > but I think in general we want to try to avoid proliferation of basic
> > citation commands. So for that reason I think we should just stick with
Hello,
Bastien writes:
> With the new template mechanism, can we have rich templates like the
> one Charles quotes?
>
> (add-to-list 'org-structure-template-alist '("r" "#+begin_src rec :data?
> :type \n#+end_src" ""))
>
> allowing cursor positioning, etc?
>
> If yes, what pointer can we add
Hi Nicolas,
Nicolas Goaziou writes:
> In master branch, the format has changed.
With the new template mechanism, can we have rich templates like the
one Charles quotes?
(add-to-list 'org-structure-template-alist '("r" "#+begin_src rec :data?
:type \n#+end_src" ""))
allowing cursor position
Hi Charles,
Charles Millar writes:
> Is this correct of has the format changed?
The format slightly changed, please check this option's docstring.
Also see ORG-NEWS here, which I just updated:
https://code.orgmode.org/bzg/org-mode/src/master/etc/ORG-NEWS#L65
Let me know if you think this is
Hello,
Charles Millar writes:
> Hi,
>
> in my .emacs I have a couple of (add-to-list
> 'org-structure-template-alist) blocks of my own, for example
>
> #+begin_src
>
> (add-to-list 'org-structure-template-alist '("r" "#+begin_src rec :data?
> :type \n#+end_src" ""))
>
> #+end_src
>
> which I u
Hi,
in my .emacs I have a couple of (add-to-list
'org-structure-template-alist) blocks of my own, for example
#+begin_src
(add-to-list 'org-structure-template-alist '("r" "#+begin_src rec :data?
:type \n#+end_src" ""))
#+end_src
which I used until a few months ago.
Is this correct of has
Dear All,
thanks for your responses. I find John's list of the most important
capabilities of org-ref very useful and agree that in the long run we
should aim at providing all of these functionality for the new syntax as
well. One point where this might prove to be difficult is precisely the
set o
Bastien writes:
> Hi Bernt,
>
> glad to read you!
>
Hi Bastien! I have been away from this list for far too long -- hoping
to correct that.
> Bernt Hansen writes:
>
>> With the below org file tags handling behaves in a surprising way.
>
> Thanks for the report - just a quick check, do you hav
Hi Bernt,
glad to read you!
Bernt Hansen writes:
> With the below org file tags handling behaves in a surprising way.
Thanks for the report - just a quick check, do you have these
issues on the maint branch as well or just on master?
No problem if you cannot check, just thought you might have
Hi Nicolas,
Nicolas Goaziou writes:
> The initial report is wrong anyway, because "file:test test.hmtl" is not
> a valid link syntax, i.e., plain links cannot contain spaces. It should
> be:
>
> (org-open-link-from-string "[[file:test test.hmtl]]")
>
> IMO, there is nothing to fix in the fir
Hi Nicolas,
Nicolas Goaziou writes:
> I just sent an email to Emacs devels for inclusion in GNU ELPA.
Great. Let's advertize it in etc/ORG-NEWS when it's available.
--
Bastien
On Thu, Apr 26, 2018 at 7:34 PM, Bastien wrote:
> Hi Andrei,
>
> Andrei Beliankou writes:
>
> > I wonder if Org-mode has a convinient function to shift a timestamp with
> > a (weekly) repeating interval by that interval.
>
> Actually the same way `org-read-date' reads the time in the timestamp
>
Hello,
Joon Ro writes:
> Hi -
>
> With Org mode version 9.1.12 (9.1.12-elpaplus @
> ~/.emacs.d/elpa/org-plus-contrib-20180427/), whenever I do C-c ' on
> a #+INCLUDE: , I get user-error: No link found error. I thought at
> first the include was broken, but when I expor
Hello,
Bastien writes:
> Hi Joon,
>
> Joon Ro writes:
>
>> With current org version (Org mode version 9.1.8 (9.1.8-elpaplus @ c:
>> /Users/joon/.emacs.d/elpa/org-plus-contrib-20171228/)),
>> org-open-link-from-string does not work with a path string if it
>> includes a space. For example,
>>
>
Hi -
With Org mode version 9.1.12 (9.1.12-elpaplus @
~/.emacs.d/elpa/org-plus-contrib-20180427/), whenever I do C-c ' on a
#+INCLUDE: , I get user-error: No link found error. I thought at first the
include was broken, but when I export the file it correctly works, so the
visiting part i
Bastien writes:
> Gregor Zattler writes:
>
+#+begin_src emacs-lisp
+ * totally secret :crypt:
>
> PS: I guess this should have been "#+begin_src org" instead.
Actually, we settled on "#+begin_example" instead, because of
fontification issues.
Fixed. Thank you.
Hello,
Bastien writes:
> orgalist.el works great for me, thanks for writing it.
You're welcome.
> Just out of curiosity, did you consider make this a minor more from
> within org-list.el (e.g. `org-list-mode')?
I did. But I think features messing with other modes should go outside
Org core.
Am 27.04.2018 um 15:47 schrieb Bastien:
Hi Rainer,
Rainer Stengele writes:
I will copy the new function and modify it to fit my needs.
Thanks for this - please share your experience so that we can better
guide people in updating their code.
The only backward-incompatible change is that :ta
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
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
-
Gregor Zattler writes:
>>> +#+begin_src emacs-lisp
>>> + * totally secret :crypt:
PS: I guess this should have been "#+begin_src org" instead.
--
Bastien
Hi Rainer,
Rainer Stengele writes:
> I will copy the new function and modify it to fit my needs.
Thanks for this - please share your experience so that we can better
guide people in updating their code.
The only backward-incompatible change is that :tags is now :match
and :tags can now be nil
Hi Nicolas,
Nicolas Goaziou writes:
> Bastien writes:
>
>> Speaking of which... IIRC one of the reasons for not having
>>
>> (defconst org-version "9.1.12")
>>
>> in org.el was to having merge conflicts.
^^
sorry for the typo: s/having/avoid
> I don't remember this is
Hi Nicolas, org-mode users,
* Nicolas Goaziou [2018-04-27; 15:13]:
> Gregor Zattler writes:
>> +It's possible to use different keys for different headings by
>> +specifying the respective key as property CRYPTKEY, e.g.:
>
> I used =CRYPTKEY= instead of CRYPTKEY, as it is meant to be written in
>
Hello,
Gregor Zattler writes:
> Hi org-mode users and developers,
>
> Marco Wahl helped me with this: As always the solution is
> already there in org-mode. Attached you find a patch in
> order to document this feature.
Thank you.
> +It's possible to use different keys for different headings
Bastien writes:
> Speaking of which... IIRC one of the reasons for not having
>
> (defconst org-version "9.1.12")
>
> in org.el was to having merge conflicts.
I don't remember this issue.
> Does having "Version: 9.1.12" in org.el means we can switch back
> to having (defconst org-version "9.1
Hi Bastien,
I see that org-clocktable-write-default has been modified quite a bit.
I will copy the new function and modify it to fit my needs.
So please consider this case closed.
Thank you.
Regards, Rainer
Am 27.04.2018 um 14:05 schrieb Rainer Stengele:
Hi Bastien,
I am addressing you becau
Hi org-mode users and developers,
Marco Wahl helped me with this: As always the solution is
already there in org-mode. Attached you find a patch in
order to document this feature.
>From be08948c331118e2c66b858dc3133d3e44bfff69 Mon Sep 17 00:00:00 2001
From: Gregor Zattler
Date: Fri, 27 Apr 2018
Hi Bastien,
I am addressing you because I read that something changed with the agenda
clocktables.
Maybe related to that E-Mail:
Subject: Re: agenda clockreport -- include tags?
Date: Fri, 27 Apr 2018 01:34:50 +0200
After updating today I cannot get the agenda clocktable anymore.
I use my own
Hi Nicolas,
Nicolas Goaziou writes:
>> Org 9.1.12, a bugfix release, is out.
>
> However, you forgot to update "Version:" keyword in org.el prior to
> release, AFAICT.
D'oh! Thanks for spotting and reporting this, fixed now.
Speaking of which... IIRC one of the reasons for not having
(defco
Hello,
Bastien writes:
> Org 9.1.12, a bugfix release, is out.
Thank you.
However, you forgot to update "Version:" keyword in org.el prior to
release, AFAICT.
Regards,
--
Nicolas Goaziou
Hi,
Org 9.1.12, a bugfix release, is out.
Enjoy!
--
Bastien
Hi Rasmus,
Rasmus writes:
> I am waiting for 9.1.12.
It's been out since a few hours, I will mention it on the list
explicitely.
--
Bastien
Bastien writes:
> Hi Nicolas and all,
>
> Bastien writes:
>
>> I'm back from a few days off, I'll be able to make the 9.2 release
>> at the end of next week. I've released 9.1.10 in the meantime.
>
> I'm now reading past emails and checking things for 9.2.
>
> Maybe we will need to release 9.1.
On Friday, 27 Apr 2018 at 09:46, Bastien wrote:
[...]
> Does that make sense to you?
It does. Thanks.
In any case, getting rid of the * END bit will be nice. And I've
already moved to using drawers for a large number of my inline task use
cases, the ones that weren't really tasks!
--
Er
Hi Eric,
Eric S Fraga writes:
> Using *s seems confusing as they are intended for headlines. From a
> font lock point of view, I would have thought that ! at the start of the
> line would be easier as well.
I should have said that I don't like having a new syntax like this.
My whole point cou
On Tuesday, 27 Mar 2018 at 00:00, 42 147 wrote:
> Hello,
>
> I'm editing a large document, mostly text, that is intended for a
> website -- thus html is interspersed throughout, though not enough to
> justify editing the document as a dedicated .html file.
[...]
> Is there a way to switch back to
On Friday, 27 Apr 2018 at 01:34, Bastien wrote:
[...]
> I'd favor a solution where inline tasks are really simple:
>
> 0. Prevent cycling for tasks with a high number of stars
>("high" being defined by the user as an option).
>
> 1. Allow TODO keywords, priority, tags, SCHEDULED and DEADLINE
50 matches
Mail list logo
