Re: [O] org-annotate/collaboration?
Uwe Brauer writes: "Eric" == Eric Abrahamsen writes: > >> Matt Price writes: >>> Does anyone use org-annotate actively? I'm wondering what your >>> workflow is, how you incorporate comments, etc. > >> I wrote it, and I don't use it that much. I do use it for quick >> notes-to-self when writing, but footnotes do the job just as well. > >>> I'm hoping to embark on a book project with a colleague. I would like >>> to use org-mode if I can, but I need to get a sense of the >>> collaboration workflow. When you work on projects together, do you use >>> annotations? Or git pull requests? If the latter, od you use any >>> filters, or any magit tricks, to approve or modify suggested changes >>> chunk by chunk? > >> It's a huge problem, and one that org-annotate isn't going to solve. I >> do a lot of manuscript editing, and passing files around, and have only >> barely gotten some people to accept my "weird" workflow, which is to >> send them a clean version of an edited file, and along with that an HTML >> file containing htmlized word-diff output, where the insertions and >> deletions are colorized. They make further edits on the clean copy, and >> I do another go-around. It's a huge pain. > > I did (and still do) the same, using latex and latexdiff, but found out > that a better solution is to use mercurial and bitbucket (I presume git > should be fine as well), since one of my collaborators agree to use it > as well. This is quite a relief to the former method relying on external > tools and email. > > - Usually instead of comments I use issuesin bitbucket. > - hg diff is not perfect but a good first approximation. I think collaborators who have even a tiny familiarity with technological tools make the whole process much, much easier. Unfortunately I'm working with technophobes, the sort of people who call the browser "the internet", so I have almost no wiggle room at all... E
Re: [O] Bug: transposition of words surrounded by forward slash [9.0.5 (release_9.0.5-266-gca31fa )]
Nicolas Goaziou writes: > Hello, > > Justin Kirby writes: > >> An org file with the following content: >> >> #+OPTIONS: *:nil >> >> /simple/ /example/ >> >> >> >> During export org will transpose the word 'example' so the final output is >> >> //examplesimple/ / >> >> >> >> This will be the output regardless of export format. I have tried html, >> txt, odt, md. >> >> The words will be transposed as long as they are on the same line, >> regardless of how many characters are between them. >> >> This was observed as early as org 8.3.5. >> >> Changing the italic character in org-emphasis-alist to | does not change >> this behavior. > > Fixed. Thank you. Verified! Thanks for the quick turn around! Justin
Re: [O] Latex summary
On Monday, 13 Feb 2017 at 19:44, Russell Adams wrote:
[...]
> Eric, thanks for that really detailed input. I'll have to consider
> it. I worry that the keywords aren't like the full sentences I'm
> using.
Ah, okay.
Well, I'm not sure there is anything in LaTeX that does this as such but
you could play around with inline tasks. You could use an inline task
to give the recommendation and then use
org-latex-format-inlinetask-function
to specify your own function that would, for instance, output the
recommendation inline but also create an endnote (cf. endnotes LaTeX
package) for the summary at the end?
I do this for collecting TODO items when I'm writing a proposal or
paper. My function looks like this:
#+begin_src emacs-lisp
;; define what to do with inline tasks: use endnote
(defun esf/org-format-inlinetask-as-endnote (todo type priority name tags
contents info)
"Format an inline task element for LaTeX export."
(let ((theinlinetask (concat " " name ": " contents)))
(if (and todo (not (equal todo "NOTE")))
(format "\\endnote{%s}\\marginpar{\\fbox{\\tiny E\\theendnote. %s}}"
theinlinetask todo)
(format "\\hl{%s}" contents
(setq-local org-latex-format-inlinetask-function
'esf/org-format-inlinetask-as-endnote)
#+end_src
Although I don't put any text inline, you could easily do so.
HTH,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8
signature.asc
Description: PGP signature
Re: [O] Heads-up: test failures
Nicolas Goaziou writes:
> What is the failure in each case?
The move-down/up failures look like this:
,
|passed 512/710 test-org-list/list-navigation
| FOLDED
| FOLDED
| FOLDED
| FOLDED
| Test test-org-list/move-item-down backtrace:
| (if (unwind-protect (setq value-6667 (apply fn-6665 args-)) (set
| (let (form-description-6669) (if (unwind-protect (setq value-6667 (a
| (let ((value-6667 (quote ert-form-evaluation-aborted-6668))) (let (f
| (let ((fn-6665 (function org-invisible-p2)) (args- (list))) (let
| (progn (org-mode) (let ((point (string-match "" inside-text))
| (unwind-protect (progn (org-mode) (let ((point (string-match "" inside-text))
| (unwind-protect (progn (org-mode) (let ((point (string-match ":FOO: val
| :END:
| " ... ...)))
| :form
| (let
| ((org-custom-properties ...))
| (org-test-with-temp-text "* H
| :PROPERTIES:
| :FOO: val
| :END:
| "
| (org-toggle-custom-properties-visibility)
| (org-invisible-p2)))
| :value nil))
|FAILED 625/710 test-org/custom-properties
`
The forward-paragraph failrue looks like this:
,
|passed 645/710 test-org/forward-element
| Test test-org/forward-paragraph backtrace:
| (if (unwind-protect (setq value-10777 (let ((inside-text (if (string
| (let (form-description-10778) (if (unwind-protect (setq value-10777
| (let ((value-10777 (cl-gensym "ert-form-evaluation-aborted-"))) (let
| (lambda nil (let ((value-10769 (cl-gensym "ert-form-evaluation-abort
| ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
| ert-run-test([cl-struct-ert-test test-org/forward-paragraph "Test `o
| ert-run-or-rerun-test([cl-struct-ert--stats "\\(org\\|ob\\)" [[cl-st
| ert-run-tests("\\(org\\|ob\\)" #[385 "\306\307\"\203G\211\211G\310
| ert-run-tests-batch("\\(org\\|ob\\)")
| ert-run-tests-batch-and-exit("\\(org\\|ob\\)")
| (let ((org-id-track-globally t) (org-test-selector (if org-test-sele
| org-test-run-batch-tests("\\(org\\|ob\\)")
| eval((org-test-run-batch-tests org-test-select-re))
| command-line-1(("--eval" "(setq vc-handled-backends nil org-startup-
| command-line()
| normal-top-level()
| Test test-org/forward-paragraph condition:
| (ert-test-failed
| ((should
|(org-test-with-temp-text "#+BEGIN_CENTER
| P1
|
| P2
| #+END_CENTER
| P3"
|(org-hide-block-toggle)
|(org-forward-paragraph)
|(looking-at "P3")))
| :form
| (let
| ((inside-text ...)
| (org-mode-hook nil))
| (with-temp-buffer
| (org-mode)
| (let ... ...)
| (org-hide-block-toggle)
| (org-forward-paragraph)
| (looking-at "P3")))
| :value nil))
|FAILED 646/710 test-org/forward-paragraph
`
Version info:
GNU Emacs 26.0.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 3.20.9) of
2017-02-07
Org mode version 9.0.5 (release_9.0.5-260-geb59c7 @
/home/nick/elisp/org-mode/lisp/)
Note: I don't remember the last time that I ran `make test', so these may (or
may not) be
recent.
And another note: I deleted some NULs from the backtraces to keep Gnus from
asking.
--
Nick
Re: [O] Feature request: lists with letters
Hello, Rasmus writes: > Here's a quick attempt. Do you want me to push it? Thank you. Some minor comments below. Feel free to push whenever you think this is good enough. > +(defconst org-html-plain-list-type > + '(ordered "ol" unordered "ul" descriptive "dl") > + "Plist of Org and html list types.") I think this is not needed. We should merge `org-html-begin-plain-list' and `org-html-end-plain-list' into `org-html-plain-list'. There is no reason to split it. As a consequence, we can compute "ol", "ul" or "dl" at the beginning of `org-html-plain-list' and be done with it. > + (let* ((html-type (plist-get org-html-plain-list-type type)) > + (html-class (format "org-%s" html-type))) > +(format "<%s %s>" > + html-type > + (org-html--make-attribute-string > + (plist-put attributes :class > + (org-trim > + (mapconcat 'identity #'identity > + (list html-class (plist-get attributes > :class)) > + " "))) > > (defun org-html-end-plain-list (type) >"Insert the end of the HTML list depending on TYPE." > - (pcase type > -(`ordered "") > -(`unordered "") > -(`descriptive ""))) > + (format "" (plist-get org-html-plain-list-type type))) See. There is no need to make this one-liner a separate function, IMO. Regards, -- Nicolas Goaziou
Re: [O] Bug: org-dblock-update regression in case of :maxlevel 0 [9.0.5 (9.0.5-elpaplus @ c:/Users/clange/.emacs.d/elpa/org-plus-contrib-20170210/)]
Hello,
Christoph LANGE writes:
> I have a clocktable that looks as follows. (Once more, I'll be happy to
> work this out as a minimum working example – later, don't have time
> right now.)
>
> #+BEGIN: clocktable :block 2017-W01 :maxlevel 0 :scope ("filename.org")
> :indent
>
> The output I got for this from an older Org version (9.0.something,
> definitely < 9.0.4) was:
>
> | File | Headline | Time |
> |--+--+|
> | | ALL *Total time* | *1:00* |
> |--+--+|
> | filename.org | *File time* | *1:00* |
>
> :maxlevel 1 would include level-1 headings _in_ this file, like this:
>
> | File | Headline | Time |
> |--+--+|
> | | ALL *Total time* | *1:00* |
> |--+--+|
> | filename.org | *File time* | *1:00* |
> | | Task 1 | 0:05 |
> | | Task 2 | 0:55 |
>
> where filename.org looks like
>
> * Task 1
> * Task 2
> ...
>
>> It sounds like a user error to me.
>
> Maybe the truth is that the handling of :maxlevel 0 was an undocumented
> feature?
I see. It makes sense. I just couldn't find it. Thanks for the
explanation. This is now fixed.
Regards,
--
Nicolas Goaziou
Re: [O] Heads-up: test failures
Hello, Marco Wahl writes: > Nick Dokos writes: > >> I just updated to >> >> Org mode version 9.0.5 (release_9.0.5-260-geb59c7 @ >> /home/nick/elisp/org-mode/lisp/) >> >> and `make test' gives me: >> >> , >> | Ran 710 tests, 706 results as expected, 4 unexpected (2017-02-13 >> 13:41:50-0500) >> | 7 expected failures >> | >> | 4 unexpected results: >> |FAILED test-org-list/move-item-down >> |FAILED test-org-list/move-item-up >> |FAILED test-org/custom-properties >> |FAILED test-org/forward-paragraph >> ` > > I see these line also. I thought this was something crazy with my > individual settings. > > #+begin_example > Ran 704 tests, 700 results as expected, 4 unexpected (2017-02-13 > 20:32:03+0100) > 8 expected failures > > 4 unexpected results: >FAILED test-org-list/move-item-down >FAILED test-org-list/move-item-up >FAILED test-org/custom-properties >FAILED test-org/forward-paragraph > #+end_example What is the failure in each case? Regards, -- Nicolas Goaziou
Re: [O] Latex summary
On Mon, Feb 13, 2017 at 1:44 PM, Russell Adams
wrote:
> On Mon, Feb 13, 2017 at 03:14:31PM +, Eric S Fraga wrote:
>> On Monday, 13 Feb 2017 at 13:06, Russell Adams wrote:
>> > On Sun, Feb 12, 2017 at 04:30:48PM +, Eric S Fraga wrote:
>>
>> [...]
>>
>> >> Maybe use #index: ?
>> >
>> > Sorry, but do you mean in Latex or Org?
>>
>> Sorry. Not clear in my response! The #+index: is an org directly.
>>
>> "#+index: keyword" directives are then translated to LaTeX
>> \index{keyword} when exporting to PDF (say) and which can then be used
>> to create an index of keywords and page numbers using the \printindex
>> directive in LaTeX and the makeindex command to process these. You'll
>> have to modify org-latex-pdf-process to invoke makeindex or else do this
>> manually from the exported LaTeX file.
>>
>> See attached for a minimal example (org and resulting PDF).
>>
>> --
>> : Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8
>
> Eric, thanks for that really detailed input. I'll have to consider
> it. I worry that the keywords aren't like the full sentences I'm
> using.
>
> Essentially what I'm doing is like this.
>
> * Issue A
>
> ** Details
>
> lorem ipsum.
>
> /Recommendation: I would recommend that you do X/
>
> * Issue B
>
> ** Details
>
> lorem ipsum.
>
> /Recommendation: Other customers are recommended to do Y/
>
> * Conclusion
>
> #babel to grep the file for recommendations#
>
> - I would recommend that you do X
> - Other customers are recommended to do Y
>
I'm dialing in super late, but seeing this format made me think of
using inline todos for this. Could that be possible? I haven't tried a
test case, but made me think:
- insert inline todos where you have your recommendations below
- maybe use special tag or todo keyword
- create agenda view via elisp src block that could spit out the
results in your conclusions section
- I'm sure someone here could get the ID/link inserted :)
Any interest in trying something like that?
Here was some discussion about inline todos and the comments package.
Looks like Eric was in on that discussion as well!
- https://lists.gnu.org/archive/html/emacs-orgmode/2011-04/msg00190.html
John
>
>
> So essentially I'm putting a summary at the end, like a list of
> conclusions. I'm not using single words. Linking back to the section
> where the recommendation came from would be ideal.
>
> I'm trying to figure out what this would be called, so I can check the
> Latex libraries. I expect it's fairly common, but that I'm using a
> poor choice of words to describe it.
>
>
>
> --
> Russell Adamsrlad...@adamsinfoserv.com
>
> PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
>
> Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
>
Re: [O] Latex summary
On Mon, Feb 13, 2017 at 03:14:31PM +, Eric S Fraga wrote:
> On Monday, 13 Feb 2017 at 13:06, Russell Adams wrote:
> > On Sun, Feb 12, 2017 at 04:30:48PM +, Eric S Fraga wrote:
>
> [...]
>
> >> Maybe use #index: ?
> >
> > Sorry, but do you mean in Latex or Org?
>
> Sorry. Not clear in my response! The #+index: is an org directly.
>
> "#+index: keyword" directives are then translated to LaTeX
> \index{keyword} when exporting to PDF (say) and which can then be used
> to create an index of keywords and page numbers using the \printindex
> directive in LaTeX and the makeindex command to process these. You'll
> have to modify org-latex-pdf-process to invoke makeindex or else do this
> manually from the exported LaTeX file.
>
> See attached for a minimal example (org and resulting PDF).
>
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8
Eric, thanks for that really detailed input. I'll have to consider
it. I worry that the keywords aren't like the full sentences I'm
using.
Essentially what I'm doing is like this.
* Issue A
** Details
lorem ipsum.
/Recommendation: I would recommend that you do X/
* Issue B
** Details
lorem ipsum.
/Recommendation: Other customers are recommended to do Y/
* Conclusion
#babel to grep the file for recommendations#
- I would recommend that you do X
- Other customers are recommended to do Y
So essentially I'm putting a summary at the end, like a list of
conclusions. I'm not using single words. Linking back to the section
where the recommendation came from would be ideal.
I'm trying to figure out what this would be called, so I can check the
Latex libraries. I expect it's fairly common, but that I'm using a
poor choice of words to describe it.
--
Russell Adamsrlad...@adamsinfoserv.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: [O] Heads-up: test failures
Nick Dokos writes: > I just updated to > > Org mode version 9.0.5 (release_9.0.5-260-geb59c7 @ > /home/nick/elisp/org-mode/lisp/) > > and `make test' gives me: > > , > | Ran 710 tests, 706 results as expected, 4 unexpected (2017-02-13 > 13:41:50-0500) > | 7 expected failures > | > | 4 unexpected results: > |FAILED test-org-list/move-item-down > |FAILED test-org-list/move-item-up > |FAILED test-org/custom-properties > |FAILED test-org/forward-paragraph > ` I see these line also. I thought this was something crazy with my individual settings. #+begin_example Ran 704 tests, 700 results as expected, 4 unexpected (2017-02-13 20:32:03+0100) 8 expected failures 4 unexpected results: FAILED test-org-list/move-item-down FAILED test-org-list/move-item-up FAILED test-org/custom-properties FAILED test-org/forward-paragraph #+end_example As Nicolas pointed out these failures don't show in the CI-build at http://www.randomsample.de:4457/waterfall. FWIW my environment: - (version): "GNU Emacs 26.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.22.7) of 2017-02-09" - Actually it's Arch-Linux. - Recent Org master. My 2 ct to HTH with this issue Marco
[O] Heads-up: test failures
I just updated to Org mode version 9.0.5 (release_9.0.5-260-geb59c7 @ /home/nick/elisp/org-mode/lisp/) and `make test' gives me: , | Ran 710 tests, 706 results as expected, 4 unexpected (2017-02-13 13:41:50-0500) | 7 expected failures | | 4 unexpected results: |FAILED test-org-list/move-item-down |FAILED test-org-list/move-item-up |FAILED test-org/custom-properties |FAILED test-org/forward-paragraph ` -- Nick
Re: [O] Latex summary
On Monday, 13 Feb 2017 at 13:06, Russell Adams wrote:
> On Sun, Feb 12, 2017 at 04:30:48PM +, Eric S Fraga wrote:
[...]
>> Maybe use #index: ?
>
> Sorry, but do you mean in Latex or Org?
Sorry. Not clear in my response! The #+index: is an org directly.
"#+index: keyword" directives are then translated to LaTeX
\index{keyword} when exporting to PDF (say) and which can then be used
to create an index of keywords and page numbers using the \printindex
directive in LaTeX and the makeindex command to process these. You'll
have to modify org-latex-pdf-process to invoke makeindex or else do this
manually from the exported LaTeX file.
See attached for a minimal example (org and resulting PDF).
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8
#+LaTeX_HEADER: \usepackage{makeidx} \makeindex
* Introduction
#+index: introduction
This is the start of the document.
\newpage
* Main contents
#+index: contents
Blah blah blah.
* Conclusions
#+index: conclusion
We conclude the document here.
\newpage
\printindex
t.pdf
Description: Adobe PDF document
signature.asc
Description: PGP signature
Re: [O] Merge 9.0.5 to emacs master?
Rasmus writes: [...] > I think we have discussed it before, but the best way seems to just copy > the Org tree to the Emacs tree, right? Given the current setup, I think copying the files is best. I've already resolved the conflicts when backporting Org-related commits from the Emacs repo. -- Kyle
Re: [O] Fontification error
Hello, "Thomas S. Dye" writes: > I get fontification error messages when loading Org mode files since > upgrading this morning. > > org-mode fontification error in # at 685 > > Org mode version 9.0.5 (9.0.5-elpaplus @ > /Users/dk/.emacs.d/elpa/org-plus-contrib-20170210/) > > Let me know if you have questions. I cannot reproduce it. Could you provide an ECM? Regards, -- Nicolas Goaziou
Re: [O] Merge 9.0.5 to emacs master?
Kyle Meyer writes: > Hi Bastien, > > Bastien Guerry writes: > >> Kyle Meyer writes: >> >>> Kaushal Modi writes: >>> Kyle -- Would this be a good time to start the merge to emacs master? >>> From my standpoint, that'd be fine. I'm not aware of any outstanding >>> patches that need to be backported from the Emacs repo. >> >> Before undertaking this, we need to make sure the Emacs maintainers >> are fine with it -- I'm late in reading the related discussions. >> >> Can you wait a few days for my "go" ? > > I'll do better than that and wait indefinitely since the plan isn't for > me to do the syncing :) I also haven't caught up with all the messages about sync the "new" plans. AFAIR Eli said to go ahead in one of the early messages. > I also mentioned [*2*] that I had created a branch, emacs-sync, in the > Org repo that contains a few extra changes that I think are appropriate > for the sync. That branch is up-to-date with 9.0.5. I think we have discussed it before, but the best way seems to just copy the Org tree to the Emacs tree, right? Rasmus -- Summon the Mothership!
[O] Fontification error
Aloha all, I get fontification error messages when loading Org mode files since upgrading this morning. org-mode fontification error in # at 685 Org mode version 9.0.5 (9.0.5-elpaplus @ /Users/dk/.emacs.d/elpa/org-plus-contrib-20170210/) Let me know if you have questions. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Feature request: lists with letters
Nicolas Goaziou writes: > Hello, > > Rasmus writes: > >> IOW the problems are all fairly easy to deal with once we've added :style >> and :class support to more places in ox-html. > > Great. Would you, or anyone else, be interested in working on this? Here's a quick attempt. Do you want me to push it? Rasmus -- Bang bang >From 0760016f2b100f4050e16f5682eca305178f3494 Mon Sep 17 00:00:00 2001 From: Rasmus Date: Mon, 13 Feb 2017 17:52:38 +0100 Subject: [PATCH] ox-html: plain list supports arbitrary attributes * lisp/ox-html.el (org-html-plain-list-type): New defconst. (org-html-begin-plain-list): (org-html-plain-list): (org-html-end-plain-list): Use new defconst and support attributes. --- lisp/ox-html.el | 37 + 1 file changed, 21 insertions(+), 16 deletions(-) diff --git a/lisp/ox-html.el b/lisp/ox-html.el index ef8c9b546..1f3def999 100644 --- a/lisp/ox-html.el +++ b/lisp/ox-html.el @@ -449,6 +449,10 @@ You can use `org-html-head' and `org-html-head-extra' to add to this style. If you don't want to include this default style, customize `org-html-head-include-default-style'.") +(defconst org-html-plain-list-type + '(ordered "ol" unordered "ul" descriptive "dl") + "Plist of Org and html list types.") + ;;; User Configuration Variables @@ -3138,34 +3142,35 @@ the plist used as a communication channel." Plain List -;; FIXME Maybe arg1 is not needed because already sets -;; the correct value for the item counter -(defun org-html-begin-plain-list (type &optional arg1) +(defun org-html-begin-plain-list (type &optional attributes) "Insert the beginning of the HTML list depending on TYPE. When ARG1 is a string, use it as the start parameter for ordered lists." - (pcase type -(`ordered - (format "" - (if arg1 (format " start=\"%d\"" arg1) ""))) -(`unordered "") -(`descriptive ""))) + (let* ((html-type (plist-get org-html-plain-list-type type)) + (html-class (format "org-%s" html-type))) +(format "<%s %s>" + html-type + (org-html--make-attribute-string + (plist-put attributes :class + (org-trim + (mapconcat 'identity +(list html-class (plist-get attributes :class)) +" "))) (defun org-html-end-plain-list (type) "Insert the end of the HTML list depending on TYPE." - (pcase type -(`ordered "") -(`unordered "") -(`descriptive ""))) + (format "" (plist-get org-html-plain-list-type type))) (defun org-html-plain-list (plain-list contents _info) "Transcode a PLAIN-LIST element from Org to HTML. CONTENTS is the contents of the list. INFO is a plist holding contextual information." - (let ((type (org-element-property :type plain-list))) + (let* ((type (org-element-property :type plain-list)) + (attributes (org-export-read-attribute :attr_html plain-list))) (format "%s\n%s%s" - (org-html-begin-plain-list type) - contents (org-html-end-plain-list type + (org-html-begin-plain-list type attributes) + contents + (org-html-end-plain-list type Plain Text -- 2.11.1
Re: [O] Merge 9.0.5 to emacs master?
Hi Bastien, Bastien Guerry writes: > Kyle Meyer writes: > >> Kaushal Modi writes: >> >>> Kyle -- Would this be a good time to start the merge to emacs master? >> >>>From my standpoint, that'd be fine. I'm not aware of any outstanding >> patches that need to be backported from the Emacs repo. > > Before undertaking this, we need to make sure the Emacs maintainers > are fine with it -- I'm late in reading the related discussions. > > Can you wait a few days for my "go" ? I'll do better than that and wait indefinitely since the plan isn't for me to do the syncing :) To give a bit more context to Kaushal's question, when he asked the list previously [*1*] about syncing 9.0.4 with the Emacs repo, I replied [*2*, *3*] that we should wait for the next release because there were Emacs commits that still needed to be backported, as well as white space touch-ups that were needed in order for the Org files to pass Emacs's pre-commit check. I also mentioned [*2*] that I had created a branch, emacs-sync, in the Org repo that contains a few extra changes that I think are appropriate for the sync. That branch is up-to-date with 9.0.5. [*1*] https://lists.gnu.org/archive/html/emacs-orgmode/2017-01/msg00551.html [*2*] https://lists.gnu.org/archive/html/emacs-orgmode/2017-01/msg00571.html [*3*] https://lists.gnu.org/archive/html/emacs-orgmode/2017-01/msg00584.html -- Kyle
Re: [O] Bug: org-dblock-update regression in case of :maxlevel 0 [9.0.5 (9.0.5-elpaplus @ c:/Users/clange/.emacs.d/elpa/org-plus-contrib-20170210/)]
Hi Nicolas,
Nicolas Goaziou on 2017-02-13 16:46:
> I can reproduce the problem. However, I'm not sure to understand the
> meaning of ":maxlevel 0". Don't you mean ":maxlevel 1"?
I have a clocktable that looks as follows. (Once more, I'll be happy to
work this out as a minimum working example – later, don't have time
right now.)
#+BEGIN: clocktable :block 2017-W01 :maxlevel 0 :scope ("filename.org")
:indent
The output I got for this from an older Org version (9.0.something,
definitely < 9.0.4) was:
| File | Headline | Time |
|--+--+|
| | ALL *Total time* | *1:00* |
|--+--+|
| filename.org | *File time* | *1:00* |
:maxlevel 1 would include level-1 headings _in_ this file, like this:
| File | Headline | Time |
|--+--+|
| | ALL *Total time* | *1:00* |
|--+--+|
| filename.org | *File time* | *1:00* |
| | Task 1 | 0:05 |
| | Task 2 | 0:55 |
where filename.org looks like
* Task 1
* Task 2
...
> It sounds like a user error to me.
Maybe the truth is that the handling of :maxlevel 0 was an undocumented
feature?
Cheers,
Christoph
--
Dr. Christoph Lange, Enterprise Information Systems Department
Applied Computer Science @ University of Bonn; Fraunhofer IAIS
http://langec.wordpress.com/about, Skype duke4701
Re: [O] Release 9.0.5
Hello, Fabrice Popineau writes: > This one is about the file system which behaves differently under Windows : > > F test-org-export/file-uri > Test ‘org-export-file-uri’ specifications. > (ert-test-failed > ((should >(equal "file:///local.org" > (org-export-file-uri "/local.org"))) > :form > (equal "file:///local.org" "file://d:/local.org") > :value nil :explanation > (arrays-of-different-length 17 19 "file:///local.org" "file://d:/ > local.org" first-mismatch-at 7))) > > The absolute path has the drive name. So actually not a failure. Ok. I rewrote the equality test. Hopefully, it should pass on your system. > F test-org-pcomplete/keyword > Test keyword and block completion. > (ert-test-failed > ((should >(equal "#+startup: " > (org-test-with-temp-text "#+start" > (pcomplete) > (buffer-string > :form > (equal "#+startup: " "#+STARTUP: ") > :value nil :explanation > (array-elt 2 > (different-atoms > (115 "#x73" "?s") > (83 "#x53" "?S") > > This one is because pcomplete is used to get completion, and the completion > depends on > the pcomplete-ignore-case variable, which makes pcomplete ignore case for > windows-nt and cygwin by default. I also fixed it. > The last one is strange: > > F test-org-element/link-parser > Test ‘link’ parser. > (ert-test-failed > ((should >(equal "id" > (org-test-with-temp-text "[[id:]]" > (org-element-property :type ... > :form > (equal "id" "fuzzy") > :value nil :explanation > (arrays-of-different-length 2 5 "id" "fuzzy" first-mismatch-at 0))) I removed this particular test. "id" links are non-standard (i.e., they need you to require Org ID library). Such a test should go in "test-org-id.el", which doesn't exist yet. > This is complete non sense, because when I evaluate the test form, I > actually get "id" and I have > no idea where this "fuzzy" may come from. A "fuzzy" link is a link with no default type, per `org-link-parameters'. It probably means `org-id' wasn't loaded at the time of the test. > Do you also get a warning like this: > Making org-entities-user local to *temp*-443480 while let-bound! > in the *Messages* buffer ? I don't. Could you confirm tests are passing now? Thank you. Regards, -- Nicolas Goaziou
Re: [O] Bug: org-dblock-update regression in case of :maxlevel 0 [9.0.5 (9.0.5-elpaplus @ c:/Users/clange/.emacs.d/elpa/org-plus-contrib-20170210/)]
Hello, Christoph LANGE writes: > I believe the following fix > > http://orgmode.org/w/?p=org-mode.git;a=commitdiff;h=ccf832e8317dbac7d3ac2b7dfbb515b1292a329c > > introduced a regression. When I want to run org-dblock-update on a > clocktable with :maxlevel 0 (I'll be happy to provide an example), it > fails with > > Debugger entered--Lisp error: (wrong-type-argument wholenump -1) > make-string(-1 124) > > in org-clocktable-write-default, I think in > > (make-string (1- (min maxlevel (or ntcol 100))) ?|) > > to be exact, because (1- maxlevel) is -1. I can reproduce the problem. However, I'm not sure to understand the meaning of ":maxlevel 0". Don't you mean ":maxlevel 1"? It sounds like a user error to me. Regards, -- Nicolas Goaziou
Re: [O] Bug: transposition of words surrounded by forward slash [9.0.5 (release_9.0.5-266-gca31fa )]
Hello, Justin Kirby writes: > An org file with the following content: > > #+OPTIONS: *:nil > > /simple/ /example/ > > > > During export org will transpose the word 'example' so the final output is > > //examplesimple/ / > > > > This will be the output regardless of export format. I have tried html, > txt, odt, md. > > The words will be transposed as long as they are on the same line, > regardless of how many characters are between them. > > This was observed as early as org 8.3.5. > > Changing the italic character in org-emphasis-alist to | does not change > this behavior. Fixed. Thank you. Regards, -- Nicolas Goaziou
Re: [O] Latex summary
"directive", not "directly"... -- : Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8 signature.asc Description: PGP signature
Re: [O] Bug: Preserve text-properties of cells when moving column in org-table
Hello, "Stefan-W. Hahn" writes: > moving org-table rows is implemented with delete-region and insert which > preserve text-properties. Moving org-table columns is implemented > with replace-string, which removes text-properties. > > My proposal is to use transpose-regions in org-table-move-column which > will preserve text-properties when moving columns in org-tables. Applied. Thank you. Regards, -- Nicolas Goaziou
Re: [O] How to change "References" headline in pdf with org-ref?
I think this is done in latex. Here are a few pointers that might get you
what you want. It seems there is more than one way to do it that depends on
your setup and which packages you use.
http://tex.stackexchange.com/questions/17445/how-can-i-change-the-references-to-reference-in-the-thebibliography-environm
http://tex.stackexchange.com/questions/12597/renaming-the-bibliography-page-using-bibtex
This worked for me:
#+latex: \renewcommand{\refname}{Whatever floats your boat}
John
---
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
On Mon, Feb 13, 2017 at 8:07 AM, Nikolai Stenfors <
nikolai.stenf...@bahnhof.se> wrote:
> When I export a text with references into pdf, the default
> headline for the reference-chapter is "References". How do I change the
> title/headline? A specific org-ref-variable?
> --
> Nikolai Stenfors
>
>
>
[O] [ANN] New Org duration library
Hello, * TL;DR; `org-time-clocksum-format', `org-time-clocksum-use-fractional' and `org-time-clocksum-fractional-format' are obsolete. If you changed them, consider modifying ~org-duration-format~ instead. Variable `org-time-clocksum-use-effort-durations' is also obsolete. Consider setting `org-duration-units' instead. * Rationale In current stable version, time duration handling is unsatisfactory: - There are overlapping and confusing functions: `org-minutes-to-clocksum-string', `org-hh:mm-string-to-minutes' and `org-duration-string-to-minutes'. - Duration format is powerful but complex to handle since there are four variables involved: `org-time-clocksum-format', `org-time-clocksum-use-fractional', `org-time-clocksum-fractional-format' and `org-time-clocksum-use-effort-durations'. - More importantly, if you set that format to something fancy, it is not possible anymore to read the produced string back. Therefore, I implemented and merged a simple "duration" library that takes care of reading and producing such durations. Quoting the file's commentary: This library provides tools to manipulate durations. A duration can have multiple formats: - 3:12 - 1:23:45 - 1y 3d 3h 4min - 3d 13:35 - 2.35h More accurately, it consists of numbers and units, as defined in variable `org-duration-units', separated with white spaces, and a "H:MM" or "H:MM:SS" part. White spaces are tolerated between the number and its relative unit. Variable `org-duration-format' controls durations default representation. The library provides functions allowing to convert a duration to, and from, a number of minutes: `org-duration-to-minutes' and `org-duration-from-minutes'. It also provides two lesser tools: `org-duration-p', and `org-duration-h:mm-only-p'. Users can set the number of minutes per unit, or define new units, in `org-duration-units'. The library also supports canonical duration, i.e., a duration that doesn't depend on user's settings, through optional arguments. At the cost of some incompatibilities if you introduced some fancy duration format, and a slightly more limited choice of representation, we get a more consistent and sturdy interface. * About base unit design choice The base unit for a duration is the minute. I hesitated with the more natural second but - Org time precision is the minute, - `org-duration-to-minutes' and `org-duration-from-minutes' can be drop-in replacements for the functions quoted above, - We would need to handle floats anyway as we don't require custom units to be multiple of the base unit. Feedback welcome. Regards, -- Nicolas Goaziou0x80A93738
Re: [O] Feature request: lists with letters
Hello, Rasmus writes: > IOW the problems are all fairly easy to deal with once we've added :style > and :class support to more places in ox-html. Great. Would you, or anyone else, be interested in working on this? Regards, -- Nicolas Goaziou
[O] How to change "References" headline in pdf with org-ref?
When I export a text with references into pdf, the default headline for the reference-chapter is "References". How do I change the title/headline? A specific org-ref-variable? -- Nikolai Stenfors
Re: [O] Latex summary
On Sun, Feb 12, 2017 at 04:30:48PM +, Eric S Fraga wrote: > On Sunday, 12 Feb 2017 at 00:16, Russell Adams wrote: > > I frequently write documentation with recommendations nested in > > different sections, typically one line per recommendation. I then > > summarize a list of those recommendations at the end of my document. > > > > Today I use babel to grep the document for my recommendation format, > > but given I'm exporting to Latex can anyone suggest a better method? > > Something like a reversed table of contents? > > Maybe use #index: ? Sorry, but do you mean in Latex or Org? -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: [O] Latex summary
Hi Russell. > I frequently write documentation with recommendations nested in > different sections, typically one line per recommendation. I then > summarize a list of those recommendations at the end of my document. > Today I use babel to grep the document for my recommendation format, > but given I'm exporting to Latex can anyone suggest a better method? > Something like a reversed table of contents? A reversed ToC seems perfect, since it will give you also a link to the original place where it is developed. I do use LaTex from Org so I'm not any expert, but I believe that this "Add an item in the table of contents" in StackExchange may be useful. http://tex.stackexchange.com/questions/119719/add-an-item-in-the-table-of-contents Best... -- eduardo mercovich Donde se cruzan tus talentos con las necesidades del mundo, ahí está tu vocación. (Anónimo)
Re: [O] Feature request: lists with letters
Hi, > #+attr_html: some clever code which I don't know. Probably `org-html-begin-plain-list' would need to patched to accept :class or :style. In general it might be nicer to accept those in more places. Then one could do either "#+attr_html: :class alpha" (with corresponding css) or "#+attr_html: :style list-style-type: lower-alpha;". For html in particular, one would need to change the reference label in the output to match the type of the list. E.g. if <> is an lower-alpha type the textContent of [[ref]] must be adjusted. This is just how html is. JS could solve it at display-time, of one could use a filter to add the right label (shouldn't be too hard as the item element already have a :bullet in the plist). One could also use a prep. filter to add the correct #+attr_ lines at the necessary places. IOW the problems are all fairly easy to deal with once we've added :style and :class support to more places in ox-html. Rasmus -- Dobbelt-A
Re: [O] Merge 9.0.5 to emacs master?
Hi Kyle, Kyle Meyer writes: > Kaushal Modi writes: > >> Kyle -- Would this be a good time to start the merge to emacs master? > >>From my standpoint, that'd be fine. I'm not aware of any outstanding > patches that need to be backported from the Emacs repo. Before undertaking this, we need to make sure the Emacs maintainers are fine with it -- I'm late in reading the related discussions. Can you wait a few days for my "go" ? Thanks, -- Bastien
