Hi all,
I've noticed that adding the :STYLE: habit property to a TODO causes
its position in the agenda view to change; it jumps to the bottom of
the day. Is there any way to prevent that?
Thanks!
Adam
particularly
convenient.
I can even imagine users occasionally wanting to mark stuff done in
the future, e.g. if they have an activity planned for tomorrow while
they're offline. So maybe using the word 'retroactive' in the wrapper
function name is a bit too limiting.
Cheers,
Adam
Hi Bastien,
On 6/1/20, Bastien wrote:
> Hi Adam,
>
> Adam Porter writes:
>
>> The relatively recent moving of org-get-outline-path to org-refile.el
>> has caused breakage in Org itself in several places, e.g.
>>
>> https://lists.gnu.org/archive/html/emacs-or
ted as non-link text.
>
> Let me know if this seems okay for you.
>
> I'm copying Adam as he may comment on that too.
That seems like an elegant solution. Thanks, Bastien.
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Adam Porter writes:
>
>> The relatively recent moving of org-get-outline-path to org-refile.el
>> has caused breakage in Org itself in several places, e.g.
>
> [...]
>
>> Thankfully, Kyle has proposed
David R writes:
> On Saturday, January 25, 2020, Adam Porter wrote:
>
>> I care about stability, not MELPA Stable. It's your choice to use MELPA
>> Stable, and you're free to upgrade or downgrade individual packages to
>> work around such occasional, temporary breakage
in the NEWS file.
Thanks,
Adam
Hi Bastien,
I've been keeping an eye out for you! :) Glad to hear you're well, and
I'm looking forward to your return.
Adam
ook. Finally I would be grateful for
> any comment whatsoever (e.g. regarding the name of org-id-cleanup.el).
Hi Marc,
Thanks, this looks useful. I posted some feedback as an issue on the
repository.
Adam
On Wed, 2020-04-01 at 11:02 +0200, Oliver Heck wrote:
> > Off-topic: Oliver is exporting/engraving to a fixed-resolution png. An
> > alternative
> > is to export scalable vector graphics of the score to PDF.
>
> PDF does scale better, but it does not help because I need the original
> size
On Tue, 2020-03-31 at 10:48 -0300, Jonathan Gregory wrote:
> Hi
>
> On 30 Mar 2020, stardiviner wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> >
> > stardiviner writes:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA256
> > >
> > >
> > > You might want
Ihor Radchenko writes:
> FYI:
> I have recently stumbled upon a FOSS service for video conferencing:
> https://meet.jit.si/ (recommended in Tor blog
> https://blog.torproject.org/remote-work-personal-safety)
>
> Might be another option for future meetings.
Yes, that's what was used for
ndame writes:
> As for org-at-table-p being slow storing the start and end position of
> the table could be a solution, so if point is between them then there
> is no need to check org-at-table-p again.
>
> org-table-align seemed fast enough for me when I tried the posted
> code, but if it's
"Mark E. Shoulson" writes:
> Heh; fair enough. The filename originally was "org-level-end.el", I
> think; I started using the catchier "org-pop" because... well, it was
> catchier. It made sense in my mind, in the "push"/"pop" sense used
> with stacks in programming, that you "push" to a
"Mark E. Shoulson" writes:
> This is something I've wanted for years in org-mode, but which in some
> ways could actually be _offensive_ to its ideals. If you're an
> outline purist, look away.
>
> ...
>
> So, I present a pre-alpha version,
>
Colin Baxter writes:
> In my opinion, if it can't be fixed then the changes should be
> removed. Surely, we cannot have an org-mode that knowingly
> exports/publishes something that causes a validation error!
Looking at the error message, the fix might be very simple:
The most common cause
Thanks to John for hosting, and to all who "attended" virtually. It was
great fun. Looking forward to doing it again.
Please don't add more arguments to org-get-heading. It used to have 2,
then it had 4, and now you want to add a 5th. Every time the function's
signature changes, it breaks code in third-party packages and user code
in random places, which requires the addition of messy compatibility
code and
Kaushal Modi writes:
> Failure 1: org-get-outline-path has moved, and not mentioned in ORG-NEWS
>
> Compiling ox-hugo.el now gives:
>
> ox-hugo.el:4284:1: Warning: the function ‘org-get-outline-path’ is not known
> to be defined.
>
> I see that defun has now moved to org-refile.el. I see that
>
Hi Russell,
This is not exactly what you asked for, but here's some code that
ensures blank lines exist between headings and entry content. You could
modify it to remove excess lines without too much trouble.
Marco Wahl writes:
- org-loop-over-headlines-in-active-region => t
>>>
>>> I vote for => 'start-level. Loop over headlines with same level as the
>>> first.
>>
>> Yes, good suggestion.
>
> Let's see what others say.
I can see how that could be useful, but I feel like it would be less
I generally approve of all of these changes. However, hiding emphasis
and macro markers can make editing text at the boundaries of emphasized
text non-intuitive, which I can imagine might frustrate some new users,
so that should probably be carefully considered. The other changes seem
like
Hi Bastien,
Bastien writes:
> Hi Adam,
>
> Adam Porter writes:
>
>> https://alphapapa.github.io/org-almanac/
>
> this is a very nice list of resources!
>
> Do you think we can advertize it somewhere on Worg?
>
> If yes but are unsure *where*, just go ahead
Stig Brautaset writes:
> Hi Bastien,
>
> Bastien writes:
>>> I can easily do this in the list of TODOs, with a tag search. However, I
>>> haven't figured out how to do this for the agenda. Is it possible? If
>>> so, how?
>>
>> From what I understand, check `org-agenda-tag-filter' to see how to
for all your contributions,
Adam
Bastien writes:
> First of all, don't be afraid, I don't have a grand plan for "cleaning
> up" things.
Don't worry, I trust you. :) Org wouldn't be what it is today without
your work, and I'm grateful for how much time you've been putting into
improving Org lately.
>> I'm not sure what you
Hi Bastien,
Bastien writes:
> I still find it strange to keep functions that are used nowhere in the
> Org's core--except of course for functions that explicitely mention as
> usable by the user (e.g. `org-clock-persistence-insinuate'.)
>
> I'd rather have these functions stored in a
or
use the Customization system. Here's a screencast of it:
https://github.com/alphapapa/org-ql/raw/master/images/org-ql-view-dispatch.gif
It seems to work well, but I'd appreciate any feedback.
Thanks,
Adam
Diego Zamboni writes:
> I came up with the following block, which cleans up all the cruft from
> the output of the =script= command and produces a nicely formatted
> session transcript:
>
> #+NAME: cleanup
> #+BEGIN_SRC emacs-lisp :var data="" :results value :exports none
>
Texas Cyberthal writes:
>> the default settings do not put blank lines between headings and
>> their entry text,
>
> I don't know what this means. Plain Emacs behaves the same way
> Spacemacs does in this regard. Insertion of a blank line after a
> heading is voluntary but standrd.
I don't know
Texas Cyberthal writes:
>> visual-line-mode and toggle-truncate-lines are basic Emacs commands
>> that all users should learn early.
>
> Visual lines, logical lines etc is a complicated mess that Spacemacs
> avoids entirely. I recall fiddling with it and never being satisfied,
> until adopting
Texas Cyberthal writes:
> Making a vet change a default if he decides he doesn't like a change
> upon upgrading won't drive him away, but Emacs' unfriendly defaults
> are always driving away noobs. Therefore Org's defaults should be
> noob-friendly, not vet-friendly.
There is certainly room to
Nicolas Goaziou writes:
> Note that, at some point, Org will support "seq.el", i.e., when we
> drop support for Emacs 24.
Just a small FYI about seq.el, for those who may not be aware: while
it's a very useful library, it can be quite slow since it uses generics.
For example, here are some
Texas Cyberthal writes:
> Code requires less line spacing. It has more whitespace, fewer capital
> letters, and no markup such as underlining. Code is read differently
> than prose; it requires less sequential scanning.
Code certainly can have markup like underlining. For example,
Texas Cyberthal writes:
> Readable prose requires variable-pitch font. Readable code requires
> fixed-pitch font. Org should make it easy to configure the two
> separately.
>
> mixed-pitch-mode mostly solves this problem, but only advanced users
> know about it.
>
Texas Cyberthal writes:
> #+begin_src elisp
> (org-adapt-indentation nil)
> #+end_src
>
> Adaptive indentation makes sense when using Org as a plain-text
> database. It does not make sense when using Org for longform prose.
>
> In the former case, outline depth is important to reflect properties
Texas Cyberthal writes:
> #+begin_src elisp
> (org-startup-truncated nil)
> #+end_src
>
> Line truncation is necessary for code but anathema for prose. Prose
> lines need visual wrap as windows resize, so that texts can be
> compared easily.
>
> Advanced Org uses such as large tables require
Texas Cyberthal writes:
> Beginners spend a while learning to use Emacs as a simple text editor
> before they're able to do anything more advanced. Their ability to
> intelligently customize is minimal. Meanwhile experts have automated
> dotfile deployment, so defaults are almost irrelevant to
As Tim said, this is really a matter for theming. There are several
themes and example configs available that make Org buffers "pretty".
For example:
https://github.com/kunalb/poet
https://github.com/jonnay/org-beautify-theme
https://lepisma.xyz/2017/10/28/ricing-org-mode/
As well, faces are
Bastien writes:
> `org-insert-subheading' and `org-insert-todo-subheading' are not used
> anywhere in Org's code. Do you them? How?
>
> I'm more inclined to delete these commands since they have no binding
> than to add an `org-insert-subitem'.
>
> Hitting then seems swift and handy enough.
Hi D,
This looks fantastic! Great work! I sent you a quick suggestion on the
issue tracker. Let's get this on MELPA ASAP! :)
"Tyler Smith" writes:
> I am trying to set up an account with code.orgmode.org. I have already
> done this, but when I try to sign in, I get an error about incorrect
> username or password. I have clicked the link to send a password reset
> several times this morning, but no email has shown up
FYI, Jonas Bernoulli also maintains a similar page for Emacs in general:
https://github.com/tarsius/elisp-maintainers
Marco Wahl writes:
> For some days now C-c C-c disables column view in Org files. This helps
> me a bit and never got in my way. And I thought it would be quite
> natural and consistent to use this binding for the agenda too.
>
> What do you think about all that?
Hi Marco,
I've always had
There are various solutions floating around. Here's one way:
(defun ap/org-count-words ()
"If region is active, count words in it; otherwise count words in current
subtree."
(interactive)
(if (use-region-p)
(funcall-interactively #'count-words-region (region-beginning)
Michael Alan Dorman writes:
> On the other hand, I *also* don't assume that maintainers are incapable
> of making a reasonable assessment of the stability of their packages, or
> of making a personal choice to try to maintain API compatibility in some
> sensible way, and so forth.
If it were
Tim Cross writes:
> I don't disagree with most of what you write. I do think a big part of
> the problem is inconsistency and poor practices by some maintainers
> which is at the hart of the issue. Sometimes it seems that package
> maintainers put too much emphasis on getting the latest package
Michael Alan Dorman writes:
>> Hi friends,
>>
>> FYI, I've released org-ql 0.4. It includes many improvements since 0.3.
>>
>> https://github.com/alphapapa/org-ql
>
> It would be nice if you could do a stable release of org-super-agenda so
> that it could be installed from melpa-stable...
Hi friends,
FYI, I've released org-ql 0.4. It includes many improvements since 0.3.
https://github.com/alphapapa/org-ql
Thanks,
Adam
On Sun, 2020-01-12 at 10:43 +1300, adam wrote:
> On Sun, 2020-01-12 at 09:04 +1300, adam wrote:
> >
> > On Sat, 2020-01-11 at 12:30 -0300, Jonathan Gregory wrote:
> > >
> > >
> > >
> > > On 11 Jan 2020, adam wrote:
> > >
>
On Sun, 2020-01-12 at 09:04 +1300, adam wrote:
> On Sat, 2020-01-11 at 12:30 -0300, Jonathan Gregory wrote:
> >
> >
> > On 11 Jan 2020, adam wrote:
> >
> > >
> > >
> > > Still no success in tangling the examples modal-cycle.org
&
On Sat, 2020-01-11 at 12:30 -0300, Jonathan Gregory wrote:
>
> On 11 Jan 2020, adam wrote:
>
> >
> > Still no success in tangling the examples modal-cycle.org
> > modal-cycle2.org
> > shown here,
> > https://orgmode.org/worg/org-contrib/babel/lang
Still no success in tangling the examples modal-cycle.org modal-cycle2.org
shown here,
https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html
My current problem is Emacs rejecting the addition of either Lilypond or
lilypond, in the org-babel-do-load-languages
On Sat, 2019-04-20 at 14:04 +0200, Jakob Schöttl wrote:
> Hi,
>
> I'm trying (second attempt), to setup orgmode to export PDFs with images
> generated by Babel/LilyPond.
>
> I followed the setup instructions here:
>
> https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html
>
Steven Penny writes:
> yes, and I would have never made this point had you not insisted on
> starting an off topic conversation.
>
> Next we know you will say why someone is using spaces over tabs, or
> emac over vim, or red over blue bikeshed. Stop.
This rude one-upsmanship is uncalled for.
Someone reminded me that Org has org-num-mode now, so please disregard
all of that. At least it was good exercise.
Adam Porter writes:
> There is no built-in way to do that, and no way independent of
> org-export to get the numbers, AFAIK.
>
> Here's some ugly old code that shows outline numbering as overlays in an
> Org buffer. It doesn't update automatically, so you have to run it
> agai
FYI, I tidied the code a tiny bit and posted it here:
https://github.com/alphapapa/unpackaged.el#outline-number-overlays
There is no built-in way to do that, and no way independent of
org-export to get the numbers, AFAIK.
Here's some ugly old code that shows outline numbering as overlays in an
Org buffer. It doesn't update automatically, so you have to run it
again when the outline changes. But it seems to work
stardiviner writes:
> I recently created an org-capture template for elfeed, it is finished. Now I
> have an idea is to refile it to all currently opened Org buffer files. So I
> created an function for ~org-refile-targets~ variable.
>
> #+begin_src emacs-lisp
> (defun
You may find the package org-web-tools useful.
Ihor Radchenko writes:
> If you accidentally move the point in the buffer being processed by
> agenda, the results may be unpredictable (org-agenda-get-* functions
> move across the buffer with re-search-forward).
I'm afraid that's the basic problem with threading in Emacs: shared
state. I
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
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 they should
>>
rt can be
> closed?
I haven't seen your bug report. Was there discussion about it
previously?
Adam
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
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
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
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
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:
>> 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
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.
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
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
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
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
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 them.
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.
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.
Hi Ian,
There's a small typo in the docstring. :)
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.
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")
>
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.
Thanks for working on and sharing this, Karl. It's great to see the Org
format getting more support in other languages and contexts.
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
Thanks. Just found that now.
Has the emacs-orgmode mail-list ceased including a [O] in the subject
line of its mails? Or, what has changed here?
I was using [O] as a filter for my incoming mails, now they are
turning up unsorted amongst my general mail.
OK. I can filter on and Sorry for the noise.
Any
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
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 "#":
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
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
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
Hi Greg,
That's very cool! Thanks for sharing it.
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
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
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.
-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
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:
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,
101 - 200 of 866 matches
Mail list logo
