[O] Potential feature request – more automatic updating of cookies

2016-07-27 Thread Jorge Peixoto de Morais Neto
Paste the following in an Org buffer:
--8<---cut here---start->8---
* Cookie_a [0/0]
* TODO Dummy_a
* Cookie_b [0/1]
** TODO Dummy_b
--8<---cut here---end--->8---

Within that buffer:
   1. Move point to the line of Dummy_a.
   2. 
I wished the cookie to be updated to [0/1] but it is not.

Then:
   1. Move point to the line of Dummy_b.
   2. C-c C-x C-w
   3. Move point to the line of Dummy_a at column 0.
   4. C-c C-x C-y
I wished both cookies to be updated.  They are not.

The manual [[info:org#Checkboxes][says]]:
    Checkbox statistic cookies are updated automatically if you toggle
checkboxes with `C-c C-c' and make new ones with `M-S-'.  TODO
statistics cookies update when changing TODO states.  If you delete
boxes/entries or add/change them by hand, use this command to get things
back into sync.

Should I request the feature of Org automatically updating cookies when using
structure editing commands such as C-c C-x C-w, C-c C-x C-y, ,
 and friends?  Would it be worth the development cost?  I
unfortunately cannot develop it myself.

The point is that C-u C-c # (to update cookies in the entire buffer) takes
long enough that I only call it a few times per week.  This means that cookies
can get out of sync.  Then I try to remember manually invoking C-c # on the
relevant line every time it goes out of sync, but I sometimes omit it.

I figured I should discuss this in the mailing list before submitting a bug
report with org-submit-bug-report.

Regards

-- 
• I am Brazilian.  I hope my English is correct and I welcome corrections.
• Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z.
• Free (as in free speech) software for Android: https://f-droid.org/





Re: [O] pagebreak

2016-07-27 Thread Nick Dokos
Leslie Watter  writes:


> Where in styles.xml did you put the above statement ?
>
Check the styles.xml attachment in

  http://thread.gmane.org/gmane.emacs.orgmode/108503/focus=108532

for the original placement and in

  http://thread.gmane.org/gmane.emacs.orgmode/108503/focus=108535

for the modified placement.

(but note that gmane is struggling atm - anybody know what's up with
it?)

-- 
Nick




Re: [O] error on make

2016-07-27 Thread Giri Prashanth
Thank you for your response. I have GNU Emacs 24.5.1
(x86_64-apple-darwin13.4.0, NS apple-appkit-1265.21) .
One possibility is that in OS X, there is a default emacs with version
22.1.1. I tried brew update but I think for some reason it is not updated
and may cause for this problem.

Is there a way to specify the location of emacs application and site-lisp
folder in the config or  Makefile ?
I tried adding path manually in the prefix argument in local.mk but was not
sucessful.

Thank you again,



On Tue, Jul 26, 2016 at 11:21 PM, Nicolas Goaziou 
wrote:

> Hello,
>
> Giri Prashanth  writes:
>
> > I got the following error while I ran make on latest org-mode code from
> git
> > got from git://orgmode.org/org-mode.git in OS X:
> >
> > rm -f
> > /Applications/Xcode.app/Contents/Developer/usr/bin/make -C lisp clean
> > rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc
> > org-install.elc
> > rm -f *.elc
> > /Applications/Xcode.app/Contents/Developer/usr/bin/make -C lisp autoloads
> > rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc
> > org-install.elc
> > org-version: 8.3.5 (release_8.3.5-1027-g04e0bc)
> > Loading ~/.emacs.d/org-mode/lisp/org-compat.el (source)...
> > Cannot open load file: cl-lib
> > make[1]: *** [org-version.el] Error 255
> > make: *** [autoloads] Error 2
> >
> >
> > Any ideas on how to fix ?
>
> What is your Emacs version? Development branch requires at least Emacs
> 24.3.
>
>




> Regards,
>
> --
> Nicolas Goaziou
>


Re: [O] pagebreak

2016-07-27 Thread Leslie Watter
Hi Uwe,

On Tue, Jul 26, 2016 at 6:52 PM, Uwe Brauer  wrote:

>
>> Uwe Brauer  writes:
>
>> Can you try the attached styles.xml? I just moved the style to another
>> place and I get the page break (whereas I did not get it with your
>> original styles.xml). But I really don't know the rules: somebody else
>> might be able to offer some enlightenment (assuming that it even
> works).
>
> It works! Great thanks, so it seems important where to put
>
>  style:parent-style-name="Text_20_body">
> 
> 
>
> In the styles.xml file
>

Where in styles.xml did you put the above statement ?

Cheers,

LEslie



>
> Uwe
>
>
>


-- 
Leslie H. Watter


Re: [O] error while upgrading to 8.3.5

2016-07-27 Thread John Kitchin
With the most current master, I get these two failed tests:

2 unexpected results:
   FAILED  ob-shell/bash-uses-assoc-arrays
   FAILED  test-ob/indented-cached-org-bracket-link

This is with a Mac, and GNU Emacs 25.1.50.1 (x86_64-apple-darwin13.4.0, NS 
appkit-1265.21 Version 10.9.5 (Build 13F1808))
 of 2016-07-11


There seem to be two identically named tests (both fail for me).

(ert-deftest ob-shell/bash-uses-assoc-arrays ()
  "Bash associative arrays"
  (org-test-at-id "bec1a5b0-4619-4450-a8c0-2a746b44bf8d"
(org-babel-next-src-block 2)
(should (equal "two" (org-babel-execute-src-block)


(ert-deftest ob-shell/bash-uses-assoc-arrays ()
  "Bash associative arrays as strings for the row"
  (org-test-at-id "82320a48-3409-49d7-85c9-5de1c6d3ff87"
(org-babel-next-src-block 2)
(should (equal "20 cm" (org-babel-execute-src-block)


The code in the should macro in this test: 
test-ob/indented-cached-org-bracket-link
evaluates to true for me, but still fails in make test.

Nicolas Goaziou writes:

> Hello,
>
> Vikas Rawal  writes:
>
>> * Output of BTEST_RE=indented-cached-org-bracket-link make test
>>
>> Test test-ob/indented-cached-org-bracket-link condition:
>> (ert-test-failed
>>  ((should
>>(let
>> (...)
>>   (org-test-with-temp-text "\n* Test\n  #+BEGIN_SRC emacs-lisp 
>> :file test.txt :cache yes\n(message \"test\")\n  #+END_SRC" ... ...)))
>>   :form
>>   (let
>>((default-directory temporary-file-directory))
>>  (org-test-with-temp-text "\n* Test\n  #+BEGIN_SRC emacs-lisp 
>> :file test.txt :cache yes\n(message \"test\")\n  #+END_SRC"
>>(org-babel-execute-src-block)
>>(string= ... ...)))
>>   :value nil))
>>FAILED  1/1  test-ob/indented-cached-org-bracket-link
>
> This doesn't ring a bell. It would help to know what is hidden behind
> the ellipsis.
>
>> Ran 1 tests, 0 results as expected, 1 unexpected (2016-07-26 05:06:12+0530)
>>
>> 1 unexpected results:
>>FAILED  test-ob/indented-cached-org-bracket-link
>>
>> * (org-parse-time-string "<2014-03-04 Tue>”)
>> (apply #'encode-time (org-parse-time-string "<2014-03-04 Tue>"))
>>
>> Evaluating these in emacs does not seem to do anything. No message.
>
> The return value is displayed in the minibuffer. Use C-x C-e right after
> the closing parens of each form.
>
> Also, did you set some weird variable like `org-extend-today-until'?
>
> Regards,


-- 
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu



Re: [O] verse

2016-07-27 Thread Christian Moe

Uwe Brauer writes:

>>> It seems that the verse environment does what I want, it is however
>>> exported in a ugly font (type writer), how can I change that font.
>
>> See the manual, section 12.9.4 "Applying custom styles".
>
> That section is a very general one, I cannot find anything about the
> verse environment and its setting.

The section is general because it tells you how to style *everything*,
including, but not limited to, verse environments. When exporting to ODT
you don't set fonts for particular environments in Org-mode. Rather, you
use an application like LibreOffice to modify and save a stylesheet, and
tell Org-mode what stylesheet to apply to exported ODT.

Export a document to ODT with the ugly verse environment, then either
locate the 'OrgVerse' style in the LibreOffice 'Stylist' and edit it
there, or simply right-click on a verse and choose 'Edit Paragraph
Style' from the menu. Choose a different font. Change any other styles
(e.g. headings) as you like. Save the modified document in a convenient
place, then use it as an Org ODT styles file as described in the manual.

Yours,
Christian




[O] Patch: org-link-ignore-path-to-self

2016-07-27 Thread Shintaro Katayama
Hi,

The attached patch enables to choose whether link contains a (file-)path to
self, or not. One new variable "org-link-ignore-path-to-self" should be
true as the original behavior (~ no path to self by org-insert-link).
However, the path-to-self will remain when the value is nil.

This feature is helpful, especially for org-journal - you can use
org-insert-link from TODOs to journal entries in a journal; the links are
preserved even after carryover.

Regards,
Shintaro


--- /Users/shin/.emacs.d/elpa/org-20160711/org.el~  2016-07-16
01:46:09.0 +0200
+++ /Users/shin/.emacs.d/elpa/org-20160711/org.el   2016-07-27
10:40:30.0 +0200
@@ -10386,6 +10386,7 @@
 ;; option If yes, simplify the link by using only the search
 ;; option.
 (when (and buffer-file-name
+  org-link-ignore-path-to-self
   (string-match "^file:\\(.+?\\)::\\(.+\\)" link))
   (let* ((path (match-string 1 link))
 (case-fold-search nil)


Re: [O] Echo heading hierarchy at point

2016-07-27 Thread Roelli, Charles A
Thank you!

`(org-display-outline-path nil t)’ gets it done.


> On Jul 26, 2016, at 9:42 AM, Nicolas Goaziou  wrote:
> 
> Hello,
> 
> "Roelli, Charles A"  writes:
> 
>> Sent this in a few days ago, and it does not seem to have gone through: 
>> 
>> ---
>> 
>> If I have this structure, with point marked by the "$":
>> 
>> * Heading Level 1
>> ** Heading Level 2
>> $
>> 
>> Is there a way to have the current place in the outline [Heading Level
>> 1 => Heading Level 2] temporarily echoed in the minibuffer? Also
>> important is that the point shouldn't have to be on the heading title
>> for it to work.
> 
> See `org-display-outline-path' and `org-get-outline-path'.
> 
> 
> Regards,
> 
> -- 
> Nicolas Goaziou



Re: [O] error on make

2016-07-27 Thread Nicolas Goaziou
Hello,

Giri Prashanth  writes:

> I got the following error while I ran make on latest org-mode code from git
> got from git://orgmode.org/org-mode.git in OS X:
>
> rm -f
> /Applications/Xcode.app/Contents/Developer/usr/bin/make -C lisp clean
> rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc
> org-install.elc
> rm -f *.elc
> /Applications/Xcode.app/Contents/Developer/usr/bin/make -C lisp autoloads
> rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc
> org-install.elc
> org-version: 8.3.5 (release_8.3.5-1027-g04e0bc)
> Loading ~/.emacs.d/org-mode/lisp/org-compat.el (source)...
> Cannot open load file: cl-lib
> make[1]: *** [org-version.el] Error 255
> make: *** [autoloads] Error 2
>
>
> Any ideas on how to fix ?

What is your Emacs version? Development branch requires at least Emacs
24.3.

Regards,

-- 
Nicolas Goaziou