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.
From dfe5b8df8d7ec6db03336594d120ee5565205ac6 Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Tue, 14 Jan 2025 17:39:38 +0700
Subject: [PATCH] testing/lisp/test-ox-man.el: Add regression tests for ox-man
* testing/lisp/test-ox-man.el (ox-man/bold, ox-man/code,
ox-man/italic-underlined
`org-babel-import-elisp-from-file' -- looks like only some languages set
it to some fixed value.
Matt writes:
> On Tue, 12 Mar 2024 10:27:46 +0100 Ilya Konovalov wrote ---
> >
> > After some usage I found that this exact patch breaks
> > `org-babel-import-
After some usage I found that this exact patch breaks
`org-babel-import-elisp-from-file's own separator detection. It looks
like it's better to leave it as `nil' unless specified.
Ilya Konovalov writes:
> On current master using ":sep" header argument does not wo
On current master using ":sep" header argument does not work as
expected and records are always split on whitespaces. For example:
#+begin_src sh :sep "\t"
echo hello world
echo test
#+end_src
#+RESULTS:
| hello | world |
| test | |
It looks like the issue is in the org-babel-sh-evalu
Hi, just wanted the code to be more elisp style guide compliant, so here's
a patch that adds spaces before opening parentheses.
>From 0d9b7ce6d5e83d7758566dab6a17642fdf4b9b73 Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Mon, 12 Feb 2024 18:33:29 +0600
Subject: [PATCH] Fix fo
-find-duplicates' is what you intended?
Yeah, now it works as it should. Thanks. I've made some minor changes
I've described in the attached patch.
>From 8bcd02bac32d3a4442814c2a42b097d642964372 Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Fri, 9 Feb 2024 17:32:58 +0600
S
Ihor Radchenko writes:
> What about the attached amendment?
> It should simplify things significantly.
Sorry, in my previous patch the test that checks the detector itself was not
even run in 'make test' because of incorrect test prefix.
Your patch does not work as you expect. Could you please
Ihor Radchenko writes:
> It has been a while since the last update in this thread.
> Ilya, do you need any help with the patch?
Hi, here is the updated patch.
>From 2385ba08a89f2966a6d71f92e8693e7def33e3fe Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Mon, 22 Jan 2024 01:33
Hi.
Is there a custom variable in org-agenda that allows to set a specific
face (or just foreground/background) for items with specific
property/tag/category?
Ilya Chernyshov writes:
> Sure, here it is. In the patch, I added a new file
> (testing/lisp/test-deduplicator.el) with a test that checks for
> duplicate forms (not just should, should-not, should-error macros) in
> all test files.
It also makes sense to add a test that searches fo
of tests to change before merging. I'll handle them and
submit a new patch if you have no questions about the code.
>From 3b38450f7de8bd168d8795728454d9f4db720843 Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Tue, 5 Sep 2023 22:40:59 +0700
Subject: [PATCH] testing: Add testing/lisp/test
Hi.
Is there anything I can do with my Org config so that every time I
change the TODO state of my habit (example below), Org logs inactive
timestamp from SCHEDULED property before TODO state change?
For example, I have this habit, which I have been forgetting to mark as
DONE/MISSED/WHATEVER fo
Hi!
I applied my ert test deduplicator on org tests and found some useless tests
which you can see in the patch.
>From 32d83fc5b2ad076dcd8681434a46b4117ac23858 Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Sun, 17 Sep 2023 02:33:51 +0700
Subject: [PATCH] testing: Delete useless
"Dr. Arne Babenhauserheide" writes:
Hi
> I started using this, and it’s great! Thank you!
Nice to hear!
> I also found an edge case: I have a deadline set to 23:59, and that
> deadline is only visible in the timeblocks when I only have that task in
> and switch to hiding all hours before the t
Ihor Radchenko writes:
> I have re-introduced the new tests in place of the removed ones,
> according to my and Max's findings. On top of the patch.
>
> Applied, onto main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=fe85d61a9
> https://git.savannah.gnu.org/cgit/emacs/org-mo
"Dr. Arne Babenhauserheide" writes:
> Wow, that looks nice!
Thank you!
>
> If you want to provide a print-export (i.e. for hanging on the door of a
> lecture room), you could see whether it’s easy to translate it to a
> latex time table like this:
> https://hg.sr.ht/~arnebab/stundenplan-wochenp
[Changed the subject]
Ilya Chernyshov writes:
> Hi! I wrote a package that provides interactive day view for orgmode
> tasks. With this package you can visually understand your day schedule
> and quickly reschedule your tasks and events. Essentially, this is what
> modern calendars provide, althoug
"Fraga, Eric" writes:
> I have tried again and now it installs. Thank you. I do get many
> errors when trying to navigate to different dates and/or scroll up/down
> in the current date being viewed.
>
> For instance, I get the following in trying org-timeblock a second time
> in the current Ema
"Fraga, Eric" writes:
> Hi,
>
> I'm late to this and I don't have the full thread on my system so
> apologies if this has been asked before.
>
> When I try
>
> M-x package-vc-install RET https://github.com/ichernyshovvv/org-timeblock/
>
> according to the instructions given at the gitlab reposito
"Fraga, Eric" writes:
> Hi,
>
> I'm late to this and I don't have the full thread on my system so
> apologies if this has been asked before.
>
> When I try
>
> M-x package-vc-install RET https://github.com/ichernyshovvv/org-timeblock/
>
> according to the instructions given at the gitlab reposito
Ihor Radchenko writes:
> Thanks for sharing!
>
> As I mentioned in Matrix chat, it would be nice if you could integrate
> the svg image display into Org agenda as minor mode, displaying the
> interactive svg in place of the time grid. That would be a welcome
> addition to Org core.
It's a great
Hi! I wrote a package that provides interactive day view for orgmode
tasks. With this package you can visually understand your day schedule
and quickly reschedule your tasks and events. Essentially, this is what
modern calendars provide, although my package currently only provides
day view.
The
cked the result manually and deleted some of them.
Here is the patch I wrote:
>From 21ba128bd648c6737ed088abdd2a1824cfe01759 Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Thu, 13 Jul 2023 01:36:33 +0700
Subject: [PATCH] testing: Delete duplicate tests
* testing/lisp/test-ol.el (test-
-element-timestamp-parser' setting nil for end part if :type is
`active'/`inactive'. That's not true. The actual behavior is that it
sets end date/time to the same values as start date/time even if it's
`active'/`inactive'. So here is the patch:
>From 823e7f3
'
types.
>From aa21a84fa38324f455cb17ac32e656e1242c2135 Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Sat, 18 Feb 2023 14:55:39 +0700
Subject: [PATCH] lisp/org-element.el: Add new timestamp property :range-type
* lisp/org-element (org-element-timestamp-interpreter): Preserve old
behavior when :ran
inside timestamp, random breakages may happen. Please, rewrite.
Fixed.
> Interpreting timestamps with :time-range nil and
> :day-end/:year-end/:month-end non-nil as timerange is a breaking change.
> Let's avoid it.
Timestamp objects (ranges) with :range-type nil are now interpreted
erange.
>
> Changing :type values will not be backwards-compatible.
>
From d95418110897bdde85a74734bb5b5fa7a3c77b92 Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Sat, 18 Feb 2023 14:55:39 +0700
Subject: [PATCH] New timestamp property :range-type
* lisp/org-element (org-el
You suggest to split timestamp types active/inactive-range to
active/inactive-timerange, active/inactive-daterange?
On February 20, 2023 6:07:19 PM GMT+07:00, Ihor Radchenko
wrote:
>Ilya Chernyshov writes:
>
>> So, an option is needed that controls whether to return a
>>
I forgot to attach the patch :)
>From b47324bc804e64e6cef482ba4897a457252e803a Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Sat, 18 Feb 2023 14:55:39 +0700
Subject: [PATCH] org-element-timestamp-interpreter: Return daterange anyway,
if DATERANGE is non-nil
* lisp/org-element (
equal).
I wrote a patch that handles this problem, could you please review
the
code and give some advice to improve it?
--
Best,
Ilya
Ihor Radchenko writes:
Updating the manual will make more sense. Would you mind writing
a patch?
Of course.
>From da84673301de7e9453cb359536235d8ce56399f1 Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Fri, 17 Feb 2023 01:23:27 +0700
Subject: [PATCH] org-manual.org: Update timest
9 Thu 7:30-16:40>"
(org-element-property :type (org-element-context)
So, we either should change the behavior of
(org-element-timestamp-parser) or update the definitions of
timestamp
and timestamp range in org-manual. What do you think?
--
Best,
Ilya
Ihor Radchenko writes:
Ilya Chernyshov writes:
(defun org-datetree--find-create
@@ -169,18 +167,19 @@ component. If INSERT is non-nil and
there is no match then it is
inserted into the buffer."
(when (or month day)
(org-narrow-to-subtree))
- (let ((re (format regex-tem
Ihor Radchenko writes:
Ilya Chernyshov writes:
(defun org-datetree--find-create
@@ -169,18 +167,19 @@ component. If INSERT is non-nil and
there is no match then it is
inserted into the buffer."
(when (or month day)
(org-narrow-to-subtree))
- (let ((re (format regex-tem
Thanks!
Instead of manually constructing the regexp, you can use
`org-complex-heading-regexp-format'.
Thanks for the tip. Applied changes in the new patch.
>From 8a32385ae2ccbbc0caa35eda9a8184c165e3afcd Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Thu, 15 Dec 2022 02:08:
annoying. This patch fixes it.
From 4d3194adf417ae5bad78c35a783ebca7974b8167 Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Thu, 15 Dec 2022 02:08:15 +0600
Subject: [PATCH] lisp/org-datetree.el: Allow datetrees with TODO, priority,
tags
* org-datetree.el (org-datetree--find-create-group,
org
// yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
>
From 74cc1a6b879c1b856fdc9205b4e042582f658f6c Mon Se
"as a GNU package, we're not allowed to mention proprietary software"
-- how is that consistent with GNU prominently distributing Emacs for
Windows from its own website? I think this shows that the guideline
is not absolute. And it's specifically phrased as a guideline
("should"), not as a requir
an 2, 2018 at 2:20 PM, Nicolas Goaziou wrote:
> Hello,
>
> ilya shlyakhter writes:
>
>> Neither is iOS or MATLAB, and yet the Org manual mentions both.
>
> We have good reasons for that. The former is because MobileOrg, which
> uses "org-mobile.el", prov
>This may be because the app is not open source?
Neither is iOS or MATLAB, and yet the Org manual mentions both.
On Tue, Jan 2, 2018 at 12:39 PM, Eric S Fraga wrote:
> On Tuesday, 2 Jan 2018 at 12:32, Ilya Shlyakhter wrote:
>> The org features page at https://orgmode.org/features.h
The org features page at https://orgmode.org/features.html, and the
Org manual, mention MobileOrg, but not the newer BeOrg app
( http://beorgapp.com/ ). Maybe add a reference to it?
The org-timeline documentation at
http://orgmode.org/manual/Timeline.html
seems no longer correct?
(also, I think it's unfortunate that the timeline agenda mode was
removed -- I found it quite useful.)
At http://orgmode.org/community.html the links to browse or search
emacs-orgmode through Gmane are broken. Maybe, remove them until
Gmane is fixed? Is there another service similar to Gmane?
The link "Browse org-mode mailing list through Gmane" at
http://orgmode.org/community.html
seems broken.
Thanks, Rasmus!
I upgrade org-mode to 8.3 and this is solve the problem.
13.05.2016, 14:49, "Rasmus" :
> Hi,
>
> Ilya Filippov writes:
>
>> I try to include subsection from one org-file to another
>> (http://orgmode.org/manual/Include-files.html) with using C
" - also works.
May be I need add something to .emacs?
- - - - - - - - - - -
Ilya
When loading any org file, I'm getting "File mode specification error:
(error "before first heading")" . This happens starting with
release_8.3.3 ; with release_8.3.2 , no error. Emacs version is
GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.18.6) of
2015-03-26 on scs-build-rhel6 .
r a general Emacs issue but looks like
Org-mode is fine :)
Thanks for your help!
Regards, Ilya.
m new to org-mode internals
so I can't decide for myself how to fix that.
Looking forward to hear your feedback.
Regards, Ilya.
ntent and couldn't be set! So I believe this code is
buggy anyway. It's possible that this bug is not triggered in some (most)
configurations, because the code is not executed, but this doesn't make this
code correct anyway.
Unfortunately I'm not an expert in org-mode internals and don't have any
idea how to fix that. Looking forward for your help here.
Regards, Ilya.
e.cmu.edu
On Thu, Dec 3, 2015 at 6:08 AM, Ilya <filip83...@yandex.ru> wrote:I export my Org-Mode notes with internal links to LaTeX and I want it to
look like this ''Section 1.1 [Section name], page 99'' (Like in the Org
Manual). I use this construction:
#+BEGIN_EXAMPLE
*
ttp://emacs.stackexchange.com/questions/18547/org-mode-latex-export-with-section-number-name-and-page-in-internal-links),
I was advised to use a Fancyref, but I have no idea how I may use it with
Org-Mode syntax.
- - - - - - - - - - -
Ilya Filippov
Yugra State University (Khanty-Mansiysk)
tsburgh, PA 15213412-268-7803@johnkitchinhttp://kitchingroup.cheme.cmu.edu On Thu, Dec 3, 2015 at 6:08 AM, Ilya <filip83...@yandex.ru> wrote:I export my Org-Mode notes with internal links to LaTeX and I want it tolook like this ''Section 1.1 [Section name], page 99'' (Like
I export my Org-Mode notes with internal links to LaTeX and I want it to
look like this ''Section 1.1 [Section name], page 99'' (Like in the Org
Manual). I use this construction:
#+BEGIN_EXAMPLE
* Chapter 1
** Section 1.1
:PROPERTIES:
:CUSTOM_ID: section-1
:END:
* Chapter 2
** Sect
torys.ander...@gmail.com (Tory S. Anderson) writes:
> We often read online articles with headings and sometimes
> subheadings. They may also include bold, italic, and hyperlinks, all
> of which are supported by Org. Is there any way to preserve this
> formatting if I copy-paste into org/emacs, the
Bastien writes:
> We should absolutely avoid advice in code.
Fully agree. (I was thinking of using an flet-like construct to
temporarily rebind functions for the duration of calls, rather than
permanent advice -- see elu-flet in
https://github.com/notestaff/elu/blob/master/elu.el -- but, still a
On 4/10/2014 3:19 PM, Nicolas Goaziou wrote:
I don't see why you would need the "full power of Org-mode" (whatever
that means) in mere comments.
There are actually many uses, especially if it becomes possible to treat
language elements (functions, classes etc) as outline elements
(cf.
https:/
On 4/19/2014 8:57 AM, Bastien wrote:
Hi Thorsten,
Thorsten Jolitz writes:
In summary, its about:
1. generalize the regexp constants and vars (allow for comment-syntax,
when org-minor-mode)
2. deal with hardcoded regexp-snippets in functions (my proposoal:
replace "^" with org-BOL, "
On 3/19/2014 9:19 PM, Ilya Shlyakhter wrote:
Another option is to use Thorsten Jolitz's excellent outshine mode
( http://orgmode.org/worg/org-tutorials/org-outside-org.html ).
I've written a small extension that allows it to fold language elements:
http://www.broadinstitute.org/~ily
g/org-tutorials/org-outside-org.html ).
I've written a small extension that allows it to fold language elements:
http://www.broadinstitute.org/~ilya/outshine-python.el
;t really in a
subtree).
Manual says that #+PROPERTY lines specify "properties that can be
inherited by any entry in a file"; more precise would be that they
specify "property settings inherited by every entry"? Likewise for
the variable org-global-properties.
On Tue, Mar 18,
gic of the code, but can you help me
see where I'm wrong in the explanation of the patch?
Thanks,
ilya
ests.
>>>
>>> Sorry, I don't buy this.
>>
>> I'm not selling anything.
>
> What I meant is this: broken tests are not a sufficient reason to
> revert a commit. You need to show the commit is wrong and the tests
> are not outdated.
>
> In thi
On 3/12/14 2:14 PM, Joost Helberg wrote:
back in the time when me and my friend created and sold the Snow Linux
Distribution, we donated all excess money to the FSF.
If people wanted to give to the FSF, they would have done it directly.
I've donated to Org in the past not to defray expenses but
>From bea0daf422e9ab8f27addb412aa03456c89d5844 Mon Sep 17 00:00:00 2001
From: Ilya Shlyakhter
Date: Fri, 7 Mar 2014 01:09:13 -0500
Subject: [PATCH] Properties: Fix property-getting with inheritance
* lisp/org.el (org-entry-get-with-inheritance): Temporarily clear
org-file-properties, org-glo
sections of code; in others, the extra lines (though shortened) actually
help. I'll use begin_src/end_src for the former and BEGIN_SRC/END_SRC
for the latter, and have your prettier-org-code-blocks fontifier match
just the lowercase version.
Thanks a lot,
ilya
helps to be able to see many things at
once, and having many extra lines (even mostly-blank ones) makes that
difficult.
ilya
not reduce the number of lines used, so a short list of
declarations interspersed with comments quickly ends up taking a lot of
vertical space. When coding it helps to be able to see many things at
once, and having many extra lines (even mostly-blank ones) makes that
difficult.
ilya
On 3/6/14 2:00 PM, Oleh wrote:
I was just committing a single line change to an org-mode table into
git, and the diff isn't good at all: the whole table appears to have
changed. Well, not really - just a few spaces were added on each table
line because the single new line caused a need to re-ali
invariants?
(Context: trying to use Org for literate programming in C++;
interested in others' experience in this area).
Thanks,
Ilya
0001-When-computing-clock-table-remove-arbitrary-limit-on.patch
Description: Binary data
Hi,
I have prepared patch which fixes incorrect replacement with org-mouse
popup function for checkbox lists: "All Set" and "All Clear". Please, check
it. See attachment.
--
*Илья Зонов* (*Ilya Zonov*) aka *puzan*
Нижний Новгород, Россия (Nizhny Novgorod, Russia)
0001-org
Hi Bastien,
On Fri, Sep 21, 2012 at 12:51 PM, Bastien wrote:
>
> Would be nice. Let us know how it goes,
>
>
I'll be on vacation next week in Spain. So I will look in this only in
October. I'll write when I have some results.
--
*Илья Зонов* (*Ilya Zonov*) aka *puzan*
Н
s and only ten tasks. So I want to clean up logs
which are older one or two month for example.
If there are no cleaning logs feature in org-mode, I will try to write it.
Thanks.
--
*Илья Зонов* (*Ilya Zonov*) aka *puzan*
Нижний Новгород, Россия (Nizhny Novgorod, Russia)
On 8/2/2012 11:10 AM, Bastien wrote:
If the whole point is to make some properties less visible,
why not a solution based on fontification?
We could have a user-defined regexp to highlight (or "dim")
certain properties.
That would still leave the :PROPERTIES: line visible, which is problem
for
On 8/6/2012 2:16 PM, Allen S. Rout wrote:
One common use would be to store the creation & last-modification dates
of each entry. I've tried various ways of doing it and they all were
too obtrusive to use on _every_ entry. Time-stamping of all entries
would be extremely useful, just as time-sta
On Mon, Aug 6, 2012 at 8:12 AM, Jonathan Leech-Pepin
wrote:
> The issue I can see with completely hiding :PROPERTIES: line is
> that you would then run the risk of adding text at the wrong
> location (between the headline and the drawer for example). At
> the moment when the drawer is folded you
On Sun, Aug 5, 2012 at 10:46 PM, Torsten Wagner
wrote:
> I can see the point that the property drawer header can be annoying
> too. Actually, when I used orgmobile for the first time I was not too
> happy to see all this property drawers suddenly appearing in my files.
> Alternatively to a new ki
On Sun, Aug 5, 2012 at 6:20 PM, Nicolas Goaziou wrote:
>> What about a HIDDEN_PROPERTIES drawer that, when folded, folds
>> completely (so that its title line is hidden too), and have a key to
>> reveal such drawers (the way M-tab opens archived entries)?
>
> This is begging for problems. At some
On 8/5/2012 5:16 AM, Bastien wrote:
Hi Ilya,
Ilya Shlyakhter writes:
But I don't want to see the timestamps during normal Org usage.
What do you think of "hiding" them by having a new face for properties
matching a custom regexp? This has the advantage of letting the user
On 7/31/2012 9:23 AM, Robert Horn wrote:
I agree. The real use needs more clarification. Things like ID are
already well hidden as :PROPERTIES: until the user explicitly opens the
drawer for viewing. I don't understand the need to hide those further, so
a better explanation of why is needed.
dear org-moders,
is it possible to syntax-highlight inline LaTeX fragments,
such as $V$ or \cite{smith2012generating} ?
I know you can highlight LaTeX code blocks, but I'm looking specifically
for highlighting of inline fragments.
thanks for help,
ilya
.
thanks,
ilya
Added some details for how to run the test suite in batch mode.
>From 2cf6b6f529748a2a39927ccfdfa583d7f00cc9df Mon Sep 17 00:00:00 2001
From: Ilya Shlyakhter
Date: Fri, 30 Mar 2012 22:11:22 -0400
Subject: [PATCH] Testing: Corrected the command to run batch tests given in
README
testing/REA
tstart
and :tend as decribed in the manual. Is there a better explanation
somewhere?
thanks,
ilya
>From d19778b3fc624e14237d69cc76a4aa9cb8450697 Mon Sep 17 00:00:00 2001
From: Ilya Shlyakhter
Date: Fri, 30 Mar 2012 21:19:12 -0400
Subject: [PATCH] Time specifications: Allow specifying relative t
Patch for a bug that left blank lines in property drawer after
org-delete-property-globally.
>From 41cbd6302e5a58ed09ec80436237c3c2f4ad8514 Mon Sep 17 00:00:00 2001
From: Ilya Shlyakhter
Date: Thu, 29 Mar 2012 22:31:14 -0400
Subject: [PATCH] Deleting properties: Fixed bug that left blank li
d post the
final working version of your patch for this.
thanks,
ilya
file, so it stands on its own and is independent of Emacs/Org.
Thanks for help,
ilya
#+Property: comments both
#+Property: tangle example.el
This is a the top of an Org-mode file.
* This is some high-level documentation
This file does X and Y.
*** Section A
High-level documentation f
and description, as goes
at the top of an elisp file, and which can be broken into
sections/subsections/etc -- not just local documentation before a given
code block).
Is that possible?
thanks,
ilya
On Mon, Mar 26, 2012 at 7:22 AM, Eric Schulte wrote:
> Yes this is possible, see the
A blank headline (e.g. with just a TODO keyword) caused a crash when
building colview. Patch attached.
>From 6bb1413821a7cbf94b3abbfc6e985e187dd8d6d9 Mon Sep 17 00:00:00 2001
From: Ilya Shlyakhter
Date: Sat, 24 Mar 2012 12:25:59 -0400
Subject: [PATCH] Colview bugfix: A headline with jus
x27;d check with the list first.
ilya
How should case-sensitivity work in Org? The documentation doesn't
specify. From past messages, it looks like tags and todo keywords
are defined to be case-sensitive. What about priorities, categories,
user-defined properties, regexp matching of entries, following of
links-to-headlines? Other
erate-programming form in
Org mode, but be able to export it into an executable form that's
independent of Org but still has all the information (not just the
text immediately before each code block).
Thanks for help,
ilya
r to org-scan-tags.
>From 3feb2edd3a705811824348546f4edad2f595f8bb Mon Sep 17 00:00:00 2001
From: Ilya Shlyakhter
Date: Wed, 21 Mar 2012 19:49:07 -0400
Subject: [PATCH] Tags/properties matcher: Fixed issues with todo-only matches
lisp/org.el (org-scan-tags): Require todo-only argument, and
67cf Mon Sep 17 00:00:00 2001
From: Ilya Shlyakhter
Date: Fri, 16 Mar 2012 17:33:36 -0400
Subject: [PATCH 2/2] Documentation: Clarified current role of ITEM special
property
doc/org.texi (section on Special Properties) Clarified that ITEM refers
to the headline of the entry not the whole en
Re-sending the patch as a correct attachment type.
One of the warnings indicated an actual (small) bug.
>From d0579b6e104b82ec7d3255086384ff8dee0d4e0e Mon Sep 17 00:00:00 2001
From: Ilya Shlyakhter
Date: Fri, 16 Mar 2012 01:52:03 -0400
Subject: [PATCH] Fixed compiler warnings, including
On 3/16/2012 2:10 AM, Nick Dokos wrote:
One more thing that you'll need to do is put your patches in attachments
of a type that will allow patchwork to snag the patch:
And here is the org-clock.el patch again.
>From 4f7f91ae62d425f7a89738b28006b1743a6bea4d Mon Sep 17 00:00:00 2001
Fr
On 3/16/2012 2:10 AM, Nick Dokos wrote:
> One more thing that you'll need to do is put your patches in attachments
> of a type that will allow patchwork to snag the patch:
Thanks, I was wondering why they're not showing up.
Here is another try (attached) for the org.el pa
1 - 100 of 160 matches
Mail list logo
