Julien Cubizolles writes:
> Got it: the problem occurs when trying to clear the TODO state of
> several entries through a bulk action:
>
> * mark several entries
>
> * "B t" doesn't offer to clear the TODO state with space like "t" does
> on a single entry.
Yes, I guess that's because it uses
Julien Cubizolles writes:
> In an agenda buffer, C-u B d should clear the deadline of the entries
> marked the way C-u does on a single entry. I think it's what it used to
> do some time ago. Instead, I get:
>
> org-agenda-deadline: Invalid function: 4
FWIW, works for me on Org 9.0.5.
Kyle Meyer writes:
> Since you have the git repo set up and have a good/bad range, you can use
> git bisect to find the offending commit.
>
> Based on changes that touched org-agenda-bulk-action recently, my guess
> is 4f578a3f7 (org-agenda: Small refactoring, 2017-05-12). Quickly
> looking at t
Julien Cubizolles writes:
> That's also what it does. It's only a minor annoyance I just noticed
> because I'm in the process of cleaning long overdue tasks, but it would
> be nice if B t could use the same dialog.
Agreed! :)
I guess
it may also be useful for Org users who don't use that package.
Thanks,
Adam
>From 8ae87be7ba98dec23b6875b72234272b78ea76a8 Mon Sep 17 00:00:00 2001
From: Adam Porter
Date: Tue, 15 Aug 2017 23:01:32 -0500
Subject: [PATCH] org-agenda: Add 'none setting for
org-agenda-overr
Although I've read all of the messages in it, this thread has not been
especially easy to follow.
Whatever changes are made, we should ensure that there are no
regressions as a result. This should mean that:
1. Existing Org users who install the new version of Org and export
documents to HTML s
Nicolas Goaziou writes:
> I assume this is the only way out of this, so I'll have a look at it.
> But I need time. What would help would be some feedback from users
> actually tweaking `org-html-htmlize-output-type'. What do they expect
> from the various values, etc.
I don't understand what's g
Kaushal Modi writes:
> With Org/ox-html, it's the same thing. Ox-html is part of Emacs
> core. So it cannot rely on htmlize.el.
1. Why not? I just git-blamed this line in ox-html.el:
(declare-function htmlize-region "ext:htmlize" (beg end))
It's from February, 2012. That's 6 and a half ye
Kodi Arfer writes:
> As of
>
> https://code.orgmode.org/bzg/org-mode/commit/b186d1d7236c0dc397eadeb004c9a17eaffd3aab
>
> archiving a subtree no longer automatically saves the archive
> file. How can I get this behavior back?
>
> A Debian bug was also opened for this issue:
>
> https://bugs.debian
Hi Marcin,
My feedback is: there be dragons. ;) The Agenda code is very
complicated and hard to follow, and it's hard to optimize something that
is hard to understand.
In the long run, to get significant speed improvements, I think it may
be necessary to reimplement the Agenda. However, due to
Nicolas Goaziou writes:
>> my understanding is that code that runs with lexical-binding enabled
>> is generally faster.
>
> Not really. But it's certainly easier to understand since it removes one
> class of problems.
>From what I've read, the byte-compiler can optimize better when
lexical-bindi
Hi Marcin,
That sounds very geekily interesting. :) I imagine Sacha Chua might be
interested as well, although she already has a sophisticated system for
her Quantified Life stuff.
I'd be interested in looking at your code. For several years I've used
a "pomodoro"-like shell script to help sta
Thanks for sharing that, John. Glad to see John (the other one) getting
more recognition for his work!
mation and optimization. I don't have much experience with that
kind of programming; maybe someone else would be interested in helping
with that.
So before taking any of the code into Org itself, you might want to
consider these issues and decide whether it could be a suitable
approach. Let me know what you'd like to do and how I can help.
Thanks,
Adam
On Oct 18, 2018 5:48 PM, "Nicolas Goaziou" wrote:
> Are you saying that queries are turned into regexp searches within Org
files? If so, I don't think they should.
Yes, because this is the fastest way to search for matching entries in a
buffer, when it's possible to use a regexp search.
> Queri
Tables with multibyte characters and ASCII are not aligned properly after
org-table-align in GUI mode.
In -nw mode table is properly aligned, but its incorrect in GUI mode.
Steps to reproduce:
Start emacs in GUI mode. Copy and paste table below to org-mode buffer. Put
emacs cursor inside the tabl
ides
tools like org-ql-agenda and org-ql-search that provide agenda-like
views.
Please let me know if you have any feedback.
Thanks,
Adam
Hi Nathan,
Well, this is an unorthodox solution using org-ql, but it seems to work.
So, for what it's worth:
#+BEGIN_SRC elisp
(let* ((sub-query (lambda ()
(save-excursion
(save-restriction
(cons (org-ql--add-markers
(org-
Nathan Neff writes:
> Wow - thanks Adam!
>
> Your stuff is awesome. org-rifle is incredible. (I just wish that
> it didn't have as many dependencies -- I guess I'm just a bit paranoid).
Thanks for the kind words.
Which dependencies concern you? helm-org-rifle use
Nathan Neff writes:
> Hello all,
>
> Has anyone created a Helm source from the results of org-agenda?
>
> Specifically org-tags-view I think would be a cool Helm source to
> configure where the headings that have certain tags could be displayed
> by Helm.
>
> I looked @ the code for org-tags-vie
Nathan Neff writes:
> I have a lot of org files and one of the main purposes of links is to be able
> to link
> to different headings across documents. This seems to imply I should use
> the ID property.
>
> However, I usually *do* manually assign IDs (not CUSTOM_IDs) myself. The
> reason is
Nathan Neff writes:
> * Show the IDs (*and* headings :-) of recently created links (because you
> know,
> the IDs are hash codes (grumble grumble). Currently Helm just shows the IDs
> :-(
Small pedantry: they're UUIDs, not hashes. The distinction is
important, because UUIDs are generated ran
Nathan Neff writes:
> I know, but rifle has so many dependencies
>
> Rifle is truly awesome, I just have to convince myself to trust
> f.el and d.el or whatever those one-letter libraries are :-)
helm-org-rifle's dependencies are libraries which have been around for
over 6 years and are used
Try using the bug-hunter package to isolate the part of your init file
that may be causing the problem.
Carsten Dominik writes:
> You system assumes, if I see that correctly (have not studied it yet),
> that not more that one ID will be created per second. Or do you have
> something in place that will catch this, for example if someone uses
> the mapping API to assign IDs to a whole bunch of entri
e it (e.g. as a module, etc).
Thanks,
Adam
Thanks for sharing those links, those videos are fascinating. It's
amazing how much some of what he demonstrates resembles features in Org
and Emacs, and even surpasses them, over 50 years ago! Even the
presentation itself, with picture-in-picture videoconferencing with
screen sharing, surpasses
Samuel Wales writes:
> i thought the visibility property already did this.
This allows more powerful and flexible configuration. Please see the
examples in the readme.
herwise, I could submit a patch.
Thanks,
Adam#+BEGIN_SRC elisp :results silent
(defun org-olp-marker (olp &optional this-buffer unique)
"Return a marker pointing to outline path OLP.
Return nil if not found. If THIS-BUFFER, search current buffer;
otherwise search file found at
I see that using an "inline" attachment was a bad idea. At least, the
lists.gnu.org Web UI wraps the lines. Here it is as an "attachment"
attachment, in case that helps.
#+BEGIN_SRC elisp :results silent
(defun org-olp-marker (olp &optional this-buffer unique)
"Return a marker pointing to
Samuel Wales writes:
> i do (eq major-mode 'org-agenda-mode)
That works, but you should probably use:
(derived-mode-p 'org-agenda-mode)
Milan Zamazal writes:
> Hi Adam,
>
> thank you for the feature. I looked at org-ql and org-super-agenda (for
> the first time) and they look interesting. So interesting that I've
> decided to convert my agendas to it, with some improvements. It took a
> lot of effort a
Samuel Wales writes:
> i have been watching these developments with interest. i want a
> faster 2-day agenda, and really like the idea of a lisp syntax for
> querying, perhaps one that can combine text search with structured.
>
> so just so it's known that there is otherwise silent interest.
> l
Samuel Wales writes:
> the idea was that we can resurrect the timeline view, for all agenda
> files instead of only one, merely by a use of a text search custom
> agenda view. timestamps go where categories currently go. sorted by
> that ts.
>
> if an entry has more than one ts (active bare, in
Mikhail Skorzhinskii writes:
> Adam Porter writes:
> > However, the org-ql-block version runs in about 1/5th the time (0.7
> > seconds compared to 3.45 seconds on my collection of org-agenda-files).
>
> For some reason I thought that on average org-ql package is working
Gustav Wikström writes:
> I'm continuing on my proposal to introduce a "document" element in
> org-mode and the idea of seeing everything before the first headline
> as the base level 0 outline for a file. I've attached two patches that
> I'd like some public review of before pushing to master.
>
Gustav Wikström writes:
> Yeah – you’re right, I didn’t think that much about automated ID
> creation so I stopped at seconds. I agree that it would be more
> general with more precision but that will also add some more noise
> into each ID. Maybe that’s not significant. But I also wonder how
> c
Hi Andrea,
This is a nice idea. Here are a few notes:
1. You should implement it as a minor mode, and enable/disable the
hooks there.
2. I would generally recommend using org-element to help with parsing.
It will make your code much cleaner and easier to understand. Much of
the searching cod
tumashu writes:
> + (when org-agenda-show-indirect
> + (let ((org-indirect-buffer-display 'current-window))
> + (org-tree-to-indirect-buffer)
> + ;; hide indirect buffer in ibuffer
> + (rename-buffer (concat " " (buffer-name)
1. That does not affect only ibuffer,
Gustav Wikström writes:
> Nicolas requested a more thorough introduction to the patch so here it
> comes.
Thank you, this is helpful.
> The first patch deals with formalities. It introduces one new greater
> element called "document". Parsers and everything around it are
> modified to work with
Gustav Wikström writes:
Hi Gustav,
Thanks for your reply. I sent my most recent message, which reiterated
my question, before this message of yours came through.
>> This is a very interesting idea, and I don't want to dismiss your work,
>> but I am concerned about how much third-party code wil
Hi Josiah,
You may find org-ql helpful, as it makes selecting entries easy and
flexible.
https://github.com/alphapapa/org-ql
Here's an example that might help:
https://github.com/alphapapa/org-ql/blob/master/examples.org#stuck-projects-block-agenda
Josiah Schwab writes:
> Hi Adam,
>
>> You may find org-ql helpful, as it makes selecting entries easy and
>> flexible.
>>
>> https://github.com/alphapapa/org-ql
>>
>> Here's an example that might help:
>>
>> https://github.com/alphapapa/
Samuel Wales writes:
> i was merely trying to get a sense of the degree to which it is a
> drop-in replacement (which i think you have said it is not).
Right, it doesn't do everything Org Agenda does. Since Org Agenda does
also serve as a kind of "search view," org-ql can largely serve as a
rep
:
https://github.com/alphapapa/org-ql#helm-org-ql
Please let me know if you have any feedback.
Thanks,
Adam
"numbch...@gmail.com" writes:
> org-notify dbus send message to KDE/Plasma caused desktop suspend and high
> CPU,memory resources.
>
> Here is my config:
> ```elisp
> (setq org-notify-audible nil)
> (org-notify-add 'default
> '(:time "1h" :period "1h" :duration 8
>
Mikhail Skorzhinskii writes:
> Great overview, thanks a lot.
>
> So I give it a try and completely fell in love. On my data set it is
> visibly faster then org-agenda. I also wrote a lot of code around
> org-agenda over the years to support my sometimes awkward needs. And now
> I just threw all t
Matt Price writes:
> Is there a lisp trick for adding arguments to the function called by
> `org-map-entries`?
>
> I have the following function:
>
> (cl-defun org-lms-return-all-assignments (&optional (send-all nil) (also-mail
> nil) (post-to-lms t) )
> "By default mail all subtrees 'READY' t
Matt Price writes:
> This is fun, thanks John. I really like the plist version put would
> also like to loop through the variables in a let statement somehow.
>
> I think what I'm missing is the equivalent of a javascript implicit
> destructuring construct:
>
> let { } = object;
>
> which will de
Joost Kremers writes:
> On Wed, Sep 18 2019, Matt Price wrote:
>> Is thre away to do that kind of destructuring bind -- which
>> binds *everything* in the plist, without knowing the symbol names in
>> advance? that would be really great.
>
> let-alist perhaps?
Well, let-alist is for alists, not
John Kitchin writes:
> I am not sure why you have to loop over everything in a let statement
> though. you can use something like
> https://github.com/nicferrier/emacs-kv to get all the keys an loop
> over those to do what you want, or you can just use cl-loop to do
> that.
Recent Emacs versions
Matt Price writes:
> OK, this is pretty cool, thank you. I took John's excellent
> suggestion of using a headline property to store the appropriate
> actions, but it makes sense to switch to org-ql if I can master the
> syntax (which seems awfully powerful). One questions: does
> org-ql-se
For parsing timestamps, you may find this helpful:
https://github.com/alphapapa/ts.el
See e.g. functions ts-parse-org and ts-parse-org-fill.
See unpackaged/org-refile-to-datetree from:
https://github.com/alphapapa/unpackaged.el#refile-to-datetree-file-using-earliestlatest-timestamp-in-entry
Greg Minshall writes:
> hi, all.
>
> for a project, i wanted to be able to easily query the contents of a
> table in an org-mode document from the shell. in case that it might be
> useful to others, the result is:
>
> https://gitlab.com/minshall/org-query
Hi Greg,
That's very cool, thanks
Gustav Wikström writes:
> Hi,
>
> This patch introduces a document level property drawer.
>
> This has been discussed previously in a larger context:
> - https://lists.gnu.org/archive/html/emacs-orgmode/2019-06/msg0.html
> - https://lists.gnu.org/archive/html/emacs-orgmode/2019-08/msg00339.h
Greg Minshall writes:
> i've renamed the gitlab *project* org-table-query-script, though i've
> kept the command, itself, the simpler org-query. does that seem
> reasonable?
Sure, thanks. :)
Marco Wahl writes:
> Adam Porter writes:
>
>> Gustav Wikström writes:
>>
>>> 3) Properties defined in a property drawer will have precedence over
>>>properties defined as a property keyword, if the same property is
>>>defined using both con
ms to work well, but I'm sure wider testing will reveal some
improvements to be made. I'd appreciate any feedback.
Thanks,
Adam
"Fraga, Eric" writes:
> Hi Adam,
>
> I've had a chance to play with it a little bit. Works very well
> generally. Some notes:
Hi Eric,
> - a way to exit the sidebar-tree mode to get back to the full buffer
> (e.g. to run commands that require the whole fi
Marco Wahl writes:
> You say the visibility is better for the #+-property keywords. I say
> they can occur _anywhere_ in the file and even in some drawers. See
> above "#+CATEGORY: cat-doc-prop-keyword-2".
>
> Further you say
>
- However, it seems to me that the simplest, most natural pr
Hi Gustav,
Gustav Wikström writes:
> I'd argue that precedence already works that way. One has to take
> inheritance into account. With inheritance turned on, tell me which
> value for Property1 is used for the nodes in the following example:
>
> #+begin_src org
> ,* Node 1
> ,* Node 2
> :
Gustav Wikström writes:
>> In Org, some keywords are special, like #+CATEGORY. For many years,
>> such keywords have had file-wide effects regardless of their placement
>> in the file. IIUC, your proposal would change that, and that would
>> still be a major, breaking change.
>
> This seems dis
Marco Wahl writes:
> One could even think about letting fade out the "#+"-file-wide
> property definition syntax or at least think about a good place within
> a file or a subtree for those definitions. (There is at least
> Sebastian Miele who wants to keep that syntax as he stated in another
> t
Marco Wahl writes:
> Just I got the idea that for a good part this discussion is about
> personal preferences.
Personal preferences are relevant to this issue in that Org is flexible
and allows users to configure it accordingly. But that is not the only
consideration at stake. Consistency, com
Hi friends,
Version 0.3 of org-ql has been released. There are many changes,
including a new helm-org-ql command and an alternative, non-sexp query
syntax.
- Changelog: https://github.com/alphapapa/org-ql#03
- helm-org-ql demo:
https://github.com/alphapapa/org-ql/raw/master/images/helm-org-ql.g
, org-super-agenda, and org-ql. If the API
were to change, it would create significant headaches in writing
compatibility code for different Org versions.
I can't easily tell if that's something that's been proposed, but I'm
making the request just in case.
Thanks,
Adam
stardiviner writes:
> This is really a helpful sidebar package. Thanks :) I like it very much.
>
> Hope can add an command to toggle it. I found I have to manually close it.
FYI, I just added some toggle commands. Thanks for the suggestion.
Nathan Neff writes:
> I'm trying to implement a function to display the TODO items of the
> currently highlighted item in the agenda and have a few questions:
>
> Goal:
>
> 1) From the agenda, place the cursor on a heading.
>
> 2) Press a key and instantly narrow the agenda to the heading which
>
Gustav Wikström writes:
> Hi again,
>
> I'd like to take the next step with this patch. I'm hesitant to do it
> without wider support though, since only a few people have commented.
>
> @Marco Wahl; As I understand you've applied the patch and tried it
> out. Have you found any issues yet? What d
Hi Greg,
That's very cool! Thanks for sharing it.
Hi Sebastian,
Sebastian Miele writes:
> * lisp/org-src.el (org-src--contents-for-write-back): Use the
> potentially buffer-local value of `org-edit-src-content-indentation'
> from the source buffer instead of that from the editing buffer.
> ---
> lisp/org-src.el | 3 ++-
> 1 file changed, 2 ins
Gustav,
There are a lot of deprecation recommendations in your attached
document:
> I propose to depricate property-keywords
> I propose to depricate the Options-keyword
> I propose to relabel these keywords as document keywords
> I propose to depricate the #+CATEGORY syntax
> I propose to depric
Clearly my Gnus-fu is weak, as somehow I posted that in entirely the
wrong thread. :)
Gustav,
There are a lot of deprecation recommendations in your attached
document:
> I propose to depricate property-keywords
> I propose to depricate the Options-keyword
> I propose to relabel these keywords as document keywords
> I propose to depricate the #+CATEGORY syntax
> I propose to depric
I agree with Robert that "whitespace" includes newlines in "Emacsland."
For example, with this document (the second "#" has a newline
immediately after, no spaces or tabs):
#+BEGIN_SRC org
foo
# comment
bar
#
buzz
#+END_SRC
This code matches both lines that begin with "#":
(re-search-forwa
ian martins writes:
> Hello, I wrote some helper functions for generating a scrum board and
> reports that is built on top of org-mode. The project is currently
> emacs-scrum. I submitted it to melpa recently and got the suggestion
> to name the package org-scrum since it's based on org-mode. Is
Eric Abrahamsen writes:
> I think this last point is key. Most full-text search engines provide
> config options for defining fields, or "facets", which in theory we
> could set up to parse tags/properties/timestamps.
Of course it's an Emacs-based tool, but please note that org-ql has
extensive,
Thanks for working on and sharing this, Karl. It's great to see the Org
format getting more support in other languages and contexts.
org-ql would make this pretty easy, I think. Use an org-ql query to
select entries, and for the :action function, use a simple function that
copies the entry or subtree and yanks it into a buffer. Then save that
buffer to a file.
Mikhail Skorzhinskii writes:
> Here is the snippet I am currently using to export all subtress directly
> tagged with :info: to the separate file. (Sorry for the lack of proper
> parametrisation).
>
> #+begin_src emacs-lisp
> (defun org-user/store-info ()
> (let ((file "~/org/cals/info.org")
>
Have you checked these settings?
M-x customize-group RET org-agenda RET
Be sure to check the subgroups as well--there are many options.
Hi Ian,
There's a small typo in the docstring. :)
This seems to duplicate functionality from org-get-outline-path. As
well, org-eldoc displays in the minibuffer the outline path for the
heading at point.
Karl Fogel writes:
> By the way, when I run `M-x eldoc-mode' in a Org Mode buffer, I get this
> message:
>
> "There is no ElDoc support in this buffer"
>
> Am I doing it wrong?
You need org-eldoc.el from /contrib.
Karl Fogel writes:
> Thank you, Adam -- I didn't know about those. I had searched for
> something like that before implementing my own, but I think I searched
> using the term "heading" or something instead of "outline",
> unfortunately, so I never found th
Karl Fogel writes:
> Unless you meant make a new interactive function to display a vertical
> hierarchy and base it on the existing Org Mode functions you informed
> me of the existence of? But I don't think there's a way to do that
> without adding some new parameters to those existing function
Karl Fogel writes:
> Unless you meant make a new interactive function to display a vertical
> hierarchy and base it on the existing Org Mode functions you informed
> me of the existence of? But I don't think there's a way to do that
> without adding some new parameters to those existing function
Functions like helm-org-in-buffer-headings,
helm-org-agenda-files-headings, etc. are built-in to the helm-org
package (they used to be part of the helm package, but now they're in
this separate helm-org package which is not installed automatically with
the helm package).
The packages org-rifle and
Be sure to read the Emacs Lisp manual regarding threads. They are
cooperative, so functions called as threads must yield back to the main
thread for Emacs to do anything else before the function returns.
If you're feeling adventurous, you could experiment with adding yields
in relevant agenda fun
May I recommend using the rx macro for regexps? They are much easier
for humans to parse, which helps reduce errors like the ones mentioned
here. And they are about to gain some very useful new features
in Emacs 27.
Ihor Radchenko writes:
>> Be sure to read the Emacs Lisp manual regarding threads. They are
>> cooperative, so functions called as threads must yield back to the main
>> thread for Emacs to do anything else before the function returns.
>
> I tried to read the manual, but I clearly misunderstand
Ihor Radchenko writes:
>> org-ql doesn't use skip functions, just queries.
>
> Skip functions are essentially used-defined queries as soon as the
> queries are tested against every headline.
Skip functions aren't necessary with org-ql, because the query itself
can have arbitrary Lisp code. So,
Ihor Radchenko writes:
>>> Asynchronous code is not faster; it's generally slower because of
>>> yielding and synchronization.
>
>> Anyway, I will try to throw yields into agenda code just to check how
>> bad the performance can degrade.
>
> With the following code, org-agenda-redo runs for 21 se
Michael Heerdegen writes:
> Or (really better IMHO) consider a different implementation where the
> original buffer is not modified until the user explicitly confirms the
> stuff to capture with C-c C-c.
That would be helpful in some ways, but harmful in others. For example,
consider a capture
How does this idea compare with Akira Komamura's org-starter package?
https://github.com/akirak/org-starter
Its readme begins:
> Org-starter is a framework for basic configuration of Emacs Org
> Mode. It allows you to configure Org Mode easily even with many files
> and directories.
> The stand
Ihor Radchenko writes:
>> So, of course, you can call custom functions in queries, even your
>> own skip functions (with `not', of course), but in most cases, they
>> can be covered with built-in predicates.
>
> Unfortunately, it does not seem to be the case for me. My main agenda
> view needs t
r my original bug report can be
> closed?
I haven't seen your bug report. Was there discussion about it
previously?
Adam
Michael Heerdegen writes:
> Adam Porter writes:
>
>> I guess you're asking me, since I'm the only other person in this
>> thread--but I'm not an Org maintainer, so my opinion isn't very
>> important. IMO, the hooks are worth considering, however
I'll try to explain my view of tags. Let's see if it makes sense. :)
Conceptually, properties are like a generic key-value store for
headings, and tags are like a certain property. Imagine if, instead of
tags being placed in headings, like this:
* Blueberries :food:fruit:
...tags were impl
501 - 600 of 918 matches
Mail list logo
