Re: [O] problem with org-capture in FF

[Detlef Steuer]

Am Tue, 09 May 2017 10:40:13 +0200
schrieb "Loris Bennett" :

> Detlef Steuer  writes:
> 
> > Hi!
> >
> > I use FF with Org-mode Capture
> > http://chadok.info/firefox-org-capture/ Version 0.3.0-1 signed
> >
> > My setup worked before (tm).
> >
> > Today an emacsclient window pops up for a ms and no information
> > is added to my web.org specified in my capture template.
> >
> > ...
> >   ("x" "org-protocol" entry (file "~/.pim/web.org")
> > "* TODO Review %c\n%U\n%i\n" :immediate-finish)
> > ...
> >
> > (Just copied from the org-capture homepage)
> >
> > All I can find is in my *Warnings* buffer:
> > Warning (emacs): Please update your Org Protocol handler to deal
> > with new-style links.
> >
> > In the minibuffer "No files remain to edit"
> >
> > In *Messages* 
> > Greedy org-protocol handler.  Killing client.
> > No server buffers remain to edit
> >
> > Any ideas?
> >
> > Org version from git today,
> > org-version: 9.0.6 (release_9.0.6-427-gc801ef)
> >
> > ~/GIT/org-mode> emacs --version
> > GNU Emacs 25.2.1
> >
> > Detlef  
> 
> The same set-up Works For Me (tm) with
> 
> - GNU Emacs 25.1.1
> - 9.0.6-elpaplus (org-plus-contrib-20170502)
> - Org-mode Capture 0.3.0-1 signed
> - Firefox 45.9.0

Hmm, ok, I have Firefox 52.1.0. Must be the culprit then.
Probably not an org-problem.

Thx for the information. 

Detlef

> 
> Cheers,
> 
> Loris
> 
-- 

"Wisely and slow. Those stumble that run fast."
Shakespeare -- Romeo and Juliet

Re: [O] problem with org-capture in FF

[Loris Bennett]

Detlef Steuer  writes:

> Hi!
>
> I use FF with Org-mode Capture http://chadok.info/firefox-org-capture/
> Version 0.3.0-1 signed
>
> My setup worked before (tm).
>
> Today an emacsclient window pops up for a ms and no information
> is added to my web.org specified in my capture template.
>
> ...
>   ("x" "org-protocol" entry (file "~/.pim/web.org")
> "* TODO Review %c\n%U\n%i\n" :immediate-finish)
> ...
>
> (Just copied from the org-capture homepage)
>
> All I can find is in my *Warnings* buffer:
> Warning (emacs): Please update your Org Protocol handler to deal with
> new-style links.
>
> In the minibuffer "No files remain to edit"
>
> In *Messages* 
> Greedy org-protocol handler.  Killing client.
> No server buffers remain to edit
>
> Any ideas?
>
> Org version from git today,
> org-version: 9.0.6 (release_9.0.6-427-gc801ef)
>
> ~/GIT/org-mode> emacs --version
> GNU Emacs 25.2.1
>
> Detlef

The same set-up Works For Me (tm) with

- GNU Emacs 25.1.1
- 9.0.6-elpaplus (org-plus-contrib-20170502)
- Org-mode Capture 0.3.0-1 signed
- Firefox 45.9.0

Cheers,

Loris

-- 
This signature is currently under construction.

[O] problem with org-capture in FF

[Detlef Steuer]

Hi!

I use FF with Org-mode Capture http://chadok.info/firefox-org-capture/
Version 0.3.0-1 signed

My setup worked before (tm).

Today an emacsclient window pops up for a ms and no information
is added to my web.org specified in my capture template.

...
  ("x" "org-protocol" entry (file "~/.pim/web.org")
"* TODO Review %c\n%U\n%i\n" :immediate-finish)
...

(Just copied from the org-capture homepage)

All I can find is in my *Warnings* buffer:
Warning (emacs): Please update your Org Protocol handler to deal with
new-style links.

In the minibuffer "No files remain to edit"

In *Messages* 
Greedy org-protocol handler.  Killing client.
No server buffers remain to edit

Any ideas?

Org version from git today,
org-version: 9.0.6 (release_9.0.6-427-gc801ef)

~/GIT/org-mode> emacs --version
GNU Emacs 25.2.1

Detlef

-- 

"Wisely and slow. Those stumble that run fast."
Shakespeare -- Romeo and Juliet

Re: [O] Problem with Org-capture mode

[Doyley, Marvin M.]

Thanks,
The problem is now solved
It turns out that the problem was yasnippet.
Cheers,
M
On Jan 4, 2017, at 2:30 PM, Kaushal Modi 
> wrote:

You seem to have mixed installations.

org-set-local has been deprecated for a while now.

What are your org and emacs versions?

On Wed, Jan 4, 2017 at 2:23 PM Doyley, Marvin M. 
> wrote:
Hi there,

Org capture template is not working.

I get the following message when I try to use it. Does anybody know how to fix 
this ?

Thanks
M


For information about GNU Emacs and the GNU system, type C-h C-a.
Problems while trying to load feature ‘org-mac-message’
File mode specification error: (void-function org-set-local)
Capture abort: (void-function org-set-local)







--

Kaushal Modi

Re: [O] Problem with Org-capture mode

[Doyley, Marvin M.]

Here is the backtrace
Debugger entered--Lisp error: (void-function org-set-local)
  (org-set-local (quote yas/trigger-key) [tab])
  (lambda nil (org-set-local (quote yas/trigger-key) [tab]) (define-key 
yas/keymap [tab] (quote yas/next-field-or-maybe-expand)))()
  run-hooks(change-major-mode-after-body-hook text-mode-hook outline-mode-hook 
org-mode-hook)
  apply(run-hooks (change-major-mode-after-body-hook text-mode-hook 
outline-mode-hook org-mode-hook))
  run-mode-hooks(org-mode-hook)
  org-mode()
  set-auto-mode-0(org-mode nil)
  set-auto-mode()
  normal-mode(t)
  after-find-file(nil t)
  find-file-noselect-1(# 
"~/Org-files/General/Master-todo.org" nil nil 
"~/Dropbox/Filing_Cabinet/O/Org-files/General/Master-todo.org" (31210154 
16777218))
  find-file-noselect("/Users/doyley/Org-files/General/Master-todo.org")
  org-capture-target-buffer("~/Org-files/General/Master-todo.org")
  org-capture-set-target-location()
  org-capture(nil "t")
  (lambda (template-shortcut) (org-capture nil template-shortcut))("t")
  helm-execute-selection-action-1()
  helm-execute-selection-action()
  #[0 "\311\211\211\211\305\206\n

Re: [O] Problem with Org-capture mode

[Kaushal Modi]

You seem to have mixed installations.

org-set-local has been deprecated for a while now.

What are your org and emacs versions?

On Wed, Jan 4, 2017 at 2:23 PM Doyley, Marvin M. 
wrote:

> Hi there,
>
> Org capture template is not working.
>
> I get the following message when I try to use it. Does anybody know how to
> fix this ?
>
> Thanks
> M
>
>
> For information about GNU Emacs and the GNU system, type C-h C-a.
> Problems while trying to load feature ‘org-mac-message’
> File mode specification error: (void-function org-set-local)
> Capture abort: (void-function org-set-local)
>
>
>
>
>
>
>
> --

Kaushal Modi

[O] Problem with Org-capture mode

[Doyley, Marvin M.]

Hi there,

Org capture template is not working.

I get the following message when I try to use it. Does anybody know how to fix 
this ?

Thanks
M


For information about GNU Emacs and the GNU system, type C-h C-a.
Problems while trying to load feature ‘org-mac-message’
File mode specification error: (void-function org-set-local)
Capture abort: (void-function org-set-local)









signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [O] problem with org-capture

[Eric S Fraga]

On Thursday,  3 Dec 2015 at 23:38, Nicolas Goaziou wrote:

[...]

> I pushed a commit which should fix these issues and the others mentioned
> in the thread. Thank you.

Hi Nicolas,

thank you very much for this.  The problems I was experiencing have all
gone away now!

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.2, Org release_8.3.2-363-g5c13a6

Re: [O] problem with org-capture

[Nicolas Goaziou]

Hello,

Charles Millar  writes:

> I think it is still broken in another way
>
> my template for capturing time as I work on a files -
>
> ("s" "timeslip" table-line
>  (file "/mnt/Data/ActiveFiles/EmacsFiles/timeslips.org")
>  "\| %(org-read-date)\| %^{FileName} %i\| %^{Narrative}
> %i\| %^{Time} %i\| %^{Expense} %i"
>
> Last week the prompt org-read-date would pull up the calendar first;
> now the template jumps first to FileName, then Narrative,then Time,
> then Expense, then back to org-read-date.

Well, this one is to be expected. S-exp placeholders are evaluated only
once. This currently happens at the end of the process because some
users do

  %(do-stuff "%i")

Here you want it to happen at the beginning of the process, which is not
quite compatible with the behaviour above.

I guess we could check if the S-exp contains any placeholder to decide
if it should be evaluated at the beginning or the end of the process,
but that somehow sounds cheesy.

> After C-c C-c there is anywhere 5 to 20 second delay.

I'm not sure this is related to the change. Could you use
elp-intrument-package and post the details?


Regards,

-- 
Nicolas Goaziou

Re: [O] problem with org-capture

[Eric S Fraga]

On Wednesday,  2 Dec 2015 at 22:24, Nicolas Goaziou wrote:
> Hello,
>
> Eric S Fraga  writes:
>
>> However, it only partially fixed.  The system does now prompt as it
>> should but the mini-buffer input only allows single words.  Hitting
>> space bar attempts to do completion.  I believe the input should be free
>> form?
>
> Fixed (again). Thank you.

Thanks (again :-).

Okay, this now works in that I can enter the text.  However, there seems
to be a very strange side effect: I get the error message

  Error running timer: `org-indent-initialize-agent': (error "Marker
  points into wrong buffer" #

Re: [O] problem with org-capture

[Charles Millar]

On 12/03/2015 04:02 AM, Nicolas Goaziou wrote:

Hello,

Charles Millar  writes:


I think it is still broken in another way

my template for capturing time as I work on a files -

 ("s" "timeslip" table-line
  (file "/mnt/Data/ActiveFiles/EmacsFiles/timeslips.org")
  "\| %(org-read-date)\| %^{FileName} %i\| %^{Narrative}
%i\| %^{Time} %i\| %^{Expense} %i"

Last week the prompt org-read-date would pull up the calendar first;
now the template jumps first to FileName, then Narrative,then Time,
then Expense, then back to org-read-date.

Well, this one is to be expected. S-exp placeholders are evaluated only
once. This currently happens at the end of the process because some
users do

   %(do-stuff "%i")

Here you want it to happen at the beginning of the process, which is not
quite compatible with the behaviour above.

I guess we could check if the S-exp contains any placeholder to decide
if it should be evaluated at the beginning or the end of the process,
but that somehow sounds cheesy.
OK; however, why should this change within the past few days (at least 
in my case)? I have been using this template for over three and I 
believe four years and the calendar prompt always started first, not last.

After C-c C-c there is anywhere 5 to 20 second delay.

I'm not sure this is related to the change. Could you use
elp-intrument-package and post the details?



You are right, it's not.

Charlie

Re: [O] problem with org-capture

[Matt Lundin]

Nicolas Goaziou  writes:

> Hello,
>
> Eric S Fraga  writes:
>
>> However, it only partially fixed.  The system does now prompt as it
>> should but the mini-buffer input only allows single words.  Hitting
>> space bar attempts to do completion.  I believe the input should be free
>> form?
>
> Fixed (again). Thank you.

Thanks Nicolas. One more issue. In the past, non-interactive escapes
were expanded when the capture buffer was displayed, which enabled me to
see what I had just clipped while entering the interactive data. Now
non-interactive escapes are expanded at the end of the capture process.

Take the following template:

(setq org-capture-templates
  '(("a" "Appointment" entry
 (file "~/org/inbox.org")
 "* %^{Appt}\n %^t%?\n %U\n %a\n\n %i")))

In the past, if I called this from the org-mode website with a region of
text selected, I would get a buffer that looked like this before
completing the interactive prompts:

--8<---cut here---start->8---
* 
 %^t%?
 [2015-12-03 Thu 11:02]
 [[http://orgmode.org/][Org mode for Emacs – Your Life in Plain Text]]

 Org mode is for keeping notes, maintaining TODO lists, planning
 projects, and authoring documents with a fast and effective plain-text
 system.
--8<---cut here---end--->8---

After the recent changes, the initial capture buffer looks like this:

--8<---cut here---start->8---
* 
 %^t%?
 %U
 %a

 %i
 --8<---cut here---end--->8---

Thanks,
Matt

Re: [O] problem with org-capture

[Mike McLean]

At the risk of piling on, I too am having problems with Org Capture
templates that haven't changed in a long time. The sample below used to
function like:

   1. I would call it from org-capture, select the “af” template
   2. I would get prompted for a date from file+datetree+prompt and I would
   select the date
   3. I would get prompted for the week number from the
   ~%^{prompt|%<%Y-W%V>}~ clause. This would default to the current week in
   ISO format (2015-W49). I would change it or not (usually not)
   4. The ISO week entered from that prompt would get substituted into the
   AR_DATE property in multiple places.

The two big differences with release_8.3.2-381-gb7ee96 are

   1. The substitution for %Y and %V does not happen before the prompt in
   step 3; I get a default value of [%<%Y-W%V>]
   2. Even if I manually type the ISO week string (2015-W09) it no longer
   gets substituted into the AR_DATE properties via %\1

I maintain some of my more complex capture templates in standalone files
and reference the file in org-capture-templates

(setq org-capture-templates (quote (
("a" "Templates for Agile Results")

("af" "Friday Afternoon Weekly Close /
Reflection"
 entry
 (file+datetree+prompt
"~/Documents/OrgMaster/org/Agile_Results.org")
 (file
"~/.init/emacs/org-capture-templates/friday.reflection.org_template")
 :jump-to-captured t :immediate-finish
t

The
file "~/.init/emacs/org-capture-templates/friday.reflection.org_template"
contains:

#+begin_example
  ,* Friday Reflection %^{prompt|%<%Y-W%V>}
  :PROPERTIES:
  :AR_DATE:  %\1
  :VISIBILITY: all
  :END:
  %u
  ,** Three Things Going Well
  + %?
  +
  +
  ,** Three Things to Improve
  +
  +
  +
  ,** Review Outcomes and Results Compared to the Monday Vision
 :Weekly_Win_Review:
  :PROPERTIES:
  :AR_DATE:  %\1
  :VISIBILITY: all
  :END:
  %<[%Y-%m-%d %a %H:%M]>
  - What got in my way? How might I do it differently? Review each of my
target Monday
Vision Outcomes; What did I get done or did not get done?
 +
 +
 +
  ,** Delta File: What will I change immediately or when my role or
influence changes :NOTE:Delta_File:
  %<[%Y-%m-%d %a %H:%M]>

#+end_example




On Thu, Dec 3, 2015 at 12:05 PM, Matt Lundin  wrote:

> Nicolas Goaziou  writes:
>
> > Hello,
> >
> > Eric S Fraga  writes:
> >
> >> However, it only partially fixed.  The system does now prompt as it
> >> should but the mini-buffer input only allows single words.  Hitting
> >> space bar attempts to do completion.  I believe the input should be free
> >> form?
> >
> > Fixed (again). Thank you.
>
> Thanks Nicolas. One more issue. In the past, non-interactive escapes
> were expanded when the capture buffer was displayed, which enabled me to
> see what I had just clipped while entering the interactive data. Now
> non-interactive escapes are expanded at the end of the capture process.
>
> Take the following template:
>
> (setq org-capture-templates
>   '(("a" "Appointment" entry
>  (file "~/org/inbox.org")
>  "* %^{Appt}\n %^t%?\n %U\n %a\n\n %i")))
>
> In the past, if I called this from the org-mode website with a region of
> text selected, I would get a buffer that looked like this before
> completing the interactive prompts:
>
> --8<---cut here---start->8---
> *
>  %^t%?
>  [2015-12-03 Thu 11:02]
>  [[http://orgmode.org/][Org mode for Emacs – Your Life in Plain Text]]
>
>  Org mode is for keeping notes, maintaining TODO lists, planning
>  projects, and authoring documents with a fast and effective plain-text
>  system.
> --8<---cut here---end--->8---
>
> After the recent changes, the initial capture buffer looks like this:
>
> --8<---cut here---start->8---
> *
>  %^t%?
>  %U
>  %a
>
>  %i
>  --8<---cut here---end--->8---
>
> Thanks,
> Matt
>
>

Re: [O] problem with org-capture

[Nicolas Goaziou]

Hello,

Mike McLean  writes:

> At the risk of piling on, I too am having problems with Org Capture
> templates that haven't changed in a long time. The sample below used to
> function like:
>
>1. I would call it from org-capture, select the “af” template
>2. I would get prompted for a date from file+datetree+prompt and I would
>select the date
>3. I would get prompted for the week number from the
>~%^{prompt|%<%Y-W%V>}~ clause. This would default to the current week in
>ISO format (2015-W49). I would change it or not (usually not)
>4. The ISO week entered from that prompt would get substituted into the
>AR_DATE property in multiple places.
>
> The two big differences with release_8.3.2-381-gb7ee96 are
>
>1. The substitution for %Y and %V does not happen before the prompt in
>step 3; I get a default value of [%<%Y-W%V>]
>2. Even if I manually type the ISO week string (2015-W09) it no longer
>gets substituted into the AR_DATE properties via %\1

I pushed a commit which should fix these issues and the others mentioned
in the thread. Thank you.

Let me know if something is still wrong.

Regards,

-- 
Nicolas Goaziou

Re: [O] problem with org-capture

[Charles Millar]

On 12/03/2015 05:38 PM, Nicolas Goaziou wrote:

Hello,

Mike McLean  writes:


At the risk of piling on, I too am having problems with Org Capture
templates that haven't changed in a long time. The sample below used to
function like:

1. I would call it from org-capture, select the “af” template
2. I would get prompted for a date from file+datetree+prompt and I would
select the date
3. I would get prompted for the week number from the
~%^{prompt|%<%Y-W%V>}~ clause. This would default to the current week in
ISO format (2015-W49). I would change it or not (usually not)
4. The ISO week entered from that prompt would get substituted into the
AR_DATE property in multiple places.

The two big differences with release_8.3.2-381-gb7ee96 are

1. The substitution for %Y and %V does not happen before the prompt in
step 3; I get a default value of [%<%Y-W%V>]
2. Even if I manually type the ISO week string (2015-W09) it no longer
gets substituted into the AR_DATE properties via %\1

I pushed a commit which should fix these issues and the others mentioned
in the thread. Thank you.

Let me know if something is still wrong.

Regards,


Works for me. Thank you, Nicholas.

Regards,

Charlie Millar

Re: [O] problem with org-capture

[Mike McLean]

Great

Everything seems to(*) work again; thank you.

Mike

(*) I have another small issue that I think is ~helm~ related based on the
initial backtrace, I'll do full checks (tomorrow or weekend) with -Q and
report back if I think it is Org related. Gut feeling right no: not.


On Thu, Dec 3, 2015 at 5:38 PM, Nicolas Goaziou 
wrote:

> Hello,
>
> Mike McLean  writes:
>
> > At the risk of piling on, I too am having problems with Org Capture
> > templates that haven't changed in a long time. The sample below used to
> > function like:
> >
> >1. I would call it from org-capture, select the “af” template
> >2. I would get prompted for a date from file+datetree+prompt and I
> would
> >select the date
> >3. I would get prompted for the week number from the
> >~%^{prompt|%<%Y-W%V>}~ clause. This would default to the current week
> in
> >ISO format (2015-W49). I would change it or not (usually not)
> >4. The ISO week entered from that prompt would get substituted into
> the
> >AR_DATE property in multiple places.
> >
> > The two big differences with release_8.3.2-381-gb7ee96 are
> >
> >1. The substitution for %Y and %V does not happen before the prompt in
> >step 3; I get a default value of [%<%Y-W%V>]
> >2. Even if I manually type the ISO week string (2015-W09) it no longer
> >gets substituted into the AR_DATE properties via %\1
>
> I pushed a commit which should fix these issues and the others mentioned
> in the thread. Thank you.
>
> Let me know if something is still wrong.
>
> Regards,
>
> --
> Nicolas Goaziou
>

Re: [O] problem with org-capture

[Nicolas Goaziou]

Hello,

Eric S Fraga  writes:

> However, it only partially fixed.  The system does now prompt as it
> should but the mini-buffer input only allows single words.  Hitting
> space bar attempts to do completion.  I believe the input should be free
> form?

Fixed (again). Thank you.


Regards,

-- 
Nicolas Goaziou

Re: [O] problem with org-capture

[Charles Millar]

Hi,

On 12/02/2015 04:24 PM, Nicolas Goaziou wrote:

Hello,

Eric S Fraga  writes:


However, it only partially fixed.  The system does now prompt as it
should but the mini-buffer input only allows single words.  Hitting
space bar attempts to do completion.  I believe the input should be free
form?

Fixed (again). Thank you.


Regards,


I think it is still broken in another way

my template for capturing time as I work on a files -

("s" "timeslip" table-line
 (file "/mnt/Data/ActiveFiles/EmacsFiles/timeslips.org")
 "\| %(org-read-date)\| %^{FileName} %i\| %^{Narrative} 
%i\| %^{Time} %i\| %^{Expense} %i"


Last week the prompt org-read-date would pull up the calendar first; now 
the template jumps first to FileName, then Narrative,then Time, then 
Expense, then back to org-read-date.  After C-c C-c there is anywhere 5 
to 20 second delay.


Charlie Millar

Re: [O] problem with org-capture

[Eric S Fraga]

On Tuesday,  1 Dec 2015 at 23:22, Nicolas Goaziou wrote:
> Hello,
>
> Eric S Fraga  writes:
>
>> at the risk of again raising an issue that is actually my fault :-(, I
>> am having a problem with org-capture.  I have been using the same
>> templates for yonks but, all of a sudden, my templates don't work.  For
>> instance,
>>
>> #+begin_src emacs-lisp
>>   (setq org-capture-templates
>> '(("t" "todo" entry (file+datetree "~/s/notes/tasks.org")
>>"* TODO %^{Task} %^G\nSCHEDULED: %t\n%i%?")))
>> #+end_src
>>
>> I do not get prompted for the task nor asked for tags.
>
> Fixed. Thank you.

Thanks Nicolas,

However, it only partially fixed.  The system does now prompt as it
should but the mini-buffer input only allows single words.  Hitting
space bar attempts to do completion.  I believe the input should be free
form?

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3.2-359-g6b2c38

Re: [O] problem with org-capture

[Matt Lundin]

Eric S Fraga  writes:

> Hello again,
>
> at the risk of again raising an issue that is actually my fault :-(, I
> am having a problem with org-capture.  I have been using the same
> templates for yonks but, all of a sudden, my templates don't work.  For
> instance,
>
> #+begin_src emacs-lisp
>   (setq org-capture-templates
> '(("t" "todo" entry (file+datetree "~/s/notes/tasks.org")
>"* TODO %^{Task} %^G\nSCHEDULED: %t\n%i%?")))
> #+end_src
>
> I do not get prompted for the task nor asked for tags.
>
> I do see that there have been changes recently to org-capture and a few
> emails flying by regarding recursive captures but I didn't think they
> applied to my use cases...  I could be wrong.
>
> Any pointers to what I need to change to get things working again would
> be most welcome!

I can confirm this bug. None of the prompt shortcuts work in capture
templates. For instance, the following capture template...

(setq org-capture-templates
  '(("a" "Appointment" entry
 (file "~/org/inbox.org") "* %^{Appt}\n %^t%?\n %U\n %i")))

...simply inserts the following in a buffer without any prompts or
expansion...

* %^{Appt}
 %^t
 [2015-12-01 Tue 14:51]

The problematic commit is the one having to do with recursive todos:

bd3a2cbf2f69d4de5ad7d41893bf418e91c23fb2

Best,
Matt

Re: [O] problem with org-capture

[Eric S Fraga]

On Tuesday,  1 Dec 2015 at 14:51, Matt Lundin wrote:

[...]

> I can confirm this bug. None of the prompt shortcuts work in capture
> templates. For instance, the following capture template...

Whew!  I was really worried I'd done some silly again... :-)

And I did check with emacs -Q for once!

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.2, Org release_8.3.2-355-g18f083

Re: [O] problem with org-capture

[Nicolas Goaziou]

Hello,

Eric S Fraga  writes:

> at the risk of again raising an issue that is actually my fault :-(, I
> am having a problem with org-capture.  I have been using the same
> templates for yonks but, all of a sudden, my templates don't work.  For
> instance,
>
> #+begin_src emacs-lisp
>   (setq org-capture-templates
> '(("t" "todo" entry (file+datetree "~/s/notes/tasks.org")
>"* TODO %^{Task} %^G\nSCHEDULED: %t\n%i%?")))
> #+end_src
>
> I do not get prompted for the task nor asked for tags.

Fixed. Thank you.


Regards,

-- 
Nicolas Goaziou

[O] problem with org-capture

[Eric S Fraga]

Hello again,

at the risk of again raising an issue that is actually my fault :-(, I
am having a problem with org-capture.  I have been using the same
templates for yonks but, all of a sudden, my templates don't work.  For
instance,

#+begin_src emacs-lisp
  (setq org-capture-templates
'(("t" "todo" entry (file+datetree "~/s/notes/tasks.org")
   "* TODO %^{Task} %^G\nSCHEDULED: %t\n%i%?")))
#+end_src

I do not get prompted for the task nor asked for tags.

I do see that there have been changes recently to org-capture and a few
emails flying by regarding recursive captures but I didn't think they
applied to my use cases...  I could be wrong.

Any pointers to what I need to change to get things working again would
be most welcome!

thanks,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.2, Org release_8.3.2-355-g18f083

Re: [O] Problem in org-capture-templates

[Bastien]

Hi Igor,

Igor Sosa Mayor joseleopoldo1...@gmail.com writes:

 Am Sun, Apr 28, 2013 at 10:49:01AM +0200, Bastien wrote: 
 I cannot reproduce this.  Does anyone can?

 thnaks for your answer. With 8.0.2 it still happens. How could I debug
 what is going on?

Can you reproduce the problem with a minimal configuration?  

E.g. starting with emacs -q then loading the bits of config that are
needed for reproducing this capture bug.

HTH,

-- 
 Bastien

Re: [O] Problem in org-capture-templates

[Igor Sosa Mayor]

Am Tue, May 07, 2013 at 03:13:57PM +0200, Bastien wrote:
 Can you reproduce the problem with a minimal configuration?  
 
 E.g. starting with emacs -q then loading the bits of config that are
 needed for reproducing this capture bug.

Thanks for your answer, Bastien.

Yes, you are right. If I start a minimal configuration the problem
disappears. I have to check my config which is very very very long...
But there is somewhere the problem.

-- 
:: Igor Sosa Mayor :: joseleopoldo1...@gmail.com ::
:: GnuPG: 0x1C1E2890   :: http://www.gnupg.org/  ::
:: jabberid: rogorido  ::::

Re: [O] Problem in org-capture-templates

[Bastien]

Hi Igor,

Igor Sosa Mayor joseleopoldo1...@gmail.com writes:

 i'm experiencing since some weeks a very strange bug (maybe). I have
 this simple template:

 (setq org-capture-templates
 '((e email (persönlich) entry (file+headline ~/Documents/org/privat.org 
 Emails)
 * TODO %^{Wem} schreiben
SCHEDULED: %t
   :PROPERTIES:
   :Effort:   0:02
   :END:
 %?)))

 I get asked for the pesron I want write to, but the problem is that
 I can not write a name with a blank space (say: `Barack Obama') because
 I get an error `no match'.

 This was working without problems for years. I have org 8.0.2 (but this
 happened also with the last 7.9 version). Emacs: 24.3.1.

I cannot reproduce this.  Does anyone can?

-- 
 Bastien

Re: [O] Problem in org-capture-templates

[Igor Sosa Mayor]

Hi Bastien,

Am Sun, Apr 28, 2013 at 10:49:01AM +0200, Bastien wrote: 
 I cannot reproduce this.  Does anyone can?

thnaks for your answer. With 8.0.2 it still happens. How could I debug
what is going on?

I thought maybe is ido-mode the problem, but if i disable it, it still
happens...

Many thanks in advance!


-- 
:: Igor Sosa Mayor :: joseleopoldo1...@gmail.com ::
:: GnuPG: 0x1C1E2890   :: http://www.gnupg.org/  ::
:: jabberid: rogorido  ::::

[O] Problem in org-capture-templates

[Igor Sosa Mayor]

[sorry for having send this emails several times... I made a mistake in
the subject...]

Hi,

i'm experiencing since some weeks a very strange bug (maybe). I have
this simple template:

(setq org-capture-templates
'((e email (persönlich) entry (file+headline ~/Documents/org/privat.org 
Emails)
* TODO %^{Wem} schreiben
   SCHEDULED: %t
  :PROPERTIES:
  :Effort:   0:02
  :END:
%?)))

I get asked for the pesron I want write to, but the problem is that
I can not write a name with a blank space (say: `Barack Obama') because
I get an error `no match'.

This was working without problems for years. I have org 8.0.2 (but this
happened also with the last 7.9 version). Emacs: 24.3.1.

Thanks in advance

-- 
:: Igor Sosa Mayor :: joseleopoldo1...@gmail.com ::
:: GnuPG: 0x1C1E2890   :: http://www.gnupg.org/  ::
:: jabberid: rogorido  ::::