Re: [O] Bug: Habits will not correctly reset timestamp [8.3.2 (release_8.3.2-570-gc17fcc @ /home/swflint/.emacs.d/org-mode/lisp/)]

[Samuel W. Flint]

:: Nicolas Goaziou writes:

NG> Hello, swfl...@flintfam.org (Samuel W. Flint) writes:

>> See my previous bug report.  This still happens.
>>
>> If I have a heading like so:
>>
>> * TODO Something SCHEDULED: <2016-01-17 Sun .+1w/2w> :PROPERTIES:
>> :STYLE: habit :END:
>>
>> And execute C-c C-t d on the heading, the following appears:
>>
>> * TODO Something :PROPERTIES: :STYLE: habit :END:
>>
>> This is incorrect behavior, and I'm unable to use org-habits
>> correctly.

NG> I cannot reproduce it. With -Q, I get

NG>   * TODO Something SCHEDULED: <2016-02-04 jeu. .+1w/2w> :PROPERTIES:
NG> :STYLE: habit :LAST_REPEAT: [2016-01-28 jeu. 09:03] :END: - State
NG> "DONE" from "TODO" [2016-01-28 jeu. 09:03]

With -Q, I still have the same problem.  It is not a top level heading,
but even as a top level heading, this doesn't happen.  The SCHEDULED
line is removed, rather than updated.

Thanks,

Sam

NG> Regards,

NG> -- Nicolas Goaziou

-- 
Samuel W. Flint
4096R/266596F4
  (9477 D23E 389E 40C5 2F10  DE19 68E5 318E 2665 96F4)
(λs.s s) λs.s s


signature.asc
Description: PGP signature

Re: [O] [PATCH] org-latex-compile timestamp checks

[Anthony Cowley]

Rasmus writes:

> Nicolas Goaziou  writes:
>
>> Hello,
>>
>> Rasmus  writes:
>>
>>> Thanks!  I have added a TODO to my agenda regarding checking other
>>> backends, but I'd not hold grudges against anyone who beats me to it.
>>
>> I took care of ox-groff, ox-man and ox-texinfo.
>
> Thanks.
>
>> I let you improve zip handling in ox-odt, if you want to.
>
> OK.  I'll be traveling this weekend so I won't have time then.  Though it
> should be quick now that I can look at yours and Anthony’s code.
>
> Rasmus

Thank you both for following up on this! I had grep'ed the tree for other time 
comparisons and not seen any, but didn't read closely enough to see the 
reliance on file existence checks in the other back-ends.

Anthony

Re: [O] links in headlines and org-bbdb-anniversaries

[Kyle Meyer]

Hello,

George McNinch  writes:

> Hi--
>
> I use org via ELPA. This week, the packages
>
>  org-20160118
>  org-plus-contrib-20160118
>
> were replaced by
>
>  org-20160125
>  org-plus-contrib-20160125
>
> After update, org began complaining about links in the headlines
> which appear in my *Agenda*.
>
> More precisely, this was reported:
>
>> org-agenda-finalize: Wrong type argument: listp, org-link

I believe this is the same issue as
http://thread.gmane.org/gmane.emacs.orgmode/104539.

It's been fixed and will be available in the next ELPA build.

-- 
Kyle

Re: [O] Orgmode testsuite

[Andrej Depperschmidt]

The minimal example are the two tables in an org-file. When I try to
move in those tables using TAB it is working okay in the first but not
in the second. Note however that it is working as expected with emacs -Q
and manually loading org.

There seems to be something in my configuration that needs to be
adjusted to the last changes in org-mode. It stopped working a few days
ago without any changes of my config. Any idea what to look for?


| col1 | col2 |
|--+--|
| a11  | a12  |
| a21  | a22  |


| col1   | col2   |
|+|
| http://www.url1.de | http://www.url2.de |



Nicolas Goaziou  writes:

> Hello,
>
> Andrej Depperschmidt  writes:
>
>> The following error occurs
>>
>> font-lock-fontify-keywords-region: Wrong type argument: listp,
>> org-table
>
> It looks like the same problem.
>
>> I checked with the latest version of org from git.
>
> Odd. Please make sure you are really using development version. If the
> problem persists, could you provide an ECM?
>
> Regards,

Re: [O] Bug: Export breaks on documents with title [8.3.3 (8.3.3-26-ge92a06-elpaplus @ /Users/leafac/.emacs.d/elpa/org-plus-contrib-20160125/)]

[Achim Gratz]

Leandro Facchinetti writes:
> I was able to figure out the issue: my versions of the packages `org'
> and `org-plus-contrib' were not matching. Updating both solved the
> issue.

In fact you should only have one or the other package installed, not
both.  I some other package tries to pull in org while you want to have
org-plus-contrib, then you need to drop a dummy org package so that ELPA
doesn't pull in a second installation.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [O] links in headlines and org-bbdb-anniversaries

[George McNinch]

Kyle> I believe this is the same issue as
Kyle> http://thread.gmane.org/gmane.emacs.orgmode/104539.

Kyle> It's been fixed and will be available in the next ELPA build.

Whoops; thanks -- I missed that.

-gm


-- 
   =---=   George McNinch 
   =---=   http://gmcninch.math.tufts.edu 

[O] Super indent when editing R blocks and using a # comment

[John Hendy]

Find attached a screenshot of the behavior I'm experiencing with this
minimal config and =emacs -Q=.

#+begin_src min-config

;; set load paths
;; set load dirs and global config options
(add-to-list 'load-path "~/.elisp/org.git/lisp/")
(add-to-list 'load-path "~/.elisp/org.git/contrib/lisp")
(add-to-list 'load-path "~/.elisp/ess/lisp/")

(require 'ess-site)

;; setup babel languages
(org-babel-do-load-languages
 'org-babel-load-languages
 '((R . t)))

#+end_src

As shown in the shot:
- create a .org file, insert a #+begin/end_src R block
- edit with =C-c '=
- start a line with a comment char (#)
- press RET
- it gets indented halfway across the page

Inside a function, it seems to use a default of four spaces (the
position of =return(i^2)=), so I'm not sure why a comment triggers
such a massive indent. I end up having to delete the preceding spaces
or be super careful about having a newline already inserted so that I
can arrow down instead of pressing RET at the end of a comment line.


Thanks for any insights!
John

[O] searching for links [8.3.3 (8.3.3-17-gce80a0-elpaplus @ c:/USR/FJM/APP/.emacs.d/elpa/org-20160118/)]

[Francis J. Monari, Esquire]

To: emacs-orgmode@gnu.org
Subject: searching for links [8.3.3 (8.3.3-17-gce80a0-elpaplus @
c:/USR/FJM/APP/.emacs.d/elpa/org-20160118/)]
From: monarif...@verizon.net (F. J. Monari)
--text follows this line--

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.


Due to file relocation on the server, I have a number of broken links in
an org document.  (problem: broken links.)

How can I / Is it possible to search and replace on links?
(expectation: I would like to use search and replace to fix the links.)

I have tried search and replace, but emacs advises me that links have
been filtered out.  (issue: emacs reports that results from the search
are filtered-out.)

The answer might be a "works as expected".  I would like to remain
within the org framework (but using standard search and replace) and
accomplish this task.

(I thought about forcing the files into a different mode, but I do not
want to risk the org file structure.)

Emacs  : GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Package: Org-mode version 8.3.3 (8.3.3-17-gce80a0-elpaplus @
c:/USR/FJM/APP/.emacs.d/elpa/org-20160118/)

-- 
Francis J. Monari, Esquire
McKernan, McKernan & Godino
113 North Sixth Street
Camden, New Jersey 08102-1269
856-964-7759 ext. 19 (voice)
856-964-9620 (fax)
francismon...@mckernangodino.com ("main", "primary")
off...@mckernangodino.com ("office")

ATTENTION: This e-mail and the materials accompanying it convey and
contain privileged and confidential information belonging to the sender
which is legally privileged.  The transmittal sheet, the materials, and
the information they contain are intended only for the use of the
individual(s) or entity(ies) named above.  If you are not the intended
recipient, you are hereby notified that any disclosure, copying,
distribution, or any reliance on the e-mail, the materials accompanying
it, or the information they contain is strictly prohibited, and that
review by any individual other than the intended recipient shall not
constitute waiver of the attorney/client privilege.  If you have
received the materials in error, please immediately notify us by
telephone at 856-964-7759 or by reply email.  We will arrange for the
return of the materials to us.  Please delete the copy of this message
on your server.  Very few methods of communication are 100% secure,
please exercise appropriate care when using or replying to this
message.  Thank you.

I.R.S. CIRCULAR 230 NOTICE: To comply with requirements imposed by the
Internal Revenue Service (I.R.S.) please be informed that the advice
contained in this communication was not intended or written to be used
and cannot be used for the purpose of avoiding penalties that may be
imposed by the I.R.S..

McKernan, McKernan & Godino does not attempt to sweep e-mail and
attachments for viruses.  It does not guarantee that either are
virus-free and accepts no liability or any damage sustained as a result
of viruses.

Re: [O] Super indent when editing R blocks and using a # comment

[Ista Zahn]

I'm pretty sure that's standard ess indentation. I don't think it has
anything to do with org mode.

Best,
Ista
On Jan 28, 2016 4:59 PM, "John Hendy"  wrote:

> Find attached a screenshot of the behavior I'm experiencing with this
> minimal config and =emacs -Q=.
>
> #+begin_src min-config
>
> ;; set load paths
> ;; set load dirs and global config options
> (add-to-list 'load-path "~/.elisp/org.git/lisp/")
> (add-to-list 'load-path "~/.elisp/org.git/contrib/lisp")
> (add-to-list 'load-path "~/.elisp/ess/lisp/")
>
> (require 'ess-site)
>
> ;; setup babel languages
> (org-babel-do-load-languages
>  'org-babel-load-languages
>  '((R . t)))
>
> #+end_src
>
> As shown in the shot:
> - create a .org file, insert a #+begin/end_src R block
> - edit with =C-c '=
> - start a line with a comment char (#)
> - press RET
> - it gets indented halfway across the page
>
> Inside a function, it seems to use a default of four spaces (the
> position of =return(i^2)=), so I'm not sure why a comment triggers
> such a massive indent. I end up having to delete the preceding spaces
> or be super careful about having a newline already inserted so that I
> can arrow down instead of pressing RET at the end of a comment line.
>
>
> Thanks for any insights!
> John
>

Re: [O] [PATCH] ox-koma-letter.el: Add support for 'location' koma variable

[Eric S Fraga]

On Wednesday, 27 Jan 2016 at 23:05, Rasmus wrote:
> It always makes me happy when someone is using ox-koma-letter.

Just to let you know that I use ox-koma-letter all the time!  It took a
while before I started using it but that was mostly because I need to
figure out how to do my organisation's letterhead using an LCO file...

So, thanks for ox-koma-letter!
-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3.3-449-gd85ff3

Re: [O] searching for links [8.3.3 (8.3.3-17-gce80a0-elpaplus @ c:/USR/FJM/APP/.emacs.d/elpa/org-20160118/)]

[Kyle Meyer]

Hello,

"Francis J. Monari, Esquire"  writes:

[...]

> Due to file relocation on the server, I have a number of broken links in
> an org document.  (problem: broken links.)
>
> How can I / Is it possible to search and replace on links?
> (expectation: I would like to use search and replace to fix the links.)
>
> I have tried search and replace, but emacs advises me that links have
> been filtered out.  (issue: emacs reports that results from the search
> are filtered-out.)

isearch filters these out by default.  To avoid this, you can set
search-invisible to t, but then you don't see what you're replacing.

Another option is to toggle literal link display with
org-toggle-link-display, and then run the search and replace as usual.

> The answer might be a "works as expected".  I would like to remain
> within the org framework (but using standard search and replace) and
> accomplish this task.
>
> (I thought about forcing the files into a different mode, but I do not
> want to risk the org file structure.)

I don't really see any danger in that because it's just plain text and
it's querying you about what to replace, so I think that's fine too for
a one-off search and replace.

--
Kyle

Re: [O] [PATCH] ox-koma-letter.el: Add support for 'location' koma variable

[Myles English]

Rasmus writes:

> Myles English  writes:
>
>> Thanks for making it!
>
> It's Nicolas’ creation, not mine.  I merely contribute a few patches
> to it.

Thanks to Nicolas too.

>>> Aside: it sounds like what you need is "yourref", maybe "yourmail",
>>> "myref", "customer", and "invoice".  These are typed in the same line as
>>> the date and place.  In my manual it’s described around pp. 180.
>>
>> Thanks, those are all useful fields I didn't know about.  The
>> description of "frombank" indicates that "location" is still a good
>> place for bank account details.
>
> OK.
>
>>> On to "location".  From the manual pp. 195 it looks like it is usually
>>> something akin to an address field on the right side of the head.  I think
>>> "location" should be settable via a special :location: heading, probably
>>> with special line breaking rules like the :to:/:from: special headings.
>>> We can allow a #+LOCATION keyword in addition, but need not.  All IMO.
>>> WDYT?
>>
>> Given that "location" is intended as a "user's extension field" I
>> suppose that a special tagged :location: heading would be convenient for
>> some uses, if you want to add it.  For most cases however, I think its
>> use would break up the structure of the org-mode letter so I would still
>> prefer this way for the simple case of inserting bank details:
>>
>> __
>>
>> ** Change of address
>> :EXPORT_LOCATION: \usekomavar{frombank}
>
> You could have this is a LCO file as well.

Do you mean like this:

\setkomavar{location}{\usekomavar{frombank}}

I don't understand why I would want to do that because I would have to
use a different LCO file depending on whether I was writing to my bank
or not.

> If so, you might be able to populate location using
> \ifkomavarempty{}{}.  I use this in my standard footer to insert
> fields depending on which variables are set.

Following on from my not understanding, any chance of an example of how
to do that showing what variable to set when writing to my bank, (to
cause the location variable to be populated with bank details)?

>> \setkomavar{frombank}{\raggedright Acc.~No.:\,1234567890\\at Big
>>   Bank\\Sort Code: 11-22-33}
>>
>> The bank details only appear in a letter when the property is set.
>>
>> Which is much neater than the special heading approach, something like
>> this:
>>
>> __
>>
>> ** Change of address
>>
>> *** Location field:location:
>> \usekomavar{frombank}
>
> But is it much neater than:
>
> ** bank details :location:
> Acc. no.: 12345
> Big Bank Corp
> Sort code: 1122 

Err, yes it is?  And anyway, that data is in my LCO file, I don't want
to duplicate it.

> For temporary data, I’d rather have it like in my example.  For permanent
> data I can keep it in a .lco file.

Yes, that is what I have done (hmmm, I am beginning to sense a
fundamental misunderstanding here).  My bank account details are
permanent data and are in a LCO file.

> And maybe #+include: "bank-info.org".

The way you have edited my original email in your reply makes it
difficult to follow what is being discussed.  I would like to clarify
the main point by quoting from my original message:

#+BEGIN_QUOTE
...I would still prefer this way for the simple case of
inserting bank details:

__

** Change of address
:EXPORT_LOCATION: \usekomavar{frombank}

I have moved.
__

Where the frombank variable has been set in the LCO file:

\setkomavar{frombank}{\raggedright Acc.~No.:\,1234567890\\at Big
  Bank\\Sort Code: 11-22-33}

The bank details only appear in a letter when the property is set.
#+END_QUOTE

That property mentioned is the :EXPORT_LOCATION: property.  You can set
it to whatever you like, referencing something in your LCO file or
temporary data.

Myles

[O] Inconsistent {{{time}}} org macro expansion

[Kaushal Modi]

Hi,

I am getting different outputs from org-export-get-date depending on
whether I export the full org file or just a selected heading. For #+DATE,
I am using a {{{time}}} macro.

Here's a test org file:

=

#+DATE: {{{time(%b %e %Y\, %a)}}}
* Heading 1
Content 1
* Heading 2
Content 2

=

And here is a test org-html-postamble function to help debug this:

=

(defun my/org-html-postamble-fn (info)
  (let ((date (car (org-export-get-date info
(message "Date: %S" date)))
(setq org-html-postamble #'my/org-html-postamble-fn)

=

SCENARIO 1: Normal export [GOOD]
In this scenario, I export the full org file to html (C-c C-e h h) without
selecting anything.
This is the output I get in *Messages*

Date: #("Jan 28 2016, Thu" 0 16 (:parent (#0)))

I get a date I case use in the postamble output.

SCENARIO 2: Export only one of the headings. [BAD]
Now select just the "Heading 1" sub-tree and then do C-c C-e h h.
This time, the output is:

Date: (macro (:key "time" :value "{{{time(%b %e %Y\\, %a)}}}" :args ("%b %e
%Y, %a") :begin 1 :end 26 :post-blank 0 :parent (#0)))

So it looks like the time macro did not expand.

Why is that? Is it a bug?

This is my org version: Org-mode version 8.3.3 (release_8.3.3-509-gc17fcc @
/home/kmodi/usr_local/apps/6/emacs/emacs-25/share/emacs/site-lisp/org/)


Thanks.

Kaushal Modi

Re: [O] Super indent when editing R blocks and using a # comment

[John Hendy]

On Thu, Jan 28, 2016 at 4:21 PM, Ista Zahn  wrote:
> I'm pretty sure that's standard ess indentation. I don't think it has
> anything to do with org mode.

Yikes. Hadn't occurred to me to just check ess directly, and I
completely assumed this was org related. Thanks for the reply, as a
google revealed this gem:
- 
http://stackoverflow.com/questions/780796/emacs-ess-mode-tabbing-for-comment-region

Short summary:
- # indents to the 40th character
- ## indents to the current indent level
- ### leaves the comment where it is

Sorry for the noise and thanks for pointing me in the right direction!


John

>
> Best,
> Ista
>
> On Jan 28, 2016 4:59 PM, "John Hendy"  wrote:
>>
>> Find attached a screenshot of the behavior I'm experiencing with this
>> minimal config and =emacs -Q=.
>>
>> #+begin_src min-config
>>
>> ;; set load paths
>> ;; set load dirs and global config options
>> (add-to-list 'load-path "~/.elisp/org.git/lisp/")
>> (add-to-list 'load-path "~/.elisp/org.git/contrib/lisp")
>> (add-to-list 'load-path "~/.elisp/ess/lisp/")
>>
>> (require 'ess-site)
>>
>> ;; setup babel languages
>> (org-babel-do-load-languages
>>  'org-babel-load-languages
>>  '((R . t)))
>>
>> #+end_src
>>
>> As shown in the shot:
>> - create a .org file, insert a #+begin/end_src R block
>> - edit with =C-c '=
>> - start a line with a comment char (#)
>> - press RET
>> - it gets indented halfway across the page
>>
>> Inside a function, it seems to use a default of four spaces (the
>> position of =return(i^2)=), so I'm not sure why a comment triggers
>> such a massive indent. I end up having to delete the preceding spaces
>> or be super careful about having a newline already inserted so that I
>> can arrow down instead of pressing RET at the end of a comment line.
>>
>>
>> Thanks for any insights!
>> John

Re: [O] Orgmode testsuite

[Nicolas Goaziou]

Hello,

Andrej Depperschmidt  writes:

> The following error occurs
>
> font-lock-fontify-keywords-region: Wrong type argument: listp,
> org-table

It looks like the same problem.

> I checked with the latest version of org from git.

Odd. Please make sure you are really using development version. If the
problem persists, could you provide an ECM?

Regards,

-- 
Nicolas Goaziou

Re: [O] Inconsistent {{{time}}} org macro expansion

[Nicolas Goaziou]

Hello,

Kaushal Modi  writes:

> I am getting different outputs from org-export-get-date depending on
> whether I export the full org file or just a selected heading. For #+DATE,
> I am using a {{{time}}} macro.
>
> Here's a test org file:
>
> =
>
> #+DATE: {{{time(%b %e %Y\, %a)}}}
> * Heading 1
> Content 1
> * Heading 2
> Content 2
>
> =
>
> And here is a test org-html-postamble function to help debug this:
>
> =
>
> (defun my/org-html-postamble-fn (info)
>   (let ((date (car (org-export-get-date info
> (message "Date: %S" date)))
> (setq org-html-postamble #'my/org-html-postamble-fn)
>
> =
>
> SCENARIO 1: Normal export [GOOD]
> In this scenario, I export the full org file to html (C-c C-e h h) without
> selecting anything.
> This is the output I get in *Messages*
>
> Date: #("Jan 28 2016, Thu" 0 16 (:parent (#0)))
>
> I get a date I case use in the postamble output.
>
> SCENARIO 2: Export only one of the headings. [BAD]
> Now select just the "Heading 1" sub-tree and then do C-c C-e h h.
> This time, the output is:
>
> Date: (macro (:key "time" :value "{{{time(%b %e %Y\\, %a)}}}" :args ("%b %e
> %Y, %a") :begin 1 :end 26 :post-blank 0 :parent (#0)))
>
> So it looks like the time macro did not expand.
>
> Why is that? Is it a bug?

It was. It is now fixed. Thank you.


Regards,

-- 
Nicolas Goaziou

Re: [O] Orgmode testsuite

[Christian Kruse]

Hi,

Nicolas Goaziou  writes:

>> Do you need more information on that? I hit the error, too.
>
> It is fixed already. 

Nice, thanks!

> Unfortunately, Org ELPA updates every Monday AFAICT. So, unless someone
> can refresh the Org package there, we'll have to live with it until next
> week.

That’s fine for me, just wanted to make sure that it can get fixed and
you don’t need more information. Thanks for your work!

Freundliche Grüsse,
-- 
Christian Kruse
https://wwwtech.de/about


signature.asc
Description: PGP signature

Re: [O] [PATCH] org-latex-compile timestamp checks

[Nicolas Goaziou]

Hello,

Rasmus  writes:

> Thanks!  I have added a TODO to my agenda regarding checking other
> backends, but I'd not hold grudges against anyone who beats me to it.

I took care of ox-groff, ox-man and ox-texinfo.

I let you improve zip handling in ox-odt, if you want to.

Regards,

-- 
Nicolas Goaziou

Re: [O] org-agenda-filter-by-tag-refine defaults to exclude

[Gustav Wikström]

Hi Kyle, Viktor and the group,

I'd say it's a naming-problem. What, really, is the purpose of the function? 
Because applying the proposed change essentially makes the function identical 
to the function it calls. Right? And that function is still available for the 
user, so a "refinement" can be done without the org-agenda-filter-by-tag-refine 
(bound to backslash (\) ) function. As of now, using the function to exclude 
tags in the agenda provides a direct access to that functionality, instead of 
calling org-agenda-filter-by-tag (bound to slash (/) ) plus pushing the minus 
key (-) to switch from filter to exclude.

If you want to make any change, I'd suggest to instead change the name of 
org-agenda-filter-by-tag-refine to org-agenda-filter-by-tag-exclude and to 
leave the code within the function as is (well.. maybe change 'refine to 
'exclude with the same argument as to the function name change).

Best Regards
Gustav

-Original Message-
From: Kyle Meyer [mailto:k...@kyleam.com] 
Sent: Tuesday, January 12, 2016 07:19
To: Viktor Rosenfeld 
Cc: emacs-orgmode@gnu.org; Gustav Wikström 
Subject: Re: org-agenda-filter-by-tag-refine defaults to exclude

Hi Viktor,

Viktor Rosenfeld  writes:

> Hi,
>
> I noticed that org-agenda-filter-by-tag-refine started to exclude 
> selected tags by default recently because the 'refine in the call to 
> org-agenda-filter-by-tag is interpreted as an exclude flag.

This seems to have been introduced by 6c6ae99 (org-agenda: Filtering in the 
agenda on grouptags, 2015-01-24).

> The attached patch fixes this.
>
> However, it seems that the function is superfluous because 
> org-agenda-filter-by-tag can filter on multiple tags as well if called 
> multiple times (that used not to be the case earlier).  So maybe it 
> should be deprecated and removed?

I agree.  Gustav, does that make sense given your changes in 6c6ae99?

> diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index 
> d91b64d..21928de 100644
> --- a/lisp/org-agenda.el
> +++ b/lisp/org-agenda.el
> @@ -7580,7 +7580,7 @@ to switch between filtering and excluding."
>  (defun org-agenda-filter-by-tag-refine (arg  char)
>"Refine the current filter.  See `org-agenda-filter-by-tag'."
>(interactive "P")
> -  (org-agenda-filter-by-tag arg char 'refine))
> +  (org-agenda-filter-by-tag arg char))

>  (defun org-agenda-filter-make-matcher (filter type  expand)
>"Create the form that tests a line for agenda filter.  Optional


--
Kyle

Re: [O] Orgmode testsuite

[Andrej Depperschmidt]

Hello,

I'm not sure if it is related...
In tables containing an url with http://something I cannot move as usual using 
TAB.
(see also
http://emacs.stackexchange.com/questions/19874/external-http-link-not-recognized-as-link
 )

The following error occurs

font-lock-fontify-keywords-region: Wrong type argument: listp, org-table

I checked with the latest version of org from git.

Best,
Andrej


Nicolas Goaziou  writes:

> Hello,
>
> Christian Kruse  writes:
>
>> Do you need more information on that? I hit the error, too.
>
> It is fixed already.
>
> Unfortunately, Org ELPA updates every Monday AFAICT. So, unless someone
> can refresh the Org package there, we'll have to live with it until next
> week.
>
> Regards,

Re: [O] Bug: Habits will not correctly reset timestamp [8.3.2 (release_8.3.2-570-gc17fcc @ /home/swflint/.emacs.d/org-mode/lisp/)]

[Nicolas Goaziou]

Hello,

swfl...@flintfam.org (Samuel W. Flint) writes:

> See my previous bug report.  This still happens.
>
> If I have a heading like so:
>
> * TODO Something
> SCHEDULED: <2016-01-17 Sun .+1w/2w>
> :PROPERTIES:
> :STYLE: habit
> :END:
>
> And execute C-c C-t d on the heading, the following appears:
>
> * TODO Something
> :PROPERTIES:
> :STYLE: habit
> :END:
>
> This is incorrect behavior, and I'm unable to use org-habits
> correctly.

I cannot reproduce it. With -Q, I get

  * TODO Something
  SCHEDULED: <2016-02-04 jeu. .+1w/2w>
  :PROPERTIES:
  :STYLE: habit
  :LAST_REPEAT: [2016-01-28 jeu. 09:03]
  :END:
  - State "DONE"   from "TODO"   [2016-01-28 jeu. 09:03]


Regards,

-- 
Nicolas Goaziou

[O] Org-mode via ELPA and via git in parallel

[Karl Voit]

Hi!

I am using Org-mode version 8.3.3 (release_8.3.3-17-gce80a0 @
c:/Users/karl.voit/.emacs.d/contrib/org-mode/lisp/)[fn:1] which is
the maint branch from the git repo. And this is the version I intend
to use.

As I noticed yesterday, in my ELPA-directory there is
"org-20160125/" which I never installed on purpose.

Since I am using use-package[fn:up] to install most of my emacs
add-ons, I do think that any other package may have org-mode
installed via ELPA (dependency-rule?).

The output of 
   cd ~/.emacs.d/elpa && du |sed 's#./##'|grep -v "/"
is published on [fn:elpa-packages]


Two questions:

1. Do I have to care about the ELPA Org-mode folder (ignoring the
occupied disk space) or might this ELPA Org-mode interfere with my
git Org-mode?

2. How am I able to find out why the ELPA Org-mode folder exists in
my setup?


Thanks!


[fn:1] at least this is what "M-x org-version" says
[fn:up] https://github.com/jwiegley/use-package
[fn:elpa-packages] http://karl-voit.at/temp/2016-01-28-du-elpa.log

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: [O] [PATCH] ox-koma-letter.el: Add support for 'location' koma variable

[Rasmus]

Myles English  writes:

> Thanks for making it!

It's Nicolas’ creation, not mine.  I merely contribute a few patches
to it.

>> Aside: it sounds like what you need is "yourref", maybe "yourmail",
>> "myref", "customer", and "invoice".  These are typed in the same line as
>> the date and place.  In my manual it’s described around pp. 180.
>
> Thanks, those are all useful fields I didn't know about.  The
> description of "frombank" indicates that "location" is still a good
> place for bank account details.

OK.

>> On to "location".  From the manual pp. 195 it looks like it is usually
>> something akin to an address field on the right side of the head.  I think
>> "location" should be settable via a special :location: heading, probably
>> with special line breaking rules like the :to:/:from: special headings.
>> We can allow a #+LOCATION keyword in addition, but need not.  All IMO.
>> WDYT?
>
> Given that "location" is intended as a "user's extension field" I
> suppose that a special tagged :location: heading would be convenient for
> some uses, if you want to add it.  For most cases however, I think its
> use would break up the structure of the org-mode letter so I would still
> prefer this way for the simple case of inserting bank details:
>
> __
>
> ** Change of address
> :EXPORT_LOCATION: \usekomavar{frombank}

You could have this is a LCO file as well.  If so, you might be able to
populate location using \ifkomavarempty{}{}.  I use this in my standard
footer to insert fields depending on which variables are set.

> \setkomavar{frombank}{\raggedright Acc.~No.:\,1234567890\\at Big
>   Bank\\Sort Code: 11-22-33}
>
> The bank details only appear in a letter when the property is set.
>
> Which is much neater than the special heading approach, something like
> this:
>
> __
>
> ** Change of address
>
> *** Location field:location:
> \usekomavar{frombank}

But is it much neater than:

** bank details :location:
Acc. no.: 12345
Big Bank Corp
Sort code: 1122 

For temporary data, I’d rather have it like in my example.  For permanent
data I can keep it in a .lco file.

And maybe #+include: "bank-info.org".

Thanks,
Rasmus

-- 
History is what should never happen again

[O] Org-mode on Github

[gongzhitaao]

Hi Awesome Orgmode,

I got a quick question: why not put org-mode on github?

1. Everyone can see the development process clearly.  While currently
   we can still do it but github makes it much more easier.
2. We can choose whichever version we want to use (most of the time,
   the latest of course, but just in case of an wierd bugs).
3. Github makes collaboration easier, e.g., everyone may submit a PR
   for a quick fix.

Re: [O] Org-mode on Github

[Robert Klein]

Hi,

gongzhitaao  wrote:

> Hi Awesome Orgmode,
> 
> I got a quick question: why not put org-mode on github?

because we have all those, too

> 
> 1. Everyone can see the development process clearly.  While currently
>we can still do it but github makes it much more easier.

git repository on orgmode.org

> 2. We can choose whichever version we want to use (most of the time,
>the latest of course, but just in case of an wierd bugs).

same as 1.  Just check out a commit or release you like and use it.

> 3. Github makes collaboration easier, e.g., everyone may submit a PR
>for a quick fix.

Org development happens on this mailing list, not i some bug tracker.
Send your git-diff to the list.

Best regards
Robert

Re: [O] Org-mode via ELPA and via git in parallel

[Alan Schmitt]

Hi Karl,

On 2016-01-28 10:48, Karl Voit  writes:

> Since I am using use-package[fn:up] to install most of my emacs
> add-ons, I do think that any other package may have org-mode
> installed via ELPA (dependency-rule?).

I have observed this in the past as well.

> Two questions:
>
> 1. Do I have to care about the ELPA Org-mode folder (ignoring the
> occupied disk space) or might this ELPA Org-mode interfere with my
> git Org-mode?

I’ve had issues with this in the past (I also use org for git). To make
sure org is never installed with elpa, I manually install
(`package-install-file') this org.el file:

#+begin_src emacs-lisp
;;; org.el --- Dummy org mode package

;; Copyright (C) 2014 Alan Schmitt

;; Version: 3101

()

;;; org.el ends here
#+end_src

If you use it, don’t forget to change the copyright ;)

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Athmospheric CO₂ (Updated January 27, 2016, Mauna Loa Obs.): 403.69 ppm


signature.asc
Description: PGP signature

Re: [O] [PATCH] ox-koma-letter.el: Add support for 'location' koma variable

[Myles English]

Hi Rasmus,

Rasmus writes:

> Thanks for your patch.
>
> It always makes me happy when someone is using ox-koma-letter.

Thanks for making it!

>> Often when writing a letter I want to include "Your Ref: xyz" or
>> "Account No.: 1234" and a good place to do this is below the sender's
>> address field and above the date (and 'place') field(s).  This space
>> becomes filled with the contents of the koma variable called 'location'.
>> This patch enables filling this variable via org-mode's contrib
>> ox-koma-letter exporter.
>
> Aside: it sounds like what you need is "yourref", maybe "yourmail",
> "myref", "customer", and "invoice".  These are typed in the same line as
> the date and place.  In my manual it’s described around pp. 180.

Thanks, those are all useful fields I didn't know about.  The
description of "frombank" indicates that "location" is still a good
place for bank account details.

> On to "location".  From the manual pp. 195 it looks like it is usually
> something akin to an address field on the right side of the head.  I think
> "location" should be settable via a special :location: heading, probably
> with special line breaking rules like the :to:/:from: special headings.
> We can allow a #+LOCATION keyword in addition, but need not.  All IMO.
> WDYT?

Given that "location" is intended as a "user's extension field" I
suppose that a special tagged :location: heading would be convenient for
some uses, if you want to add it.  For most cases however, I think its
use would break up the structure of the org-mode letter so I would still
prefer this way for the simple case of inserting bank details:

__

** Change of address
:EXPORT_LOCATION: \usekomavar{frombank}

I have moved.
__

Where the frombank variable has been set in the LCO file:

\setkomavar{frombank}{\raggedright Acc.~No.:\,1234567890\\at Big
  Bank\\Sort Code: 11-22-33}

The bank details only appear in a letter when the property is set.

Which is much neater than the special heading approach, something like
this:

__

** Change of address

*** Location field:location:
\usekomavar{frombank}

*** Rest of letter
I have moved.
__


Myles

Re: [O] org-player and switch to lexical binding in org.el

[Michael Brand]

Hi Nicolas

On Sun, Jan 17, 2016 at 9:40 PM, Nicolas Goaziou  wrote:
> Hello,
>
> Michael Brand  writes:
>
>> release_8.3.3-426-g1f49e9f introduces a regression. The link
>>
>> [[file:/dir/audio.mp3::0:12:34]]
>>
>> results in
>>
>> Debugger entered--Lisp error: (void-variable search)
>>   (org-player-play-file file search)
>>   [...]
>>   org-open-file("/dir/audio.mp3" nil nil "0:12:34")
>>   [...]
>
> `search' never was advertised as a dynamically scoped variable in
> `org-file-apps' docstring, so "org-player" is just playing with fire
> here.
>
> I don't like the current solution either (eval with a LEXICAL argument).
>
> I think it would be better to use un function with two arguments (file
> and link-string instead). This is not backward compatible, but the
> change is trivial: sexp -> (lambda (file link) sexp).
>
> In the current case, you need to use match string:
>
>   (add-to-list 'org-file-apps
>(cons (concat org-player-file-extensions-regexp
>  "::\\([0-9]+:[0-9]+\\(:[0-9]+\\)?\\)")
>  (lambda (file link)
>(org-player-play-file file (match-string 1 link)
>
> WDYT?

I am still not able to get your suggestion that Paul has implemented
in the meantime in org-player.el 1.0.1 to work. Now I am trying to
understand what I am missing with the lambda.

Has the (eval cmd) in org-open-file to be extended somehow to the
variant (funcall cmd) as lambda evaluates to itself?

Michael

Re: [O] [PATCH] org-latex-compile timestamp checks

[Rasmus]

Nicolas Goaziou  writes:

> Hello,
>
> Rasmus  writes:
>
>> Thanks!  I have added a TODO to my agenda regarding checking other
>> backends, but I'd not hold grudges against anyone who beats me to it.
>
> I took care of ox-groff, ox-man and ox-texinfo.

Thanks.

> I let you improve zip handling in ox-odt, if you want to.

OK.  I'll be traveling this weekend so I won't have time then.  Though it
should be quick now that I can look at yours and Anthony’s code.

Rasmus

-- 
Hooray!

Re: [O] Org-mode via ELPA and via git in parallel

[Karl Voit]

Hi Alan,

* Alan Schmitt  wrote:
>
> On 2016-01-28 10:48, Karl Voit  writes:
>
>> Since I am using use-package[fn:up] to install most of my emacs
>> add-ons, I do think that any other package may have org-mode
>> installed via ELPA (dependency-rule?).
>
> I have observed this in the past as well.
>
>> Two questions:
>>
>> 1. Do I have to care about the ELPA Org-mode folder (ignoring the
>> occupied disk space) or might this ELPA Org-mode interfere with my
>> git Org-mode?
>
> I=E2=80=99ve had issues with this in the past (I also use org for git). To =
> make
> sure org is never installed with elpa, I manually install
> (`package-install-file') this org.el file:
>
> #+begin_src emacs-lisp
> ;;; org.el --- Dummy org mode package
>
> ;; Copyright (C) 2014 Alan Schmitt
>
> ;; Version: 3101
>
> ()
>
> ;;; org.el ends here
> #+end_src

There is no "(provide 'org)" or so?

> If you use it, don=E2=80=99t forget to change the copyright ;)

*ggg*

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: [O] Org-mode via ELPA and via git in parallel

[Achim Gratz]

Karl Voit writes:
> As I noticed yesterday, in my ELPA-directory there is
> "org-20160125/" which I never installed on purpose.

It's probably been pulled in by some dependency.  Package manager is not
very smart with this.  You need to drop a dummy org package with a high
enough version so that Org never gets upgraded via package manager.

> 1. Do I have to care about the ELPA Org-mode folder (ignoring the
> occupied disk space) or might this ELPA Org-mode interfere with my
> git Org-mode?

No, you shouldn't have it installed via ELPA.  It may work one day and
stop working another depending on which patch your initializations
actually take.

> 2. How am I able to find out why the ELPA Org-mode folder exists in
> my setup?

Some other package pulls it in as a dependency.  Package manager
operates on the assumption that you install everything via ELPA.  If you
don't, then you have to take care of that yourself.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: [O] Attach a Word doc in org mode file

[Richard Lawrence]

Hi Eliya,

Eliya Voldman  writes:

> How could I attach a Word document in my .org file? I could do it for plain
> text file like C-c C-a but not .doc type.
>
> In other words: attach Word doc is not a problem but the problem is to open
> it.

What OS are you on?  Windows?  OS X?

I don't know how exactly Org decides how to open files on your system,
but if you're having trouble, I guess you should start by looking up the
value of the org-file-apps variable.  Try:

C-h v org-file-apps

> Are there other options to point to Word file in my system other the
> attach?

You can use a link; see this section of the manual:

http://orgmode.org/manual/Hyperlinks.html#Hyperlinks

> BTW: is it possible to attach and then open in org mode files other that
> plain text?

It depends what you mean by "open in org mode".  The only files it makes
sense to open as Emacs buffers with Org as the major mode are plain text
files in Org mode format.  But you can open other types of files in
Emacs in other modes.  And from within an Org mode buffer, you should be
able to launch programs other than Emacs (such as Word) that can read
other kinds of files, for example by following a link with C-c C-o.

Hope that helps!

Best,
Richard

[O] links in headlines and org-bbdb-anniversaries

[George McNinch]

Hi--

I use org via ELPA. This week, the packages

 org-20160118
 org-plus-contrib-20160118

were replaced by

 org-20160125
 org-plus-contrib-20160125

After update, org began complaining about links in the headlines
which appear in my *Agenda*.

More precisely, this was reported:

   > org-agenda-finalize: Wrong type argument: listp, org-link

So, I removed links from my headlines.

But: I still get the error, I believe because I have

%%(org-bbdb-anniversaries)

in my agenda. The result of org-bbdb-anniversaries seems to at least act
like headlines from the point-of-view of the agenda, and those headlines
contain [bbdb:...][...] links.

All the best,
gm

-- 
   |∈|∋|   George McNinch 
   |∈|∋|   http://gmcninch.math.tufts.edu 

[O] Attach a Word doc in org mode file

[Eliya Voldman]

How could I attach a Word document in my .org file? I could do it for plain
text file like C-c C-a but not .doc type. Are there other options to point
to Word file in my system other the attach?
In other words: attach Word doc is not a problem but the problem is to open
it.
BTW: is it possible to attach and then open in org mode files other that
plain text?
Thanks

--

[O] display org-link url

[Satoru KURASHIKI]

hi,

Are there any good way/settings to display org-link's url easily?

I'm happy if I can see them in minibuffer putting cursor on the org-link.
(like pointing urls on web browsers may show urls in statusbar)

regards,
-- 
KURASHIKI Satoru

Re: [O] [PATCH] org-attach.el: Get attachments from git annex

[Kyle Meyer]

Erik Hetzner  writes:

> I believe this addresses all the issues that have been raised. Thanks for all
> your help with this.

Thanks for the updates.  I just have two minor things to add to Rasmus's
comments.

- Nitpick: It'd be nice if you could re-flow some of your lines to not
  be as wide.

- What's the advantage of using cl-defmacro instead of defmacro below?

> +(cl-defmacro test-org-attach-annex/with-annex ( body)
> +  `(let ((tmpdir (make-temp-file "org-annex-test" t)))
> + (unwind-protect
> +  (let ((default-directory tmpdir)

Thanks again.

-- 
Kyle