Re: [O] function for inserting a block

Kaushal Modi writes: > On Sat, Sep 2, 2017, 10:23 PM Adam Porter wrote: > > Hi Eric, > > Thanks for doing this. I've had some similar code in my config for a > while. I'll share some of it here in case you find it useful in doing > this. You

Re: [O] function for inserting a block

On Sat, Sep 2, 2017, 10:23 PM Adam Porter wrote: > Hi Eric, > > Thanks for doing this. I've had some similar code in my config for a > while. I'll share some of it here in case you find it useful in doing > this. You especially might find the org-read-structure-template >

Re: [O] function for inserting a block

Hi Eric, Thanks for doing this. I've had some similar code in my config for a while. I'll share some of it here in case you find it useful in doing this. You especially might find the org-read-structure-template function useful. Note that some of this uses s and hydra, which obviously isn't

Re: [O] [PATCH] org-agenda: Add 'none setting for org-agenda-overriding-header

Hi Nicolas, Here is another patch series with the requested changes. Thanks, Adam >From 98a90c8e05acc8733972be731e5a9eb1efe10fee Mon Sep 17 00:00:00 2001 From: Adam Porter Date: Sat, 19 Aug 2017 21:26:12 -0500 Subject: [PATCH 1/2] org-agenda: Refactor

Re: [O] [Patch] Hide the file column in a clock report.

Michaël Cadilhac writes: > While I definitely agree that question form is weird, I copied it from > the ":level" option (arguably without thinking twice) which reads: > > :level @r{Should a level number column be included?} > > In any case, let's not repeat that

Re: [O] Automatic mtime and ctime on all or select group of trees?

Jorge Morais Neto writes: Hi Jorge, Thanks for sharing that, I didn't even remember org-expiry. Very clever use of it! You seem to know more about elisp than you give yourself credit for. :) > Suggestions welcome. It currently > gives compile warnings, which I ignore

Re: [O] Sort error [9.0.9 (9.0.9-88-g251f88-elpa @ /home/someone/.emacs.d/elpa/org-20170821/)]

Hi Nicolas, Nicolas Goaziou writes: > Hello, > > Adam Porter writes: > >> Curious, I see that the functions org-clocking-buffer and >> org-clock-is-active are identical. Should one of these be a deprecated >> alias? > > Indeed, I noticed the same.

Re: [O] Automatic mtime and ctime on all or select group of trees?

Samuel Wales writes: > pedantry: > > birth time, sometimes called btime, is a new kernel feature, present > in some filesystems but not traditionally available to stat. Actually that's a very good reminder, especially for people who work on both Windows and *nix. In

[O] function for inserting a block

The easy template entry thing is useful as far as it goes, but for some reason I find myself "marking up" existing text in Org as least as often as I'm writing new text from scratch. I've always wanted a "wrap region in block" command, and finally wrote one. Don't know why it took me so long.

Re: [O] Automatic mtime and ctime on all or select group of trees?

pedantry: birth time, sometimes called btime, is a new kernel feature, present in some filesystems but not traditionally available to stat.

Re: [O] Automatic mtime and ctime on all or select group of trees?

On 31 August 2017 at 08:55, Tim Visher wrote: > I would like to track the time I created a tree and the last time it was > edited, like ctime and mtime on a filesystem. Is that possible to have > happen automatically? To insert a creation timestamp I use org-expiry. I have

Re: [O] [PATCH] Update statistic cookies when archiving

Sorry, forgot to actually attach the patch, here it is. >From 95cdfa8c3ec81b3a0763b68044611c10a4dadc29 Mon Sep 17 00:00:00 2001 From: Jay Kamat Date: Sat, 2 Sep 2017 15:57:36 -0400 Subject: [PATCH] org-archive.el: Update statistic cookies when archiving *

[O] [PATCH] Update statistic cookies when archiving

Hi, Currently, statistic cookies do not update when archiving headings. For example, when archiving the 'Two' header in the below example: * Top [50%] ** TODO One ** DONE Two The status cookie on 'Top' does not get set to [100%]. I have attached a draft patch to add support for this. However,

Re: [O] [Patch] Hide the file column in a clock report.

On 2 September 2017 at 03:20, Adam Porter wrote: > One suggestion: > > +:hidefiles @r{Should the file column be hidden when multiple files are > parsed?} > > It would be clearer if it said something like, "Hide file column when > multiple files are parsed." The other

Re: [O] [RFC] Remove Org Struct mode

Michael Brand writes: > I assume in the above sentence you meant that a comment to be a > heading has not to be indented. Well, yes and no. On my config, " ;;; test" is highlighted as a heading, but it's only foldable as ";;; test". > That is at least what I

Re: [O] Sort error [9.0.9 (9.0.9-88-g251f88-elpa @ /home/someone/.emacs.d/elpa/org-20170821/)]

Hello, Adam Porter writes: > Curious, I see that the functions org-clocking-buffer and > org-clock-is-active are identical. Should one of these be a deprecated > alias? Indeed, I noticed the same. This could be a first step, but we should also move all "org-clock-"

Re: [O] keyboard scrolling with inline images

This happens to me as well. I always thought it was simply an Emacs limitation. Do any of the options in "M-x customize-apropos RET scroll RET" make a difference?

Re: [O] EXPORT_FILE_NAME property default to heading content?

Hello, Adam Porter writes: > Tim Visher writes: > >> I like the filename of the exported file to always match the content of the >> heading being exported. Is that possible? At the moment I basically >> duplicate it >> like: >> >> ** Foo Heading >>

Re: [O] [PATCH] org-agenda: Add 'none setting for org-agenda-overriding-header

Hello, Adam Porter writes: > You're right, that's why IIRC I used cl-defmacro originally. The > issue here seems to be using the keyword argument. It seemed like a > good idea to specify it with the ":default: keyword argument for two > reasons: > > 1. To make it

Re: [O] EXPORT_FILE_NAME property default to heading content?

Tim Visher writes: > I like the filename of the exported file to always match the content of the > heading being exported. Is that possible? At the moment I basically duplicate > it > like: > > ** Foo Heading > :PROPERTIES: > :EXPORT_FILE_NAME: Foo Heading > :END: I