Puneeth Chaganti puncha...@gmail.com writes:
Yes, that is correct. I have a few code blocks that work and don't
work, in the ECM, if at all you want to look at them.
It should now be fixed. Thank you for reporting it.
Regards,
Hi Nicolas,
It looks the commit 8d8ad983823c63b13fd6b471ce9db8c2f95e3808 broke
generation of org sparse trees, when searching with properties that
are not all uppercase. The fix seems to be just removing the
conversion of key to upcase in `org-entry-properties'. Since the
comparison with
Hello,
Puneeth Chaganti puncha...@gmail.com writes:
It looks the commit 8d8ad983823c63b13fd6b471ce9db8c2f95e3808 broke
generation of org sparse trees, when searching with properties that
are not all uppercase.
Could you provide an ECM?
The fix seems to be just removing the conversion of
On Sat, Dec 6, 2014 at 5:01 AM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
Hello,
Puneeth Chaganti puncha...@gmail.com writes:
It looks the commit 8d8ad983823c63b13fd6b471ce9db8c2f95e3808 broke
generation of org sparse trees, when searching with properties that
are not all uppercase.
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
The above function is perfect for her task! No diff at all [1] when
applied on all my files from org-agenda-files (~ 45).
I updated ORG-NEWS then. Thanks for the feedback.
Regards,
Hello Nicolas,
Nicolas Goaziou wrote:
Sebastien Vauban writes:
** Sectionnement
Exemple de section avec un titre court pour LaTeX :
#+begin_src org
,* Ceci est un titre de section assez long
:PROPERTIES:
:ALT_TITLE: Ceci est un titre court
:END:
#+end_src
Upon execution of the
Hello Nicoalas,
Nicolas Goaziou wrote:
Sebastien Vauban writes:
I've done that but, now, it does not support anymore the structure I had
in all my Org files:
** TODO Show typical Org entry
SCHEDULED: 2014-11-08 Sat
:LOGBOOK:
CLOCK: [2014-11-11 Tue 12:35]--[2014-11-11 Tue
Nicolas,
Sebastien Vauban wrote:
Sebastien Vauban wrote:
After heavy testing (on all my Org files, I mean) of the function
`org-repair-property-drawers', it works perfectly except for the
following corner-case (when there are Org properties in quote
blocks).
I did not retest (yet) the same
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
** Sectionnement
Exemple de section avec un titre court pour LaTeX :
#+begin_src org
,* Ceci est un titre de section assez long
:PROPERTIES:
:ALT_TITLE: Ceci est un titre court
:END:
#+end_src
Upon
Hello,
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
After heavy testing (on all my Org files, I mean) of the above function,
it works perfectly except for the following corner-case (when there are
Org properties in quote blocks):
* Reference
Example of
Hello Nicolas,
Nicolas Goaziou wrote:
Sebastien Vauban writes:
After heavy testing (on all my Org files, I mean) of the above function,
it works perfectly except for the following corner-case [...].
Thanks for your feedback. Would the following updated function solve the
problem?
Hello,
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
I've done that but, now, it does not support anymore the structure I had
in all my Org files:
** TODO Show typical Org entry
SCHEDULED: 2014-11-08 Sat
:LOGBOOK:
CLOCK: [2014-11-11 Tue
Hello Nicolas,
Nicolas Goaziou wrote:
Sebastien Vauban writes:
It does work perfectly on the meta-stuff (SCHEDULED, DEADLINE,
etc.). Though, it moves as well the body text -- while I'm not
using `org-indent-mode'.
* New section
** The SCHED will be moved
SCHEDULED: 2011-08-18 Thu
Hello Nicolas,
Nicolas Goaziou wrote:
As discussed previously, I would like to modify property drawers
syntax. [...]
However, it will break some Org documents. In particular, TODO-states
changes are usually logged before any drawer, including properties
drawers. The following function
Nicolas,
Sebastien Vauban wrote:
After heavy testing (on all my Org files, I mean) of the function
`org-repair-property-drawers', it works perfectly except for the
following corner-case (when there are Org properties in quote
blocks).
PS- I did not retest (yet) the same thing in
Hello Nicolas,
Nicolas Goaziou wrote:
Sebastien Vauban writes:
One question, now that this syntax is stabilized, can the following
long-standing bug be fixed: sometimes the SCHEDULED line (or
DEADLINE, or ...) is moved synchronously with the heading when
promoting/demoting, sometimes not.
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
It does work perfectly on the meta-stuff (SCHEDULED, DEADLINE,
etc.). Though, it moves as well the body text -- while I'm not using
`org-indent-mode'.
* New section
* The SCHED will be moved
SCHEDULED:
Nicolas Goaziou wrote:
Sebastien Vauban writes:
It does work perfectly on the meta-stuff (SCHEDULED, DEADLINE,
etc.). Though, it moves as well the body text -- while I'm not using
`org-indent-mode'.
* New section
* The SCHED will be moved
SCHEDULED: 2011-08-18 Thu
** This one won't
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
Isn't that somehow duplicate with `org-indent-mode' (which I don't
enable either)?
`org-indent-mode' sets `org-adapt-indentation' to nil _and_ indents
virtually (no modification to the document) body as if
Nicolas Goaziou wrote:
Sebastien Vauban writes:
Isn't that somehow duplicate with `org-indent-mode' (which I don't
enable either)?
`org-indent-mode' sets `org-adapt-indentation' to nil _and_ indents
virtually (no modification to the document) body as if
`org-adapt-indentation' wasn't nil.
Hello,
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
One question, now that this syntax is stabilized, can the following
long-standing bug be fixed: sometimes the SCHEDULED line (or DEADLINE,
or ...) is moved synchronously with the heading when
Nicolas Goaziou wrote:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
As discussed previously, I would like to modify property drawers syntax.
The change is simple: they must be located right after a headline and
its planning line, if any.
[...]
I pushed a new branch, top-properties in
John Hendy jw.he...@gmail.com writes:
I use this, or at least things like this. For example:
* task
:PROPERTIES:
:start:2014-11-03-08:00
:task_id: task_d
:depends: task_a task_b task_c
:duration: 30min
:END:
Not multi-line, but currently I can feed any
Hello,
Christian Egli christian.e...@sbs.ch writes:
This usage is perfectly fine and will continue to work. There are some
very obscure attributes that taskjuggler (and the exporter) support,
such as note and journalentry. These can span multiple lines. They can
be used to add notes or more
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Christian Egli christian.e...@sbs.ch writes:
I see that it is too late now, but let me still note that the
taskjuggler exporter is quite liberal in what attribute values it allows
for exporting. I've never used it and I haven't ever
Christian Egli christian.e...@sbs.ch writes:
AFAIK the org-mode taskjuggler exporter was previously able to handle
this if given the following headline:
* task
:PROPERTIES:
:Effort: 1w
:depends: software
:allocate: test dev2
:note: Hopefully most bugs will be found
Hello,
Christian Egli christian.e...@sbs.ch writes:
I see that it is too late now, but let me still note that the
taskjuggler exporter is quite liberal in what attribute values it allows
for exporting. I've never used it and I haven't ever seen anyone using
it, but in theory you could give a
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
As discussed previously, I would like to modify property drawers syntax.
The change is simple: they must be located right after a headline and
its planning line, if any.
Feedback welcome.
If
On Fri, Oct 31, 2014 at 8:10 AM, Christian Egli christian.e...@sbs.ch wrote:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
As discussed previously, I would like to modify property drawers syntax.
The change is simple: they must be located right
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
As discussed previously, I would like to modify property drawers syntax.
The change is simple: they must be located right after a headline and
its planning line, if any.
[...]
I pushed a new branch, top-properties in the repository for code
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
As discussed previously, I would like to modify property drawers syntax.
The change is simple: they must be located right after a headline and
its planning line, if any.
[...]
I pushed a new branch, top-properties in the repository for code
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
As discussed previously, I would like to modify property drawers syntax.
I think the syntax change looks great (based on the proposal)!
Thanks a bunch!
—Rasmus
--
Dobbelt-A
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Hi
I am not using org that much for schedulig, todo items, and other
similar topics, but mainly for literate programming, so I will comment
From that perspective.
As discussed previously, I would like to modify property drawers syntax.
Hello,
Eric Abrahamsen e...@ericabrahamsen.net writes:
Is there any chance this has messed up file-local #+TODO: keyword
definitions?
The changes mess with todo keywords, tags, properties, initialization
(local keywords), clock and logging. However, the modifications are
internal and no
Hello,
Rainer M Krug rai...@krugs.de writes:
Moreover, node properties' keys can only contain non-whitespace
characters and cannot end with a plus sign (which is used for
accumulation).
This is problematic for me, as I am using it extensively in the case
of :header-args.
I set file
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Eric Abrahamsen e...@ericabrahamsen.net writes:
Is there any chance this has messed up file-local #+TODO: keyword
definitions?
The changes mess with todo keywords, tags, properties, initialization
(local keywords), clock and logging.
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Rainer M Krug rai...@krugs.de writes:
Moreover, node properties' keys can only contain non-whitespace
characters and cannot end with a plus sign (which is used for
accumulation).
This is problematic for me, as I am using it
Hi Nicolas
My questions were misleading, I'm sorry. I should not have asked about
valid and not have added a property drawer. Rather I wanted to know
when regarding only the agenda whether I can still postpone to make
these examples valid:
* Yearly meeting
2013-08-11 Sun
Hello,
Michael Brand michael.ch.br...@gmail.com writes:
My questions were misleading, I'm sorry. I should not have asked about
valid and not have added a property drawer.
Actually valid/invalid is a bit strong. There is no such thing as
a syntax error in Org. However, Org may differ from your
Hi Nicolas,
My only 'concern' is that it looks awkward or at least unfamiliar when the
property drawer is closed (which it is always in my documents).
I guess than it would change from
*** Call XXX
:PROPERTIES:...
2014-10-16 Thu 13:00-14:00
to
*** Call XXX
2014-10-16
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
My only 'concern' is that it looks awkward or at least unfamiliar when the
property drawer is closed (which it is always in my documents).
I guess than it would change from
*** Call XXX
:PROPERTIES:...
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
As discussed previously, I would like to modify property drawers syntax.
The change is simple: they must be located right after a headline and
its planning line, if any. Therefore the following cases are valid
* Headline
Hi Nicolas
On Tue, Oct 14, 2014 at 4:42 PM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
As discussed previously, I would like to modify property drawers syntax.
The change is simple: they must be located right after a headline and
its planning line, if any. Therefore the following cases are
Hello,
Eric Abrahamsen e...@ericabrahamsen.net writes:
Sounds like fun! Here's maybe a bug. In this test case:
* Here's something
** Second level
:PROPERTIES:
:ID: 06b778b5-72a5-45b5-aea6-2d0fef0fd24b
:END:
Good catch. Fixed, thank you.
Regards,
--
Nicolas Goaziou
Hello,
Michael Brand michael.ch.br...@gmail.com writes:
What about legacy multi line plain timestamp and planning info:
* Yearly meeting
2013-09-22 Sun
2014-10-19 Sun
SCHEDULED: 2015-01-01 Thu Add next plain timestamp.
:PROPERTIES:
:KEY: value
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
As discussed previously, I would like to modify property drawers syntax.
The change is simple: they must be located right after a headline and
its planning line, if any. Therefore the following cases are valid
Is there any chance this
46 matches
Mail list logo
