Re: [O] blank lines after every capture

[Adrian Bradd]

Hello,

I'm on master and this seems to be happening to me also. I haven't 
tested against 9.1, but a quick review of my config seems to 
suggest it isn't a configuration error on my part.


Cheers,

Samuel Wales  writes:

before i try to create a testcase, is anybody getting blank 
lines

after every capture, regardless, in the new 9.2 release?

seems it doesn't matter what you do, even if you do whitespace 
cleanup

in a hook.  blank lines keep getting added.

is this something obvious?  i did not change anything from 9.1.



--
Adrian Bradd

Re: [O] [BUG] org-agenda-skip-*-if-* variables change log mode

[Samuel Wales]

On 12/22/18, Samuel Wales  wrote:
> at least i /think/ this is a bug.

[what i mean is, as opposed to there already being a fix, or it being
an intentional feature.  i am pretty sure it is a bug: you either have
stuff you don't need in the agenda, or you have a broken log mode.]

but i'm wondering if my emails are reaching the list.

>
> i like to set log mode to show everything.  i also go to
> previous dates to find out what i did.
>
> however, the skip variables can change log mode.
>
> ===
>
> consider org-agenda-skip-scheduled-if-done.  showing is
> useful for "what was doneified at an unspecified date but
> was first scheduled today or on that day".
>
> it is not intended for "what you did today or on that day".
>
> in my case, the latter is useful, but the former is not.
>
> ===
>
> if you have it set to the default of nil, and have log mode
> on, it will redundantly show a closed non-timed scheduled in
> both the timed section as a closed log mode item, and in the
> non-timed section.
>
> thus it is tempting to set it to t to remove the redundancy.
>
> ===
>
> but if you do that, YOU ARE ALSO REMOVING ITEMS FROM LOG
> MODE.  (note: untested in -Q.)
>
> assuming log mode is set to show closed tasks:
>
> - if it was UNSCHEDULED and done, it will show in log mode.
> - if it was SCHEDULED and done, it will not show in log mode.
>
> this absence might get lost.  you might notice closed tasks,
> and not notice that you turned off scheduled tasks.
>
> ===
>
> i doubt that many want to skip scheduled done tasks in log
> mode, especially when unscheduled done tasks show.
>
> imagine a user with a "memacs type mindset".  he or she
> would probably be surprised that this variable omits items
> from log mode.
>
> it seems impossible to skip without also affecting log mode.
>
> my suggested fix is a new or changed non-nil value to skip without
> changing log mode.
>
> --
> The Kafka Pandemic: 
>
> The disease DOES progress. MANY people have died from it. And ANYBODY
> can get it at any time.
>
> "You’ve really gotta quit this and get moving, because this is murder
> by neglect." ---
> .
>


-- 
The Kafka Pandemic: 

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
.

Re: [O] default value for org-capture-templates

[Tyler Smith]

On Sat, Dec 29, 2018, at 8:41 AM, Nicolas Goaziou wrote:
> "Tyler Smith"  writes:
> 
> > I can put together a patch to do this if I haven't overlooked
> > a problem this would create.
> 
> I think you can go ahead. Thank you.
> 
> Have you signed FSF papers?
> 

Not yet. I just sent the request to ass...@gnu.org.

I'll put the patch together this week.

Best,

Tyler