[O] source block breaks when code looks like heading

[bruce robertson]

multi-line comments or expressions appearing to be headings break block.

* top
#+begin_src php
/*
*do not prepend a space to 'do'
*/
b = 2
*3; // do not prepend a space to '3'
#+end_src

GNU Emacs 25.1.1 (x86_64-apple-darwin13.4.0, NS appkit-1265.21 Version
10.9.5 (Build 13F1911)) of 2016-09-20
Org mode version 9.0.9 (release_9.0.9-736-gf1b2a9 @
/Users/brucer42/git/org-mode/lisp/)

Re: [O] ox-taskjuggler on MELPA useful despite org-plus-contrib

[Simon Guest]

Well, almost as soon as I started on that, I see some issues around mixing
old/new org-mode functionality, so this seems like a not-so-good idea after
all.

In particular, ox-taskjuggler is using the very new org-duration library.

I'll think of another approach, not using MELPA.  At least until the
underlying problem with org-plus-contrib is resolved.

cheers,
Simon

On 8 August 2017 at 10:57, Simon Guest  wrote:

> Well, I see now that org-plus-contrib has its issues.  Specifically I am
> hitting the same issue as reported here, which I see has been a problem for
> nearly 2 years.
> https://github.com/purcell/emacs.d/issues/297
>
> Therefore, unless I hear another idea or an objection here, I intend to
> proceed with getting ox-taskjuggler in isolation onto MELPA, unless its
> author and/or maintainer would prefer not.
>
> cheers,
> Simon
>
>>
>> On 5/08/2017 10:51 PM, "Adam Porter"  wrote:
>>
>>>
>>> Actually all you need to do is install the org-plus-contrib package from
>>> ELPA, which includes contrib.  Then you'll get the latest release of
>>> Org, too.  ;)
>>>
>>>
>>>
>

[O] ox-taskjuggler on MELPA useful despite org-plus-contrib

[Simon Guest]

Well, I see now that org-plus-contrib has its issues.  Specifically I am
hitting the same issue as reported here, which I see has been a problem for
nearly 2 years.
https://github.com/purcell/emacs.d/issues/297

Therefore, unless I hear another idea or an objection here, I intend to
proceed with getting ox-taskjuggler in isolation onto MELPA, unless its
author and/or maintainer would prefer not.

cheers,
Simon

>
> On 5/08/2017 10:51 PM, "Adam Porter"  wrote:
>
>>
>> Actually all you need to do is install the org-plus-contrib package from
>> ELPA, which includes contrib.  Then you'll get the latest release of
>> Org, too.  ;)
>>
>>
>>

Re: [O] [PATCH] Add option to automatically align tags in agenda view

[Kyle Meyer]

Adam Porter  writes:

> Ok, I've updated the patch.

Thanks.  A few more comments.

> (org-agenda-align-tags): Handle automatic alignment
> (org-agenda-tags-column): Add 'auto setting

You're missing the file name in the entries above.  Also, the entries
should end in a period.

> -(defcustom org-agenda-tags-column -80
> +(defcustom org-agenda-tags-column 'auto
>"Shift tags in agenda items to this column.
> -If this number is positive, it specifies the column.  If it is negative,
> -it means that the tags should be flushright to that column.  For example,
> --80 works well for a normal 80 character screen."
> +If set to `auto', tags will be automatically aligned to the right
> +edge of the window.
> +
> +If set to a positive number, tags will be left-aligned to that
> +column.  If set to a negative number, tags will be right-aligned
> +to that column.  For example, -80 works well for a normal 80
> +character screen."
>:group 'org-agenda-line-format
> -  :type 'integer)
> +  :type '(choice
> +   (const :tag "Automatically align to right edge of window" auto)
> +   (integer :tag "Specific column" -80)))

Since you're changing the default value, shouldn't you add appropriate
values for the :version and :package-version keywords?

It'd be good to mention this change in ORG-NEWS as well.

-- 
Kyle

Re: [O] clock start time is gone

[Samuel Wales]

On 8/7/17, Nicolas Goaziou  wrote:
> I'm not sure about the steps required to reproduce your issue. What do
> you do on the same mwe? Clock in
>
>   "* clock in here, then sort below, then try to clock out here"
>
> then sort at
>
>   "*** sort here by alpha"
>
> then clock out?

yes.

-- 
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] [PATCH] org.el: Allow tags without keys in customization

[Nicolas Goaziou]

Hello,

Allen Li  writes:

> * lisp/org.el (org-tag-alist, org-tag-persistent-alist):
> Add non-keyed tag type.

Applied. Thank you.

Regards,

-- 
Nicolas Goaziou0x80A93738

Re: [O] clock start time is gone

[Nicolas Goaziou]

Hello,

Samuel Wales  writes:

> i seem to get another bug, no active clock, on the same mwe:
>
> :LOGBOOK:
> CLOCK:
> :END:
>
> if i use -Q with these settings:
>
> (setq org-log-into-drawer t)
> (setq org-clock-into-drawer t)
> (setq org-clock-mode-line-total 'today)
> (setq org-clock-display-default-range 'untilnow)
> (setq org-clock-in-resume t)

I'm not sure about the steps required to reproduce your issue. What do
you do on the same mwe? Clock in

  "* clock in here, then sort below, then try to clock out here"

then sort at

  "*** sort here by alpha"

then clock out?


Regards,

-- 
Nicolas Goaziou

Re: [O] clock start time is gone

[Samuel Wales]

On 8/7/17, Nicolas Goaziou  wrote:
> Fixed. Thank you.

thank you!

i seem to get another bug, no active clock, on the same mwe:

:LOGBOOK:
CLOCK:
:END:

if i use -Q with these settings:

(setq org-log-into-drawer t)
(setq org-clock-into-drawer t)
(setq org-clock-mode-line-total 'today)
(setq org-clock-display-default-range 'untilnow)
(setq org-clock-in-resume t)


samuel

-- 
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] [PATCH] Add option to automatically align tags in agenda view

[Adam Porter]

Kyle Meyer  writes:

> ... with just one case and a fallthrough, I'd prefer you test with eq
> rather than using pcase.

Hi Kyle,

Ok, I've updated the patch.

Thanks,
Adam
>From 99a61e09d5267ddaa84e8f93fbab161144aea011 Mon Sep 17 00:00:00 2001
From: Adam Porter 
Date: Mon, 7 Aug 2017 08:50:26 -0500
Subject: [PATCH] org-agenda.el: Add option to automatically align tags in
 agenda

(org-agenda-align-tags): Handle automatic alignment
(org-agenda-tags-column): Add 'auto setting

TINYCHANGE
---
 lisp/org-agenda.el | 22 --
 1 file changed, 16 insertions(+), 6 deletions(-)

diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index c8097de..76282d4 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -1886,13 +1886,19 @@ When this is the symbol `prefix', only remove tags when
 (defvaralias 'org-agenda-remove-tags-when-in-prefix
   'org-agenda-remove-tags)
 
-(defcustom org-agenda-tags-column -80
+(defcustom org-agenda-tags-column 'auto
   "Shift tags in agenda items to this column.
-If this number is positive, it specifies the column.  If it is negative,
-it means that the tags should be flushright to that column.  For example,
--80 works well for a normal 80 character screen."
+If set to `auto', tags will be automatically aligned to the right
+edge of the window.
+
+If set to a positive number, tags will be left-aligned to that
+column.  If set to a negative number, tags will be right-aligned
+to that column.  For example, -80 works well for a normal 80
+character screen."
   :group 'org-agenda-line-format
-  :type 'integer)
+  :type '(choice
+	  (const :tag "Automatically align to right edge of window" auto)
+	  (integer :tag "Specific column" -80)))
 
 (defvaralias 'org-agenda-align-tags-to-column 'org-agenda-tags-column)
 
@@ -8959,7 +8965,11 @@ If FORCE-TAGS is non nil, the car of it returns the new tags."
 
 (defun org-agenda-align-tags (&optional line)
   "Align all tags in agenda items to `org-agenda-tags-column'."
-  (let ((inhibit-read-only t) l c)
+  (let ((inhibit-read-only t)
+	(org-agenda-tags-column (if (eq 'auto org-agenda-tags-column)
+(- (window-text-width))
+  org-agenda-tags-column))
+	l c)
 (save-excursion
   (goto-char (if line (point-at-bol) (point-min)))
   (while (re-search-forward "\\([ \t]+\\)\\(:[[:alnum:]_@#%:]+:\\)[ \t]*$"
-- 
2.7.4

Re: [O] [PATCH] org.el: Allow tags without keys in customization

[Allen Li]

* lisp/org.el (org-tag-alist, org-tag-persistent-alist):
Add non-keyed tag type.
---
 lisp/org.el | 10 +++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/lisp/org.el b/lisp/org.el
index 4bb2345a3..32c337601 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -3574,8 +3574,10 @@ See also `org-tag-persistent-alist' to sidestep
this behavior."
   :group 'org-tags
   :type '(repeat
   (choice
-   (cons   (string:tag "Tag name")
-   (character :tag "Access char"))
+   (cons :tag "Tag with key"
+ (string:tag "Tag name")
+ (character :tag "Access char"))
+   (list :tag "Tag" (string :tag "Tag name"))
(const :tag "Start radio group" (:startgroup))
(const :tag "Start tag group, non distinct" (:startgrouptag))
(const :tag "Group tags delimiter" (:grouptags))
@@ -3607,8 +3609,10 @@ on a per-file basis, insert anywhere in the file:
   :group 'org-tags
   :type '(repeat
   (choice
-   (cons (string:tag "Tag name")
+   (cons :tag "Tag with key"
+ (string:tag "Tag name")
  (character :tag "Access char"))
+   (list :tag "Tag" (string :tag "Tag name"))
(const :tag "Start radio group" (:startgroup))
(const :tag "Start tag group, non distinct" (:startgrouptag))
(const :tag "Group tags delimiter" (:grouptags))
-- 
2.14.0.rc1.383.gd1ce394fe2-goog

Re: [O] [PATCH] Add option to automatically align tags in agenda view

[Kyle Meyer]

Adam Porter  writes:

[...]

> + (org-agenda-tags-column (pcase org-agenda-tags-column
> +   ('auto (- (window-text-width)))

I believe that `auto is needed instead of 'auto because the latter will
fail with Emacs versions earlier than Emacs 25.  Though ...

> +   (otherwise org-agenda-tags-column)))

... with just one case and a fallthrough, I'd prefer you test with eq
rather than using pcase.

-- 
Kyle

[O] [PATCH] Add option to automatically align tags in agenda view

[Adam Porter]

Hi Nicolas,

Here is a patch to optionally automatically align tags in the agenda
view to the right edge of the window.  I don't yet have the CA done, but
I think this qualifies as a tinychange.

Thanks,
Adam

>From 8cd0a4035ddb8fcd90d6011c9fd529526472b379 Mon Sep 17 00:00:00 2001
From: Adam Porter 
Date: Mon, 7 Aug 2017 08:50:26 -0500
Subject: [PATCH] org-agenda.el: Add option to automatically align tags in
 agenda

(org-agenda-align-tags): Handle automatic alignment
(org-agenda-tags-column): Add 'auto setting

TINYCHANGE
---
 lisp/org-agenda.el | 22 --
 1 file changed, 16 insertions(+), 6 deletions(-)

diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index c8097de..52cbea0 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -1886,13 +1886,19 @@ When this is the symbol `prefix', only remove tags when
 (defvaralias 'org-agenda-remove-tags-when-in-prefix
   'org-agenda-remove-tags)
 
-(defcustom org-agenda-tags-column -80
+(defcustom org-agenda-tags-column 'auto
   "Shift tags in agenda items to this column.
-If this number is positive, it specifies the column.  If it is negative,
-it means that the tags should be flushright to that column.  For example,
--80 works well for a normal 80 character screen."
+If set to `auto', tags will be automatically aligned to the right
+edge of the window.
+
+If set to a positive number, tags will be left-aligned to that
+column.  If set to a negative number, tags will be right-aligned
+to that column.  For example, -80 works well for a normal 80
+character screen."
   :group 'org-agenda-line-format
-  :type 'integer)
+  :type '(choice
+	  (const :tag "Automatically align to right edge of window" auto)
+	  (integer :tag "Specific column" -80)))
 
 (defvaralias 'org-agenda-align-tags-to-column 'org-agenda-tags-column)
 
@@ -8959,7 +8965,11 @@ If FORCE-TAGS is non nil, the car of it returns the new tags."
 
 (defun org-agenda-align-tags (&optional line)
   "Align all tags in agenda items to `org-agenda-tags-column'."
-  (let ((inhibit-read-only t) l c)
+  (let ((inhibit-read-only t)
+	(org-agenda-tags-column (pcase org-agenda-tags-column
+  ('auto (- (window-text-width)))
+  (otherwise org-agenda-tags-column)))
+	l c)
 (save-excursion
   (goto-char (if line (point-at-bol) (point-min)))
   (while (re-search-forward "\\([ \t]+\\)\\(:[[:alnum:]_@#%:]+:\\)[ \t]*$"
-- 
2.7.4

Re: [O] Change in appearance of org-todo-keywords

[Colin Baxter]

Dear Josh,
> "Josh" == Josh Moller-Mara  writes:

Josh> Nicolas Goaziou  writes:
>> Hello,
>> 
>> Colin Baxter  writes:
>> 
>>> Yes, you are correct. I can confirm that switching off
>>> org-todo-state-tags-triggers removes the insertion of colons for
>>> me too.
>> 
>> Fixed. Thank you.
>> 

Josh> Hello,

Josh> ~org-toggle-tag~ now seems to delete currently set tags for a
Josh> heading. It seems that calling ~(match-string 1)~ after
Josh> ~(replace-match "")~ makes the former return an empty string,
Josh> so the ~current~ tags get set as an empty string. It also
Josh> still seems to set a blank tag ("::") if there was a tag set
Josh> previously.

Ah yes, I spoke too soon. I am now seeing what you report.

Sorry Nicolas, It isn't fixed completely.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

Re: [O] Change in appearance of org-todo-keywords

[Colin Baxter]

Dear Nicolas,

> "Nicolas" == Nicolas Goaziou  writes:

Nicolas> Hello, Colin Baxter  writes:

>> Yes, you are correct. I can confirm that switching off
>> org-todo-state-tags-triggers removes the insertion of colons for
>> me too.

Nicolas> Fixed. Thank you.

Nicolas> Regards,

Nicolas> -- Nicolas Goaziou


Thank you. I can confirm that my org-todo-keywords are now appearing as
normal.

Best wishes,

Colin.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

Re: [O] Slow speed of week and month views

[Nicolas Goaziou]

Hello,

Karl Voit  writes:

> Results at the end of this posting.

Thank you.

I assume you have around 17 agenda files, use a single day view and have
much more SCHEDULED than DEADLINE? Is it right?

> I may take some time to come up with a minimum config and my agenda
> files.

I suggest to use

  M-: (org-agenda nil "a")

as a first step.

> However, in case this is much faster compared to my current
> situation, this does not help me with my issues and just shows that
> Org itself does not have urgent performance issues, right?

No worries. It will still be excruciatingly slow.

Regards,

-- 
Nicolas Goaziou

Re: [O] Announcing Worg (Web-Org)

[Nicolas Goaziou]

Hello,

Josh Moller-Mara  writes:

> ~org-toggle-tag~ now seems to delete currently set tags for a heading. It
> seems that calling ~(match-string 1)~ after ~(replace-match "")~ makes
> the former return an empty string, so the ~current~ tags get set as an
> empty string. It also still seems to set a blank tag ("::") if there was
> a tag set previously.

Indeed. Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] Change in appearance of org-todo-keywords

[Josh Moller-Mara]

Nicolas Goaziou  writes:
> Hello,
>
> Colin Baxter  writes:
>
>> Yes, you are correct. I can confirm that switching off
>> org-todo-state-tags-triggers removes the insertion of colons for me
>> too.
>
> Fixed. Thank you.
>

Hello,

~org-toggle-tag~ now seems to delete currently set tags for a heading. It
seems that calling ~(match-string 1)~ after ~(replace-match "")~ makes
the former return an empty string, so the ~current~ tags get set as an
empty string. It also still seems to set a blank tag ("::") if there was
a tag set previously.

Best,

Josh

Re: [O] clock start time is gone

[Nicolas Goaziou]

Hello,

Samuel Wales  writes:

> this mce produces "clock start time is gone" bug in emacs -Q.  emacs
> 24, org maint.
>
> ===
> * b
> * clock in here, then sort below, then try to clock out here
> *** SOMEWHAT b
> *** c
> *** c
> *** c
> *** c
> *** sort here by alpha
> * asdfasd
> * asdfasd
> * asdfasd
> * asdfasd
> * asdfasd
> *** c
> *** c
> *** c
> *** FACT d
> * d
> ===

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] [PATCH] ob-vala.el: Add Vala support to Babel

[Nicolas Goaziou]

Hello,

Christian Garbs  writes:

> I fear that I am the only one who will ever run the vala tests ;-)
>
> - Are there any build hosts that automatically run the tests with all
>   languages enabled?

I don't think so.

> - Or could the BTEST_OB_LANGUAGES default in mk/default.mk be expanded
>   to include vala?  (99% of the users will simply skip the vala test
>   because they don't have the compiler binary, so it should have no
>   ill effacts)

Done.

Regards,

-- 
Nicolas Goaziou

Re: [O] Add-Easy-Template-for-COMMENT-C to org.el

[Nicolas Goaziou]

Hello,

Grant Rettke  writes:

> Attached is a patch to an Easy Template binding `C' for `COMMENT'.

Thank you. Would you mind also adding an entry in ORG-NEWS about it?

> The tests had the same 1 failure before and after I made the change
> "1 unexpected results:
>FAILED  test-org/refile-get-targets"

FWIW, I do not see the same. Have you set
`org-refile-target-verify-function' or some other refile-related
variable that would be different from `org-refile-use-outline-path'?

Regards,

-- 
Nicolas Goaziou

Re: [O] [PATCH v3] ob-vala.el: Add Vala support to Babel

[Nicolas Goaziou]

Hello,

Christian Garbs  writes:

> * lisp/ob-vala.el: Add support for the Vala language to Babel.
>
> * testing/lisp/test-ob-vala.el: Add tests for ob-vala.el.
>
> * doc/org.texi (Working with source code): Add Vala to the list of
>   supported languages.

Applied. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] Change in appearance of org-todo-keywords

[Nicolas Goaziou]

Hello,

Colin Baxter  writes:

> Yes, you are correct. I can confirm that switching off
> org-todo-state-tags-triggers removes the insertion of colons for me
> too.

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] Commit "org-agenda: Support for dimming..." breaks agenda display

[Yuri Lensky]

Hi,

I have a attached a patch to fix this bug. As can be seen from the patch,
the problem was improperly balanced parenthesis in
`org-agenda--mark-blocked-entry' which caused the function to return 'nil
unless the entry passed to it had the todo-state text property, whereas the
proper behavior is to always return the entry in some form.

Apologies for carelessness and introducing the bug,

YL

On Sun, Aug 6, 2017 at 3:55 AM, Nicolas Goaziou 
wrote:

> Hello,
>
> Oleh Krehel  writes:
>
> > I updated Org recently and noticed that the agenda display looks very
> > broken, especially in `org-agenda-log-mode'.
> >
> > I did a bisect; reverting commit
> > 912a385518bcf2e320cc161d573ad329111de6c7 fixes it.
> > Anyone else have this problem?
>
> Confirmed. See also
> .
>
> I'm Cc'ing Yuri about it.
>
> Regards,
>
> --
> Nicolas Goaziou
>


0001-lisp-org-agenda.el-Properly-return-all-entries-from-.patch
Description: Binary data

Re: [O] Change in appearance of org-todo-keywords

[Malcolm Purvis]

> "Josh" == Josh Moller-Mara  writes:

Josh> From what I can tell, doing something like (org-toggle-tag
Josh> "sometag" 'off) produces these double colons. It seems to have to
Josh> do with the way that org-split-string no longer returns nil, but
Josh> returns ("").

I'm also seeing this problem and I have org-todo-state-tags-triggers
set.

A git bisect points the finger at this commit, which also agrees your
observations about org-split-string.

commit f776e65373fa135fffb51e201698823fbfb3865b (refs/bisect/bad)
Author: Nicolas Goaziou 
Date:   Thu Jul 27 13:39:52 2017 +0200

Move `org-split-string' to "org-macs.el"

* lisp/org.el (org-split-string): Move the function...
* lisp/org-macs.el (org-split-string): ... here.  Also clarify
  docstring with regards to `split-string'.

Malcolm

-- 
   Malcolm Purvis 

Re: [O] Slow usage of capture templates

[Johan Ekh]

Thanks Fabrice!
I will continue to evaluate the WSL as I now have it installed and it seems
to work. I think my strategy will be to try both the native windows version
and the Ubuntu version of my key applications and just see which one works
best for me. I installed XMing for X server and it seems to work well.

BR / Johan

On Mon, Aug 7, 2017 at 10:00 AM, Fabrice Popineau <
fabrice.popin...@supelec.fr> wrote:

>
>
> 2017-08-03 0:12 GMT+02:00 Tim Cross :
>
>> Probably no real help, but win10 is (or soon will be) bundling in bash
>> shell, which may address many of the reasons to use Cygwin. From posts
>> I've seen on a number of lists, I would not be surprised to see cygwin
>> slowly decline into obscurity. I see little interest in the emacs devel
>> list for cygwin since the native windows version has matured (and it has
>> been suggested, is the largest emacs user base).
>>
>> I am a Windows user (very long time) and Cygwin has never been an option
> to me.
> Native Emacs works pretty well under Windows.
> There is only one drawback: it is slow (slower than linux) at running
> external processes and some emacs packages do that pretty heavily
> (ivy/counsel, flycheck).
> I have seen reports of slower startup times with the native Windows emacs
> than with Linux, however I have not
> been able to reproduce them (for example using helm default config or
> spacemacs config).
>
> Depending on wheter you use a 32 bits emacs or a 64 bits emacs, you may
> want to add
> 32 bits Gnu utilities (https://sourceforge.net/projects/ezwinports/files/)
> or 64 bits Gnu utilities (http://www.msys2.org/, provides a much better
> environment than Cygwin in my opinion)
>
> Or you may want to try the new WSL (Windows Subsystem for Linux, as
> described by Tim)
> which provides a full Ubuntu distribution without the penalty for running
> external processes,
> and without the penalty of running a VM.
> WSL is pretty impressive and emacs works pretty well once you get a good X
> server (like MobaXTerm).
>
> Fabrice
>

Re: [O] Commit "org-agenda: Support for dimming..." breaks agenda display

[Nicolas Goaziou]

Hello,

Yuri Lensky  writes:

> I have a attached a patch to fix this bug. As can be seen from the patch,
> the problem was improperly balanced parenthesis in
> `org-agenda--mark-blocked-entry' which caused the function to return 'nil
> unless the entry passed to it had the todo-state text property, whereas the
> proper behavior is to always return the entry in some form.
>
> Apologies for carelessness and introducing the bug,

No worries. Thank you for the quick fix!

Applied.


Regards,

-- 
Nicolas Goaziou0x80A93738

Re: [O] Change in appearance of org-todo-keywords

[Colin Baxter]

Dear Josh,
> "Josh" == Josh Moller-Mara  writes:

Josh> Colin Baxter  writes:
>> As of today, TODO now appears with three sets of un-requested
>> double colons after it, as in TODO :: :: ::
>> 
>> The behaviour doesn't occur with emacs -q, so the cause is
>> presumably in my ~/.emacs. I can't work out what's wrong with my
>> org-todo-sequence, which is:
>> 
>> (setq org-todo-keywords (quote((sequence "TODO(t)" "STARTED(s)"
>> "NEXT(n@/!)" "WAITING(w@/!)"  "HOLD(h@/!)" "CANCELLED(c@/!)"
>> "PHONE(p)" "BREAK(b)" "MEETING(m)" "DONE(d@/!)"  

Josh> This is happening with me too. But I suspect it has more to do
Josh> with org-todo-state-tags-triggers being set. I don't get the
Josh> double colons if I don't set org-todo-state-tags-triggers.

Josh> From what I can tell, doing something like (org-toggle-tag
Josh> "sometag" 'off) produces these double colons. It seems to have
Josh> to do with the way that org-split-string no longer returns
Josh> nil, but returns ("").

Josh> Best, Josh

Yes, you are correct. I can confirm that switching off
org-todo-state-tags-triggers removes the insertion of colons for me too.

Thank you.

Best wishes,

Colin.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

Re: [O] Slow usage of capture templates

[Fabrice Popineau]

2017-08-03 0:12 GMT+02:00 Tim Cross :

> Probably no real help, but win10 is (or soon will be) bundling in bash
> shell, which may address many of the reasons to use Cygwin. From posts
> I've seen on a number of lists, I would not be surprised to see cygwin
> slowly decline into obscurity. I see little interest in the emacs devel
> list for cygwin since the native windows version has matured (and it has
> been suggested, is the largest emacs user base).
>
> I am a Windows user (very long time) and Cygwin has never been an option
to me.
Native Emacs works pretty well under Windows.
There is only one drawback: it is slow (slower than linux) at running
external processes and some emacs packages do that pretty heavily
(ivy/counsel, flycheck).
I have seen reports of slower startup times with the native Windows emacs
than with Linux, however I have not
been able to reproduce them (for example using helm default config or
spacemacs config).

Depending on wheter you use a 32 bits emacs or a 64 bits emacs, you may
want to add
32 bits Gnu utilities (https://sourceforge.net/projects/ezwinports/files/)
or 64 bits Gnu utilities (http://www.msys2.org/, provides a much better
environment than Cygwin in my opinion)

Or you may want to try the new WSL (Windows Subsystem for Linux, as
described by Tim)
which provides a full Ubuntu distribution without the penalty for running
external processes,
and without the penalty of running a VM.
WSL is pretty impressive and emacs works pretty well once you get a good X
server (like MobaXTerm).

Fabrice

Re: [O] Slow usage of capture templates

[Johan Ekh]

Thanks Tim! I didn't know about this. Ive installed it and it seems to work
very nice! I will continue to test it and maybe scrap both vmware (been
using for 10+ years) and cygwin. Thanks alot!

Johan

On Thu, Aug 3, 2017 at 12:12 AM, Tim Cross  wrote:

>
> Probably no real help, but win10 is (or soon will be) bundling in bash
> shell, which may address many of the reasons to use Cygwin. From posts
> I've seen on a number of lists, I would not be surprised to see cygwin
> slowly decline into obscurity. I see little interest in the emacs devel
> list for cygwin since the native windows version has matured (and it has
> been suggested, is the largest emacs user base).
>
> Having bash, a native emacs and even a 'better' system shell in
> powershell (better than bat scripts and VB that is), at some point, you
> will likely have to switch and I can say, it is much less distasteful
> than it was (I've been using Linux since 1993 and Emacs since 97 and am
> also forced to run windows at work).
>
> Alternatively, do what I actually do - run vmware and Linux as a
> virtual - technically, I'm running the work SOE and within policy! When
> I absolutely have to do things in windows, I use native Emacs and a
> small amount of powershell, but plan to use the bash shell once I find
> time to sort it all out.
>
> Tim
>
> Johan Ekh writes:
>
> > Thanks Adam
> >
> > I've tried the native windows version and it does not have this problem.
> > But I'm an old school Linux user that is forced to use windows at work.
> > I've managed to set up Cygwin and it works quite well, in fact I think
> > Emacs is working very well except for the issue in this post. Not slow.
> > Thanks anyway. / Johan
> >
> > On Wed, Aug 2, 2017 at 12:55 PM, Adam Porter  wrote:
> >
> >> This isn't much help, but the best suggestion I have is to try the
> >> non-Cygwin, native Windows build.  I use the Cygwin build myself, but it
> >> is inherently slow compared to Linux builds for some reason.  It takes
> >> probably 10-20 times as long to startup, and everything I do it in it is
> >> slow compared to in Linux.  Maybe the native Windows build will perform
> >> better.
> >>
> >>
> >>
>
>
> --
> Tim Cross
>