Re: [O] org-mode vs pandoc export

[CHARPENTIER Emmanuel]

1) I just checked: I was incorrect, Pythontex now has complete support
for R language. One can now use it for processing \LaTeX files
including Sage, R (and of course, Python) chunks.

2) Please, DO NOT include "images of a table" in a scientific document!
Lazy students pull this one on me in their manuscripts, and it's a
pain: you can't do a thing with such horrors, and you have to retype
manually these data if you want to work on them...

3) Did you try the route org-->LaTeX-->WhateverViaPandoc suggested by
John Kitchin ?

--
Emmanuel Charpentier

PS: I'm surprised that a philosophy journal does not accept \LaTeX
submissions: formal mathematics have been part of the philosophical
toolbox for a long while (since about 700 BC IIRC...).

Re: [O] org-mode vs pandoc export

[Joseph Vidal-Rosset]

Hello,

Many thanks Emmanuel for your help.

Indeed, I'm  using org-ref and scimax, all the  nice tools that
John offers very  generously to the community; org-ref  is so convenient
that  now I  cannot  imagine to  work  without it.  Maybe  John has  the
solution for future exports. (I did not succeed to export in odt because
of links, bibliography links.)

Finally the best result was done directly via pandoc, via a command line
like this one:

pandoc -s --filter pandoc-crossref --bibliography=reforg.bib --csl=ieee.csl -o 
mydocument.odt mydocument.org

But pandoc-crossref never  worked and I had also to  make png images for
tables.

The best  solution that I  found was to install  libreoffice-texmaths. I
just had  to enter "sudo  aptitude install libreoffice-texmaths"  via my
GNU/Linux Debian sid, but for other OS, the package is here

https://extensions.libreoffice.org/extensions/texmaths-1

and it works.

Of course the output is less pretty than the pdf via the tex life

I hope that it will help other people.

Best wishes,

Jo.

PS: The publisher is in philosophy... 

Re: [O] org-mode vs pandoc export

[Emmanuel Charpentier]

I suppose that you need org-mode to use Babel features (code and/or
code execution results intermixed with your paper's text).

I have had trouble with .dot exporting using the builtin .dot exporter,
but can't, for the life of me, remembering if my troubles were cross-
reference or citations-related (an academic paper usually needs
both...). I noted that the references done via John Kitchin's excellent
org-ref didn't export to .dot.

As far as I can tell, ox-pandoc does its own numbering (generating an
intermediate temporary file that I never managed to catch) and does not
use  pandoc-crossref.

ISTR that a "clever" use of org-ref allows to number equations... in
LaTeX output. I also STR that it doesn't work in .docx output. John
Kitchin (the org-ref author) thinks that the key is to generate a
correct \LaTeX file and to export that to .docx via pandoc.

At this point, writing a \LaTeX file with pandoc export in mind is
probably your best bet. There exist (limited) alternatives to the 
Babel features of org-mode:
 - knitr (supports R and Python code in "session"mode, i. e. continuity
between code chunks),
 - SageTeX (post-processing in a single Sagemath run ; can include code
for a variety of math software, including R),
 - Pythontex (postprocessor, supports Python, Sage, Octave and a couple
other, but not R ; a clever use of knitr and Pythontex is possible).

Possible alternative: Markdown + Codebraid (supports a hanful of
langiages, including R and (development branch) Sage). This should
accept pandoc-crossref numbering. But it's Markdown, with limited
formatting abilities...

So, we have an array of partial solutions, none universal. Pick your
poison...

Out of curiosity: in which domain still exist journal publishers not
accepting \LaTeX ? I suspect medicine...

HTH,

--
Emmanuel Charpentier

Re: [O] Org - mode manual missing

[Fraga, Eric]

On Wednesday, 18 Sep 2019 at 17:17, Logan Lee wrote:
> My emacs doesn't come with org-mode manual.
> C-h i m then org TAB produces nothing.

How did you install org (and what version)?
-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.2.4-401-gfabd6d

Re: [O] Org mode pollutes the narrow-map

[Omar Antolín Camarena]

Great, thanks!

On Fri, Aug 23, 2019, 3:40 AM Nicolas Goaziou 
wrote:

> Hello,
>
> Omar Antolín Camarena  writes:
>
> > Hello everyone,
> >
> > Does it seems a little rude that Org mode binds its own narrowing
> commands in the global narrow-map?
> >
> > You can find this in org.el starting at line 19018:
> >
> > #+begin_src emacs-lisp
> >    Narrow map
> >   (org-defkey narrow-map "s" #'org-narrow-to-subtree)
> >   (org-defkey narrow-map "b" #'org-narrow-to-block)
> >   (org-defkey narrow-map "e" #'org-narrow-to-element)
> > #+end_src
> >
> > I don't need or really want those commands bound in non-org buffers.
> > I think it would be better to bind them (to C-x n s, C-x n b and C-x
> > n e) in org-mode-map. This is the approach taken by AUCTeX, for
> > example. (To be clear, I mean AUCTeX has some narrowing commands and
> > it binds them to C-x n e and C-x n g in its own keymaps.)
>
> It sounds reasonable. I changed the bindings in master. Thank you.
>
> Regards,
>
> --
> Nicolas Goaziou
>

Re: [O] Org mode pollutes the narrow-map

[Nicolas Goaziou]

Hello,

Omar Antolín Camarena  writes:

> Hello everyone,
>
> Does it seems a little rude that Org mode binds its own narrowing commands in 
> the global narrow-map?
>
> You can find this in org.el starting at line 19018:
>
> #+begin_src emacs-lisp
>    Narrow map
>   (org-defkey narrow-map "s" #'org-narrow-to-subtree)
>   (org-defkey narrow-map "b" #'org-narrow-to-block)
>   (org-defkey narrow-map "e" #'org-narrow-to-element)
> #+end_src
>
> I don't need or really want those commands bound in non-org buffers.
> I think it would be better to bind them (to C-x n s, C-x n b and C-x
> n e) in org-mode-map. This is the approach taken by AUCTeX, for
> example. (To be clear, I mean AUCTeX has some narrowing commands and
> it binds them to C-x n e and C-x n g in its own keymaps.)

It sounds reasonable. I changed the bindings in master. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] Org-mode latex pdf export issue: Underlined lines not breaking properly

[Gustavo Barros]

On Mon, Jul 29 2019, Gustavo Barros wrote:



But the ability to have line breaks is a clear edge
of soul, and the reason of the original request which started this
thread.



I must correct myself, the difference between ulem and soul is not that 
one allows line breaks while the other does not.  More precisely, both 
handle line breaks, but soul is able to honor hyphenation patterns, 
while ulem is not.  If one wants a (underlined/stricken-through) word to 
break with ulem, the hyphenation has to be done manually.


Best,
Gustavo.

Re: [O] Org-mode latex pdf export issue: Underlined lines not breaking properly

[Gustavo Barros]

Hi all,

On Fri, Jun 14 2013, Nicolas Goaziou wrote:

 Nicolas Goaziou  writes:
>   1. Does \underline{中文测试} work properly (notwithstanding the line
>  breaks)?

 \underline can show chinese, but the command can't resolve lines
 breaking properly.

>   2. Does \uline from "ulem" package handle it correctly, including the
>  line breaks?

 \uline seem to work properly.
>>>
>>> Then, the best solution seems to add "ulem" package to
>>> `org-latex-default-packages-alist' and use \ulem for underline. "soul"
>>> will only be used for strike-through.
>>>
>>> Is there any objection to this change?
>>
>> May be \ulem should be used for strike-through too!
>
> Done.
>

I know this is a very old thread, and that perhaps this boat has sailed
definitely.

But it seems to me that the attempt to use soul back then eventually
backfired because soul does not handle utf8 properly, as Feng Shu’s
issue demonstrated.  Indeed it does not.  But there is a patch to soul,
by Heiko Oberdiek, to handle this precise issue, and it is the package
soulutf8.

I’ve checked the commit history around the time of this thread, and it
seems soul, rather than soulutf8, was the attempt
(https://code.orgmode.org/bzg/org-mode/commit/95eeefa9bca1b6c57fe62c248a0a35302cd7374d).

Neither soul nor ulem is very active nowadays, but are used quite
extensively, as far as I know (from following TeX.SX).  And both have
their limitations.  But the ability to have line breaks is a clear edge
of soul, and the reason of the original request which started this
thread.

So, if the only reason to prefer ulem back in 2013 was utf8 support,
perhaps soulutf8 might be worthy of your reconsideration.


Best regards,
Gustavo Barros.

Re: [O] org-mode table element selection WITH blanks elements

[Nick Dokos]

This was posted on the Emacs SE and I replied there:

   
https://emacs.stackexchange.com/questions/51141/org-mode-table-element-selection-with-blanks
   
-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

Re: [O] Org mode 9.2 breaks org-edit-special on INCLUDE statement with :only-contents t

[Nicolas Goaziou]

Hello,

Joon Ro  writes:

> After upgrading to org 9.2, I found that C-c ' (org-edit-special) does not 
> work on an INCLUDE statement if it has :only-contents t.
>
> That is, I can normally visit the subtree with CUSTOM_ID theory in paper.org 
> if I press C-c ' on the following:
>
> #+INCLUDE: "./paper.org::#theory"
>
> but pressing C-c ' on the following gives me this error: "org-open-file: No 
> match for custom ID: theory" :only-contents t"
>
> #+INCLUDE: "./paper.org::#theory" :only-contents t
>
> Looks like parsing the statement was not working -- it seems it is
> capturing stuff after ".

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] org-mode export behavior change in 9.2?

[Berry, Charles]

> On Jan 12, 2019, at 1:33 PM, Haider Rizvi  wrote:
> 
> "Berry, Charles"  writes:
> 
>>> On Jan 11, 2019, at 5:03 PM, Haider Rizvi  wrote:
>>> 
>>> I've been using literate programming approach with org-babel for a
>>> while. I just noticed that with 9.2, when I try to export (c-c c-e h
>>> o) an org doc / section, any shell blocks with a named session are
>>> executed as it is exporting to html!
>>> 
>>> I don't think it was this way before?
>> 
>> 
>> AFAICS, nothing has changed in the way :session is handled for shell src 
>> blocks in a very
>> long time.
>> 
>> Perhaps, you had set `:eval never-export' previously, but not now. ??
>> 
>>> Is there a way to not have it
>>> execute each shell block when trying to export.
>> 
>> This seems to work as you would want:
>> 
>> #+begin_src shell :session sh-pcnw3 :eval never-export
>> /usr/bin/say something # say it out loud!
>> #+end_src
>> 
>> 
>> If you can identify a release in which the behavior was as you said, it 
>> might be possible to
>> dig deeper.
> 
> Chuck, thanks for responding.
> 
> I've never had the never-export set. I'll try to go back and pinpoint
> when the change shows up if I can.
> 
> Is the difference between named session and without it expected? With
> the named session, the block is executed on export, and without it, it
> is not executed!


With the default `:exports code' (your case) or with `:exports none' the 
difference is expected. You can read `org-babel-exp-do-export' for details.

If I were you I wouldn't spend much time trying to run this down.  I'd just use 
`:eval never-export'.  It seems like that is the behavior you want.


Chuck

Re: [O] org-mode export behavior change in 9.2?

[Haider Rizvi]

"Berry, Charles"  writes:

>> On Jan 11, 2019, at 5:03 PM, Haider Rizvi  wrote:
>> 
>> I've been using literate programming approach with org-babel for a
>> while. I just noticed that with 9.2, when I try to export (c-c c-e h
>> o) an org doc / section, any shell blocks with a named session are
>> executed as it is exporting to html!
>> 
>> I don't think it was this way before?
>
>  
> AFAICS, nothing has changed in the way :session is handled for shell src 
> blocks in a very
> long time.
>
> Perhaps, you had set `:eval never-export' previously, but not now. ??
>
>>  Is there a way to not have it
>> execute each shell block when trying to export.
>
> This seems to work as you would want:
>
> #+begin_src shell :session sh-pcnw3 :eval never-export
> /usr/bin/say something # say it out loud!
> #+end_src
>
>
> If you can identify a release in which the behavior was as you said, it might 
> be possible to
> dig deeper.

Chuck, thanks for responding.

I've never had the never-export set. I'll try to go back and pinpoint
when the change shows up if I can.

Is the difference between named session and without it expected? With
the named session, the block is executed on export, and without it, it
is not executed!

-- 

Re: [O] org-mode export behavior change in 9.2?

[Berry, Charles]

> On Jan 11, 2019, at 5:03 PM, Haider Rizvi  wrote:
> 
> I've been using literate programming approach with org-babel for a
> while. I just noticed that with 9.2, when I try to export (c-c c-e h
> o) an org doc / section, any shell blocks with a named session are
> executed as it is exporting to html!
> 
> I don't think it was this way before?

 
AFAICS, nothing has changed in the way :session is handled for shell src blocks 
in a very long time. 

Perhaps, you had set `:eval never-export' previously, but not now. ??

>  Is there a way to not have it
> execute each shell block when trying to export.

This seems to work as you would want:

#+begin_src shell :session sh-pcnw3 :eval never-export
/usr/bin/say something # say it out loud!
#+end_src


If you can identify a release in which the behavior was as you said, it might 
be possible to dig deeper.

HTH,

Chuck

Re: [O] Org mode repeated dates to do spaced learning

[Marcin Borkowski]

On 2019-01-06, at 18:17, Andrea Giugliano  wrote:

> Hi there,
>
> That was a very helpful suggestion. At the bottom of the mail I attached

Glad to have helped!

Best,

-- 
Marcin Borkowski
http://mbork.pl

Re: [O] Org mode repeated dates to do spaced learning

[Andrea Giugliano]

Hi there,

That was a very helpful suggestion. At the bottom of the mail I attached
my first (working) stab at it.

The idea is to have an headline with the :spaced: tag and another tag
maintaining the number of repetition performed so far. At the beginning
I was thinking to use scheduled times instead of a "counter" tag, but it
was not worth the complexity of the code.

If anybody else finds this feature useful, what would be the best way
to share this?

#+begin_src elisp
(defun my/space-repeat-if-tag-spaced (e)
  "Resets the header on the TODO states and increases the scheduled date
according to a suggested spaced repetition interval."
  (let* ((spaced-rep-map '((0 . "++1d")
  (1 . "++2d")
  (2 . "++10d")
  (3 . "++30d")
  (4 . "++60d")
  (5 . "++4m")))
 (spaced-key "spaced")
 (tags (org-get-tags nil t))
 (spaced-todo-p (member spaced-key tags))
 (repetition-n (first (cdr spaced-todo-p)))
 (n+1 (if repetition-n (+ 1 (string-to-number (substring repetition-n 
(- (length repetition-n) 1) (length repetition-n 0))
 (spaced-repetition-p (alist-get n+1 spaced-rep-map))
 (new-repetition-tag (concat "repetition" (number-to-string n+1)))
 (new-tags (reverse (if repetition-n
(seq-reduce
 (lambda (a x) (if (string-equal x 
repetition-n) (cons new-repetition-tag a) (cons x a)))
 tags
 '())
  (seq-reduce
   (lambda (a x) (if (string-equal x spaced-key) 
(cons new-repetition-tag (cons x a)) (cons x a)))
   tags
   '())
(if (and spaced-todo-p spaced-repetition-p)
  (progn
  ;; avoid infinitive looping
  (remove-hook 'org-trigger-hook 'my/space-repeat-if-tag-spaced)
  ;; reset to previous state
  (org-call-with-arg 'org-todo 'left)
  ;; schedule to next spaced repetition
  (org-schedule nil (alist-get n+1 spaced-rep-map))
  ;; rewrite local tags
  (org-set-tags new-tags)
  (add-hook 'org-trigger-hook 'my/space-repeat-if-tag-spaced))
)))

(add-hook 'org-trigger-hook 'my/space-repeat-if-tag-spaced)
#+end_src


Thanks,

Andrea




On Wed 02 Jan 2019 at 05:59, Marcin Borkowski  wrote:

> On 2019-01-01, at 17:34, Andrea Giugliano  wrote:
>
>> Hi,
>>
>> Thanks for your reply. You are right org-drill does spaced repetition. I
>> just was unclear: I would like to see that in the agenda as a normal
>> item (that gets space-repeated every time I mark it DONE though).
>> I could not get from the docs if org-drill does that.
>
> That is an interesting idea.  I am pretty sure you could make it happen
> with `org-trigger-hook' or `org-after-todo-state-change-hook' (I am not
> entirely sure why both exist, btw).
>
>> Thanks,
>>
>> Andrea
>
> Hth,

Re: [O] Org mode repeated dates to do spaced learning

[Marcin Borkowski]

On 2019-01-01, at 17:34, Andrea Giugliano  wrote:

> Hi,
>
> Thanks for your reply. You are right org-drill does spaced repetition. I
> just was unclear: I would like to see that in the agenda as a normal
> item (that gets space-repeated every time I mark it DONE though).
> I could not get from the docs if org-drill does that.

That is an interesting idea.  I am pretty sure you could make it happen
with `org-trigger-hook' or `org-after-todo-state-change-hook' (I am not
entirely sure why both exist, btw).

> Thanks,
>
> Andrea

Hth,

--
Marcin Borkowski
http://mbork.pl

Re: [O] Org mode repeated dates to do spaced learning

[Andrea Giugliano]

Hi,

Thanks for your reply. You are right org-drill does spaced repetition. I
just was unclear: I would like to see that in the agenda as a normal
item (that gets space-repeated every time I mark it DONE though).
I could not get from the docs if org-drill does that.

Thanks,

Andrea

On Tue 01 Jan 2019 at 16:39, Bingo  wrote:

> Le 1 janvier 2019 18:02:31 GMT+05:30, Andrea Giugliano  a 
> écrit :
>>Happy 2019 everyone!
>>
>>I would like to slightly change my learning method this year. I have
>>heard that spaced learning is much better than bang your head against
>>the same material multiple times in a row.
>>
>>Spaced learning is simply reviewing some interesting topic at given
>>intervals: after 1 day, 1 week, 2 weeks, 1 month, 3 months, etc...
>>
>>It seems to me that org-mode does not support this: how would you make
>>a
>>repetitive task with spaced intervals?
>>
>>I saw org-drill.el, but I do not think it does this.
>>Ideally I could do something like:
>>
>>""
>>* review this interesting thing
>>SCHEDULED: <2019-01-01 Tue>
>>:PROPERTIES:
>>:SPACED:
>>:END:
>>""
>>
>>If this is not an interesting use case for org-mode, what do you think
>>about me trying to extend org-habits.el instead?
>>
>>Best wishes to all the community,
>>
>>Andrea
>
> Hi,
>Why do you think org-drill doesn't do spaced repetition ? I used it for a 
> while in 2017, and it does. I've since moved to Anki on Android phone for the 
> same purpose, because phones are accessible for longer, but was happy with 
> org-drill.

Re: [O] Org mode repeated dates to do spaced learning

[Bingo]

Le 1 janvier 2019 18:02:31 GMT+05:30, Andrea Giugliano  a 
écrit :
>Happy 2019 everyone!
>
>I would like to slightly change my learning method this year. I have
>heard that spaced learning is much better than bang your head against
>the same material multiple times in a row.
>
>Spaced learning is simply reviewing some interesting topic at given
>intervals: after 1 day, 1 week, 2 weeks, 1 month, 3 months, etc...
>
>It seems to me that org-mode does not support this: how would you make
>a
>repetitive task with spaced intervals?
>
>I saw org-drill.el, but I do not think it does this.
>Ideally I could do something like:
>
>""
>* review this interesting thing
>SCHEDULED: <2019-01-01 Tue>
>:PROPERTIES:
>:SPACED:
>:END:
>""
>
>If this is not an interesting use case for org-mode, what do you think
>about me trying to extend org-habits.el instead?
>
>Best wishes to all the community,
>
>Andrea

Hi,
   Why do you think org-drill doesn't do spaced repetition ? I used it for a 
while in 2017, and it does. I've since moved to Anki on Android phone for the 
same purpose, because phones are accessible for longer, but was happy with 
org-drill.

Re: [O] Org mode at 34C3: my demo + request for help

[stardiviner]

I'd like to see a statistics of Org Mode and Emacs users too.

How about use Org Mode to organize the project source code and publish
as Org file?

--
[ stardiviner ]
   I try to make every word tell the meaning what I want to express.

   Blog: https://stardiviner.github.io/
   IRC(freenode): stardiviner, Matrix: stardiviner
   GPG: F09F650D7D674819892591401B5DF1C95AE89AC3

Re: [O] org-mode blogging

[Thibault Marin]

I have done something similar with the sitemap functionality:
- I used the sitemap functions to extract date and title from the page:
  
https://thibaultmarin.github.io/blog/posts/2016-11-13-Personal_website_in_org.html#sitemap
- The sitemap is added in the main page to show a list of blog posts:
  
https://thibaultmarin.github.io/blog/posts/2016-11-13-Personal_website_in_org.html#index_org
- For the RSS feed, I wrote a simple function to extract the first
  paragraph of the blog post (there is probably a better way to do this).

I don't know of a standard way to do this, but this seems to work and
approach your needs.

Hope it helps.

thibault

On 2018-12-22T11:57:01-0500, Roy Lemmon wrote:

  I have setup a blog using org mode publish.

  I can easily list all blog posts on a page. However I would like to list
  the blog title, first few lines and date. Then be able to provide a link to
  another page with the full blog post.

  Is there a standard way to do this or do I need to use some elisp to
  extract the title and first few lines manually ?

  Thanks for any hints.

  Roy.

Re: [O] Org Mode - Organize Your Life In Plain Text!

[David Masterson]

Bernt Hansen  writes:

> I am working with the latest git version (master branch) on Windows
> running Emacs 25.1.1
>
> $ git describe
> release_9.1.14-1065-gdc7477070
>
> (currently 2 commits behind master since I haven't updated today)

You're a little ahead of me on Org and I am using Emacs 26.1 under
Cygwin to get a more Unix-like environment (personal taste).

> There were some changes:
>
>   - dropping org-structure_template_alist and temporarily using
> org-tempo. Sinc then I've switched to C-c , which is much better.
>
>   - org-time-clocksum-format -> org-duration-format
>
>   - refile changes (use caching)
>   - change time grid definition in agenda
>   - org-finalize-agenda-hook -> org-agenda-finalize-hook

You're much more advanced than I am on Org.  I mostly a beginner who is
also looking to hook it into BeOrg and other iOS tools for my family.  I
like Org for managing all the family information, but Apple tools are
simpler for the non-computer literate.  Things like being able to use
Siri to create family reminders or grocery lists is hard to ignore (but
coming with BeOrg).

> I am not aware of any other manuals.  When I started I used the
> out-of-the-box org-mode agendas (daily, weekly, separate task lists) and
> then when I was comfortable with how that worked I started making small
> customizations so they worked better for me and this eventually turned
> into the setup described on my website.

I've hacked Emacs some over the last 35 years, but I'm not a deep Elisp
programmer.  Over the years, I was more the type to read other people's
Elisp packages and add the interesting ones into my .emacs.

I think I'm beginning to see from your custom agenda commands how to
adjust the standard agenda views without doing too much elisp
programming.  I was hoping to find more examples of agenda setups to get
simpler ones that I could use.

Thanks
--
David

Re: [O] Org Mode - Organize Your Life In Plain Text!

[Bernt Hansen]

David Masterson  writes:

> Bernt Hansen  writes:
>
>> Hi David,
>>
>> Sorry my website on org-mode is stale and I don't currently have time to
>> update it.  I stopped updating it in 2015 after changing jobs and moving
>> to the windows platform (at work).  My main issue is lack of free time
>> to spend on this project.
>>
>> The downloadable org file is actually the result of publishing the org
>> source from my very out-of-date Linux workstation.  The original org
>> file (all versions) is available in the git repository.
>>
>> I'd be happy to answer any questions you have related to the site or my
>> current use of org-mode.  I still work in a similar way described on
>> http://doc.norang.ca/org-mode.html but my agenda and some workflows have
>> evolved a bit from what is described in the document.
>>
>> Regards,
>> Bernt
>
> Thank you for replying.  I'll just ask a few questions and maybe expand
> upon them later.
>
> 1. Are you still working with Emacs/Org from 2015 or have you updated
> (but not updated your paper)?

I am working with the latest git version (master branch) on Windows
running Emacs 25.1.1

$ git describe
release_9.1.14-1065-gdc7477070

(currently 2 commits behind master since I haven't updated today)

>
> 2. If you've updated to Org v9+, did you find significant changes from
> what you documented in your paper?  In other words, will running your
> paper through tangle and trying to use the results with latest Emacs and
> Org be likely to work?  Particularly agendas...

There were some changes:

  - dropping org-structure_template_alist and temporarily using
org-tempo. Sinc then I've switched to C-c , which is much better.

  - org-time-clocksum-format -> org-duration-format

  - refile changes (use caching)
  - change time grid definition in agenda
  - org-finalize-agenda-hook -> org-agenda-finalize-hook

>
> 3. Can you suggest a more detailed manual on the setup and use of
> Agendas?  The agenda manual with Org is not really clear to me.

I am not aware of any other manuals.  When I started I used the
out-of-the-box org-mode agendas (daily, weekly, separate task lists) and
then when I was comfortable with how that worked I started making small
customizations so they worked better for me and this eventually turned
into the setup described on my website.

Regards,
Bernt

Re: [O] Org Mode - Organize Your Life In Plain Text!

[David Masterson]

Bernt Hansen  writes:

> Hi David,
>
> Sorry my website on org-mode is stale and I don't currently have time to
> update it.  I stopped updating it in 2015 after changing jobs and moving
> to the windows platform (at work).  My main issue is lack of free time
> to spend on this project.
>
> The downloadable org file is actually the result of publishing the org
> source from my very out-of-date Linux workstation.  The original org
> file (all versions) is available in the git repository.
>
> I'd be happy to answer any questions you have related to the site or my
> current use of org-mode.  I still work in a similar way described on
> http://doc.norang.ca/org-mode.html but my agenda and some workflows have
> evolved a bit from what is described in the document.
>
> Regards,
> Bernt

Thank you for replying.  I'll just ask a few questions and maybe expand
upon them later.

1. Are you still working with Emacs/Org from 2015 or have you updated
(but not updated your paper)?

2. If you've updated to Org v9+, did you find significant changes from
what you documented in your paper?  In other words, will running your
paper through tangle and trying to use the results with latest Emacs and
Org be likely to work?  Particularly agendas...

3. Can you suggest a more detailed manual on the setup and use of
Agendas?  The agenda manual with Org is not really clear to me.

--
David

Re: [O] Org Mode - Organize Your Life In Plain Text!

[Bernt Hansen]

David Masterson  writes:

> I've been reading Bernt Hansen's excellent paper on setting up Org-Mode,
> but I noticed that it is rather dated and was wondering if Bernt is
> watching and plans to update the paper.  In particular, the last version
> of the paper on his website has a couple of things that I think should
> be fixed even if he doesn't do anything further with the paper.
>
> 1. Update the stale screen shots to match the rest of the paper so that
> people can see what you're talking about directly -- they would be very
> helpful.
>
> 2. Embed the version numbers in the paper so that when people download
> the paper, they don't lose the version/date of the paper they
> downloaded.  If I read it right, the paper calls a function which gets
> the version from git.  That won't work if I just download the org file.
>
> Is Bernt watching?

Hi David,

Sorry my website on org-mode is stale and I don't currently have time to
update it.  I stopped updating it in 2015 after changing jobs and moving
to the windows platform (at work).  My main issue is lack of free time
to spend on this project.

The downloadable org file is actually the result of publishing the org
source from my very out-of-date Linux workstation.  The original org
file (all versions) is available in the git repository.

I'd be happy to answer any questions you have related to the site or my
current use of org-mode.  I still work in a similar way described on
http://doc.norang.ca/org-mode.html but my agenda and some workflows have
evolved a bit from what is described in the document.

Regards,
Bernt

Re: [O] Org mode fontification broken

[Peter Westlake]

Problem solved! I had forgotten that I was using a copy of the Org repository 
instead of the package bundled with Emacs.

Peter.

On Mon, 12 Nov 2018, at 14:52, Peter Westlake wrote:
> Since upgrading from Fedora 27 to Fedora 28, Emacs 26.1-3.fc28.x86_64, 
> links and other fontified text in Org files appear as the underlying 
> plain text. A few of them look correct, and deleting a marker character 
> (e.g. square bracket) and reinserting it makes the link appear correctly 
> for a while. The Messages buffer is full of things like this:
> 
> Error during redisplay: (jit-lock-function 501) signaled (wrong-type-
> argument listp org-level-4)
> Error during redisplay: (jit-lock-function 1001) signaled (wrong-type-
> argument listp org-level-4)
> Error during redisplay: (jit-lock-function 1501) signaled (wrong-type-
> argument listp org-level-3)
> Error during redisplay: (jit-lock-function 2001) signaled (wrong-type-
> argument listp org-level-3)
> Error during redisplay: (jit-lock-function 1152403) signaled (wrong-
> type-argument listp org-level-2)
> 
> I've attempted to set jit-lock-mode to nil in .emacs, with no success.
> 
> This Emacs has a built-in version of Org, 9.1.14, and I've tried 
> 20181125 installed through Melpa. Nothing makes a difference.
>  
> Any ideas?
> 
> Peter.
> 

Re: [O] org-mode: Would like to add custom chars as org-list bullets

[Tom Burbage]

I don't think the suggestions made in that thread are going to help in 
terms of org-mode recognizing a line as being a list item.
What I tried that I did think might work was to customize 
org-list-full-item-re:


org-list-full-item-re is a variable defined in ‘org-list.el’.
Its value is
"^[     ]*\\(\\*(?:[-+*]\\|\\(?:[0-9]+\\|[A-Za-z]\\)[.)]\\)*\\(?:[     
]+\\|$\\)\\)\\(?:\\[@\\(?:start:\\)?\\([0-9]+\\|[A-Za-z]\\)\\][     
]*\\)?\\(?:\\(\\[[ X-]\\]\\)\\(?:[ ]+\\|$\\)\\)?\\(?:\\(.*\\)[     
]+::\\(?:[     ]+\\|$\\)\\)?"


  This variable may be risky if used as a file-local variable.

Documentation:
Matches a list item and puts everything into groups:
*group 1: bullet*
group 2: counter
group 3: checkbox
group 4: description tag

to add '!' and '?' to '-+' in the group 1 expression, but that didn't do 
it. ( *[-+*] => [-+!?*]* )


On 10/24/2018 5:47 PM, Grant Rettke wrote:

On Sat, Oct 13, 2018 at 1:56 AM Colin Baxter  wrote:

Tom Burbage  writes:

 > When I use simple lists, I would like to be able to mix in '!' and
 > '?'  with '-' as these are sometimes more expressive of what the
 > list item represents.  My request is that the list of characters
 > org-list recognizes as being a valid "bullet" be customizable by
 > the user.

Have a look at 
https://emacs.stackexchange.com/questions/35626/how-to-make-my-own-org-mode-text-emphasis-work-again.

Which code are you recommending?

Re: [O] org-mode: Would like to add custom chars as org-list bullets

[Colin Baxter]

> Grant Rettke  writes:

> On Sat, Oct 13, 2018 at 1:56 AM Colin Baxter  wrote:
>> 
>> > Tom Burbage  writes:
>> 
>> > When I use simple lists, I would like to be able to mix in '!'
>> and > '?'  with '-' as these are sometimes more expressive of
>> what the > list item represents.  My request is that the list of
>> characters > org-list recognizes as being a valid "bullet" be
>> customizable by > the user.
>> 
>> Have a look at
>> 
https://emacs.stackexchange.com/questions/35626/how-to-make-my-own-org-mode-text-emphasis-work-again.

> Which code are you recommending?

I'm not recommending anything. I'm suggesting that if you want
one or more characters in a list to act as emphasis then perhaps they
could be defined in terms of org-font-lock-extra-keywords, as in 'Answer
2'.

Best wishes,

Re: [O] org-mode: Would like to add custom chars as org-list bullets

[Grant Rettke]

On Sat, Oct 13, 2018 at 1:56 AM Colin Baxter  wrote:
>
> > Tom Burbage  writes:
>
> > When I use simple lists, I would like to be able to mix in '!' and
> > '?'  with '-' as these are sometimes more expressive of what the
> > list item represents.  My request is that the list of characters
> > org-list recognizes as being a valid "bullet" be customizable by
> > the user.
>
> Have a look at 
> https://emacs.stackexchange.com/questions/35626/how-to-make-my-own-org-mode-text-emphasis-work-again.

Which code are you recommending?

Re: [O] org-mode: Would like to add custom chars as org-list bullets

[Colin Baxter]

> Tom Burbage  writes:

> When I use simple lists, I would like to be able to mix in '!' and
> '?'  with '-' as these are sometimes more expressive of what the
> list item represents.  My request is that the list of characters
> org-list recognizes as being a valid "bullet" be customizable by
> the user.

Have a look at 
https://emacs.stackexchange.com/questions/35626/how-to-make-my-own-org-mode-text-emphasis-work-again.

Best wishes,

Re: [O] org-mode: Would like to add custom chars as org-list bullets

[Nicolas Goaziou]

Hello,

Tom Burbage  writes:

> My request is that the list of characters org-list recognizes as being
> a valid "bullet" be customizable by the user.

The syntax is not meant to be customizable. It goes against having
a standard Org format.

You can however, put overlays on top of bullets and /display/ them as
you wish. The extension "org-bullets" does something similar.

Regards,

-- 
Nicolas Goaziou

Re: [O] Org mode + Solid = collaborative, privacy-respecting future

[Roland Everaert]

I would also like to see something developped in ths direction.
Karl Voit writes:

> Hi!
>
> I stubled over Tim Berners-Lee Solid:
> https://www.fastcompany.com/90243936/exclusive-tim-berners-lee-tells-us-his-radical-new-plan-to-upend-the-world-wide-web
> https://www.inrupt.com/blog/one-small-step-for-the-web
> https://en.wikipedia.org/wiki/Solid_(web_decentralization_project)
>
> On https://github.com/solid/solid-apps I'd like to see something
> that combines the awesome (local) power of Org mode with the
> privacy-respecting soon-to-be platform Solid which adds
> collaborative notions to the story.
>
> Are there any actions going on already?
>
> This just feels right to be combined with the power of Org/Emacs.


-- 
Luke, use the FOSS

Sent from Emacs

Re: [O] Org mode + Solid = collaborative, privacy-respecting future

[Martin Schöön]

It looks like perfect solution to one of my org-mode uses.

Disclaimer: I have spent just a couple of minutes browsing those Solid-web
pages.

-- 
Martin Schöön

http://hem.bredband.net/b262106/index.html

Re: [O] Org-mode and koma-script

[gmx]

Thank you very much for that very complete answer and advice. This will 
allow me to learn better how to use emacs (and org-mode).


Frédéric


Le 29/08/2018 à 00:38, Tim Cross a écrit :

Just a few comments. While none will solve your immediate issue, they
may help track it down.

- it looks like your running as root! This is a very bad idea,
   especially if your inexperienced and still trying to work things
   out. Highly recommend you create a normal account (possibly with
   appropriate permissions to run sudo and perform administration tasks).

- Those lines look like your system is installing quite a few ELPA
   packages - this normally only happens once or after you do an upgrade
   of the elpa packages.

Most of those packages are not standard parts of Emacs and while very
useful, can severely complicate working out problems. Installing lots of
them at once also makes configuration much harder. Given you appear to
only have limited Emacs experience, I would highly recommend avoiding
the temptation to install lots of interesting packages all at once. A
far better approach is to get to know basic Emacs and then, as you gain
familiarity, look at what packages are available and then install and
try out ones which look like they might actually be useful. At the
moment, you have lots of packages which I suspect your not even using or
know about.

My recommendation would be to start again. Create a user account and
just run emacs without installing any packages. Focus on configuring
basic Emacs (which comes with org 'built-in'). Ensure you are using a
current version of Emacs (preferably Emacs 26.1 or Emacs 25.3). Get
basic Org working - don't worry about Korma Script initially, just use
basic Latex and verify that is all working first). Once the basics are
all working, then start tweaking to suit your needs, but do it
incrementally.

Another popular alternative, but not one I recommend, is to use one of
the pre-defined Emacs setups, such as spacemacs, prelude, Purcell's
.emacs etc. This will get you up and runining with an emacs config
defined by someone else and force you to work following their workflows,
but it is quick. Problem is, when you run into problems, you will be
lost and need others to help you out rather than being able to help
yourself.

Re: [O] Org-mode and koma-script

[Tim Cross]

Just a few comments. While none will solve your immediate issue, they
may help track it down.

- it looks like your running as root! This is a very bad idea,
  especially if your inexperienced and still trying to work things
  out. Highly recommend you create a normal account (possibly with
  appropriate permissions to run sudo and perform administration tasks).

- Those lines look like your system is installing quite a few ELPA
  packages - this normally only happens once or after you do an upgrade
  of the elpa packages.

Most of those packages are not standard parts of Emacs and while very
useful, can severely complicate working out problems. Installing lots of
them at once also makes configuration much harder. Given you appear to
only have limited Emacs experience, I would highly recommend avoiding
the temptation to install lots of interesting packages all at once. A
far better approach is to get to know basic Emacs and then, as you gain
familiarity, look at what packages are available and then install and
try out ones which look like they might actually be useful. At the
moment, you have lots of packages which I suspect your not even using or
know about.

My recommendation would be to start again. Create a user account and
just run emacs without installing any packages. Focus on configuring
basic Emacs (which comes with org 'built-in'). Ensure you are using a
current version of Emacs (preferably Emacs 26.1 or Emacs 25.3). Get
basic Org working - don't worry about Korma Script initially, just use
basic Latex and verify that is all working first). Once the basics are
all working, then start tweaking to suit your needs, but do it
incrementally.

Another popular alternative, but not one I recommend, is to use one of
the pre-defined Emacs setups, such as spacemacs, prelude, Purcell's
.emacs etc. This will get you up and runining with an emacs config
defined by someone else and force you to work following their workflows,
but it is quick. Problem is, when you run into problems, you will be
lost and need others to help you out rather than being able to help
yourself.

HTH

Tim


gmx  writes:

> Le 28/08/2018 à 18:04, Tim Cross a écrit:
>> Sorry, I was in a rush before work and sent you the wrong command!
> No problem. Thank you for giving me your time.
>>
>> What you need to do is run emacs --debug-init rather than emacs -q.
>
> Well. And the answer is... too long (many, many lines) : are ready to 
> read it (please take a look down) ?
>
>
>>
>> Your emacs init is either in the file .emacs in your home directory or
>> the file init.el in the .emacs.d directory (assuming your not using
>> something like spacemacs or some other 'canned' setup, which may break
>> out the config into other files).
> I work with Debian 9.
>>
>> The code you posted i.e.
>
>
> Leaving directory ‘/root/.emacs.d/elpa/avy-20180814.2121’
>
> Compiling file /root/.emacs.d/elpa/avy-20180814.2121/avy.el at Tue Aug 
> 28 20:00:34 2018
> Entering directory ‘/root/.emacs.d/elpa/avy-20180814.2121/’
>
> Compiling no file at Tue Aug 28 20:00:35 2018
> Leaving directory ‘/root/.emacs.d/elpa/ace-window-20180814.1516’
>
> Compiling file 
> /root/.emacs.d/elpa/ace-window-20180814.1516/ace-window.el at Tue Aug 28 
> 20:00:35 2018
> Entering directory ‘/root/.emacs.d/elpa/ace-window-20180814.1516/’
>
> Compiling no file at Tue Aug 28 20:00:36 2018
> Leaving directory ‘/root/.emacs.d/elpa/anzu-20161017.1607’
>
> Compiling file /root/.emacs.d/elpa/anzu-20161017.1607/anzu.el at Tue Aug 
> 28 20:00:36 2018
> Entering directory ‘/root/.emacs.d/elpa/anzu-20161017.1607/’
>
> Compiling no file at Tue Aug 28 20:00:37 2018
> Leaving directory ‘/root/.emacs.d/elpa/seq-2.20’
>
> Compiling file /root/.emacs.d/elpa/seq-2.20/seq-24.el at Tue Aug 28 
> 20:00:37 2018
> Entering directory ‘/root/.emacs.d/elpa/seq-2.20/’
>
> Compiling file /root/.emacs.d/elpa/seq-2.20/seq-25.el at Tue Aug 28 
> 20:00:37 2018
>
> Compiling file /root/.emacs.d/elpa/seq-2.20/seq-pkg.el at Tue Aug 28 
> 20:00:37 2018
>
> Compiling file /root/.emacs.d/elpa/seq-2.20/seq.el at Tue Aug 28 
> 20:00:37 2018
> Leaving directory ‘/root/.emacs.d/elpa/seq-2.20/’
>
> Compiling file /root/.emacs.d/elpa/seq-2.20/tests/seq-tests.el at Tue 
> Aug 28 20:00:37 2018
> Entering directory ‘/root/.emacs.d/elpa/seq-2.20/tests/’
>
> Compiling no file at Tue Aug 28 20:00:39 2018
> Leaving directory ‘/root/.emacs.d/elpa/beacon-20180706.1725’
>
> Compiling file /root/.emacs.d/elpa/beacon-20180706.1725/beacon.el at Tue 
> Aug 28 20:00:39 2018
> Entering directory ‘/root/.emacs.d/elpa/beacon-20180706.1725/’
>
> Compiling no file at Tue Aug 28 20:00:40 2018
> Leaving directory ‘/root/.emacs.d/elpa/browse-kill-ring-20171219.1908’
>
> Compiling file 
> /root/.emacs.d/elpa/browse-kill-ring-20171219.1908/browse-kill-ring.el 
> at Tue Aug 28 20:00:40 2018
> Entering directory ‘/root/.emacs.d/elpa/browse-kill-ring-20171219.1908/’
>
> Compiling no file at Tue Aug 28 20:00:41 2018
> Leaving directory 

Re: [O] Org-mode and koma-script

[gmx]

Oh, oh. I've opening a new emacs file, and this message waits me :

Warning (initialization): An error occurred while loading 
‘/home/frederic/.emacs’:


Symbol's value as variable is void: +

To ensure normal operation, you should investigate and remove the
cause of the error in your initialization file.  Start Emacs with
the ‘--debug-init’ option to view a complete error backtrace.


Well. I deleted this +, and... Everything's working perfectly!
That stupid + blocked everything. I'm sorry I didn't see it.
Thank you again, Tim, for your patience in answering me.

Problem solved (shame on me...).

Frédéric


Le 28/08/2018 à 18:04, Tim Cross a écrit :

Sorry, I was in a rush before work and sent you the wrong command!

What you need to do is run emacs --debug-init rather than emacs -q.

Your emacs init is either in the file .emacs in your home directory or
the file init.el in the .emacs.d directory (assuming your not using
something like spacemacs or some other 'canned' setup, which may break
out the config into other files).

The code you posted i.e.


; CONFIGURATION POUR UTILISER LATEX ;;
;; Source : https://orgmode.org/worg/org-tutorials/org-latex-export.html

;; Pour pouvoir utiliser LaTeX dans un doc. org-mode
(require 'ox-latex)
(unless (boundp 'org-latex-classes)
(setq org-latex-classes nil))
+
(add-to-list 'org-latex-classes
'("article"
"\\documentclass{article}"
("\\section{%s}" . "\\section*{%s}")))

;; Pour configurer les subdivisions des articles
(add-to-list 'org-latex-classes
'("article"
"\\documentclass{article}"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}")))

;; Pour configurer les subdivisions de la classe book (indiquer :
#+LaTeX_CLASS: book)
(with-eval-after-load "ox-latex"
(add-to-list 'org-latex-classes
'("book"
"\\documentclass{book}"
("\\part{%s}" . "\\part*{%s}")
("\\chapter{%s}" . "\\chapter*{%s}")
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}"

;; Pour utiliser la classe koma-script. Indiquer : #+LaTeX_CLASS:
koma-article
(with-eval-after-load "ox-latex"
(add-to-list 'org-latex-classes
'("koma-article" "\\documentclass{scrartcl}"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}"

doesn't look quite right. It should be in your init file i.e. .emacs or
.emacs.d/init.el and it needs to be correctly formed elisp statements,
The --debug-init will check this. Looking at it, you seem to have a
spurious '+' character, but there may be other problems as well.

There is a customize interface you can use to add the korma classes,
which may be easier than writing elisp if your not familiar with
that. Do M-x customize-group  org and have a look around.

What I use in my init is

   (setq org-latex-classes
 '(("beamer"
"\\documentclass[presentation]{beamer}"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
   ("hitec-article"
"\\documentclass[12pt]{hitec}
   [DEFAULT-PACKAGES]
   [PACKAGES]
   [NO-EXTRA]
   \\settextfraction{0.95}\n"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
   ("article" "\\documentclass[11pt]{article}"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
   ("korma-article" "\\documentclass[11pt]{scrartcl}"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
   ("report"
"\\documentclass[11pt]{report}"
("\\part{%s}" . "\\part*{%s}")
("\\chapter{%s}" . "\\chapter*{%s}")
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
   ("korma-report"
"\\documentclass[11pt]{scrreport}"
("\\part{%s}" . "\\part*{%s}")
 

Re: [O] Org-mode and koma-script

[Nick Dokos]

gmx  writes:

> Hello,
>
> I'm trying to use the koma class. I found a configuration of the.emacs 
> file, in the manual and in a Stack Exchange post 
> (https://tex.stackexchange.com/questions/364914/using-koma-script-article-with-org-mode).
>  
>
>
> I open a new .org file, and I declare:
>
> #+TITLE: MyTitle
> #+DATE: date
>
> #+LANGUAGE: fr
> #+LaTeX_CLASS: koma-article
>
> When I want to export my work in .pdf, I get the following answer: 
> Unknown LaTeX class 'koma-article'.
>
> What to do?

Most likely, you have an error in your .emacs file. You can check that
by seeing whether you successfully modified the org-latex-classes variable:

M-x v org-latex-classes RET

Chances are that it does not contain an entry for `koma-article',
because your .emacs was not read completely: emacs encountered an error
while processing it and gave up on processing the rest of it.

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

Re: [O] Org-mode and koma-script

[Nick Dokos]

Tim Cross  writes:

> If that is a copy of what is in your .emacs or init.el file, then I
> think you have a number of errors. Try running emacs -q and see if emacs
> reports errors in  your init file.
>

Did you mean `emacs --debug-init'? `emacs -q' will skip the user file.

> Tim
>
> gmx  writes:
>
>> I forgot the
>>
>> Le 27/08/2018 à 21:51, gmx a écrit:
>>> Hello,
>>>
>>> I'm trying to use the koma class. I found a configuration of the.emacs 
>>> file, in the manual and in a Stack Exchange post 
>>> (https://tex.stackexchange.com/questions/364914/using-koma-script-article-with-org-mode).
>>>  
>>>
>>>
>>> I open a new .org file, and I declare:
>>> #+TITLE: MyTitle
>>> #+DATE: date
>>> #+LANGUAGE: fr
>>> #+LaTeX_CLASS: koma-article
>>>
>>> When I want to export my work in .pdf, I get the following answer: 
>>> Unknown LaTeX class 'koma-article'.
>>>
>>> What to do?
>>> Thank you for your advice
>>>
>>> Frédéric (real newbie with org-mode, but I do my best)
>>>
>> contents of the file. Ready ?
>>
>>
>>
>> ;; Added by Package.el. This must come before configurations of
>> ;; installed packages. Don't delete this line. If you don't want it,
>> ;; just comment it out by adding a semicolon to the start of the line.
>> ;; You may delete these explanatory comments.
>> (package-initialize)
>>
>> (custom-set-variables
>>  ;; custom-set-variables was added by Custom.
>>  ;; If you edit it by hand, you could mess it up, so be careful.
>>  ;; Your init file should contain only one such instance.
>>  ;; If there is more than one, they won't work right.
>>  '(ansi-color-faces-vector
>>   [default default default italic underline success warning error])
>>  '(ansi-color-names-vector
>>   ["#212526" "#ff4b4b" "#b4fa70" "#fce94f" "#729fcf" "#e090d7" 
>> "#8cc4ff" "#ec"])
>>  '(current-language-environment "UTF-8")
>>  '(custom-enabled-themes (quote (deeper-blue)))
>>  '(display-battery-mode t))
>> (custom-set-faces
>>  ;; custom-set-faces was added by Custom.
>>  ;; If you edit it by hand, you could mess it up, so be careful.
>>  ;; Your init file should contain only one such instance.
>>  ;; If there is more than one, they won't work right.
>>  )
>> (put 'upcase-region 'disabled nil)
>>
>>
>> ; CONFIGURATION POUR UTILISER LATEX ;;
>> ;; Source : https://orgmode.org/worg/org-tutorials/org-latex-export.html
>>
>> ;; Pour pouvoir utiliser LaTeX dans un doc. org-mode
>> (require 'ox-latex)
>> (unless (boundp 'org-latex-classes)
>>   (setq org-latex-classes nil))
>> +
>> (add-to-list 'org-latex-classes
>>   '("article"
>>   "\\documentclass{article}"
>>   ("\\section{%s}" . "\\section*{%s}")))
>>
>> ;; Pour configurer les subdivisions des articles
>> (add-to-list 'org-latex-classes
>>   '("article"
>>   "\\documentclass{article}"
>>   ("\\section{%s}" . "\\section*{%s}")
>>   ("\\subsection{%s}" . "\\subsection*{%s}")
>>   ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
>>   ("\\paragraph{%s}" . "\\paragraph*{%s}")
>>   ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
>>
>> ;; Pour configurer les subdivisions de la classe book (indiquer : 
>> #+LaTeX_CLASS: book)
>> (with-eval-after-load "ox-latex"
>> (add-to-list 'org-latex-classes
>>   '("book"
>>   "\\documentclass{book}"
>>   ("\\part{%s}" . "\\part*{%s}")
>>   ("\\chapter{%s}" . "\\chapter*{%s}")
>>   ("\\section{%s}" . "\\section*{%s}")
>>   ("\\subsection{%s}" . "\\subsection*{%s}")
>>   ("\\subsubsection{%s}" . "\\subsubsection*{%s}"
>>
>> ;; Pour utiliser la classe koma-script. Indiquer : #+LaTeX_CLASS: 
>> koma-article
>> (with-eval-after-load "ox-latex"
>>   (add-to-list 'org-latex-classes
>>   '("koma-article" "\\documentclass{scrartcl}"
>>   ("\\section{%s}" . "\\section*{%s}")
>>   ("\\subsection{%s}" . "\\subsection*{%s}")
>>   ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
>>   ("\\paragraph{%s}" . "\\paragraph*{%s}")
>>   ("\\subparagraph{%s}" . "\\subparagraph*{%s}"

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

Re: [O] Org-mode and koma-script

[gmx]

Le 28/08/2018 à 18:04, Tim Cross a écrit :

Sorry, I was in a rush before work and sent you the wrong command!

No problem. Thank you for giving me your time.


What you need to do is run emacs --debug-init rather than emacs -q.


Well. And the answer is... too long (many, many lines) : are ready to 
read it (please take a look down) ?





Your emacs init is either in the file .emacs in your home directory or
the file init.el in the .emacs.d directory (assuming your not using
something like spacemacs or some other 'canned' setup, which may break
out the config into other files).

I work with Debian 9.


The code you posted i.e.



Leaving directory ‘/root/.emacs.d/elpa/avy-20180814.2121’

Compiling file /root/.emacs.d/elpa/avy-20180814.2121/avy.el at Tue Aug 
28 20:00:34 2018

Entering directory ‘/root/.emacs.d/elpa/avy-20180814.2121/’

Compiling no file at Tue Aug 28 20:00:35 2018
Leaving directory ‘/root/.emacs.d/elpa/ace-window-20180814.1516’

Compiling file 
/root/.emacs.d/elpa/ace-window-20180814.1516/ace-window.el at Tue Aug 28 
20:00:35 2018

Entering directory ‘/root/.emacs.d/elpa/ace-window-20180814.1516/’

Compiling no file at Tue Aug 28 20:00:36 2018
Leaving directory ‘/root/.emacs.d/elpa/anzu-20161017.1607’

Compiling file /root/.emacs.d/elpa/anzu-20161017.1607/anzu.el at Tue Aug 
28 20:00:36 2018

Entering directory ‘/root/.emacs.d/elpa/anzu-20161017.1607/’

Compiling no file at Tue Aug 28 20:00:37 2018
Leaving directory ‘/root/.emacs.d/elpa/seq-2.20’

Compiling file /root/.emacs.d/elpa/seq-2.20/seq-24.el at Tue Aug 28 
20:00:37 2018

Entering directory ‘/root/.emacs.d/elpa/seq-2.20/’

Compiling file /root/.emacs.d/elpa/seq-2.20/seq-25.el at Tue Aug 28 
20:00:37 2018


Compiling file /root/.emacs.d/elpa/seq-2.20/seq-pkg.el at Tue Aug 28 
20:00:37 2018


Compiling file /root/.emacs.d/elpa/seq-2.20/seq.el at Tue Aug 28 
20:00:37 2018

Leaving directory ‘/root/.emacs.d/elpa/seq-2.20/’

Compiling file /root/.emacs.d/elpa/seq-2.20/tests/seq-tests.el at Tue 
Aug 28 20:00:37 2018

Entering directory ‘/root/.emacs.d/elpa/seq-2.20/tests/’

Compiling no file at Tue Aug 28 20:00:39 2018
Leaving directory ‘/root/.emacs.d/elpa/beacon-20180706.1725’

Compiling file /root/.emacs.d/elpa/beacon-20180706.1725/beacon.el at Tue 
Aug 28 20:00:39 2018

Entering directory ‘/root/.emacs.d/elpa/beacon-20180706.1725/’

Compiling no file at Tue Aug 28 20:00:40 2018
Leaving directory ‘/root/.emacs.d/elpa/browse-kill-ring-20171219.1908’

Compiling file 
/root/.emacs.d/elpa/browse-kill-ring-20171219.1908/browse-kill-ring.el 
at Tue Aug 28 20:00:40 2018

Entering directory ‘/root/.emacs.d/elpa/browse-kill-ring-20171219.1908/’

Compiling no file at Tue Aug 28 20:00:41 2018
Leaving directory ‘/root/.emacs.d/elpa/crux-20180612.655’

Compiling file /root/.emacs.d/elpa/crux-20180612.655/crux.el at Tue Aug 
28 20:00:41 2018

Entering directory ‘/root/.emacs.d/elpa/crux-20180612.655/’

Compiling no file at Tue Aug 28 20:00:42 2018
Leaving directory ‘/root/.emacs.d/elpa/makey-20131231.1430’

Compiling file /root/.emacs.d/elpa/makey-20131231.1430/makey.el at Tue 
Aug 28 20:00:42 2018

Entering directory ‘/root/.emacs.d/elpa/makey-20131231.1430/’

Compiling no file at Tue Aug 28 20:00:43 2018
Leaving directory ‘/root/.emacs.d/elpa/discover-my-major-20180606.511’

Compiling file 
/root/.emacs.d/elpa/discover-my-major-20180606.511/discover-my-major.el 
at Tue Aug 28 20:00:43 2018

Entering directory ‘/root/.emacs.d/elpa/discover-my-major-20180606.511/’

Compiling no file at Tue Aug 28 20:00:44 2018
Leaving directory ‘/root/.emacs.d/elpa/diff-hl-20180201.1155’

Compiling file 
/root/.emacs.d/elpa/diff-hl-20180201.1155/diff-hl-amend.el at Tue Aug 28 
20:00:44 2018

Entering directory ‘/root/.emacs.d/elpa/diff-hl-20180201.1155/’

Compiling file 
/root/.emacs.d/elpa/diff-hl-20180201.1155/diff-hl-dired.el at Tue Aug 28 
20:00:44 2018


Compiling file 
/root/.emacs.d/elpa/diff-hl-20180201.1155/diff-hl-flydiff.el at Tue Aug 
28 20:00:44 2018


Compiling file 
/root/.emacs.d/elpa/diff-hl-20180201.1155/diff-hl-margin.el at Tue Aug 
28 20:00:44 2018


Compiling file /root/.emacs.d/elpa/diff-hl-20180201.1155/diff-hl.el at 
Tue Aug 28 20:00:44 2018


Compiling no file at Tue Aug 28 20:00:46 2018
Leaving directory ‘/root/.emacs.d/elpa/diminish-20170419.1736’

Compiling file /root/.emacs.d/elpa/diminish-20170419.1736/diminish.el at 
Tue Aug 28 20:00:46 2018

Entering directory ‘/root/.emacs.d/elpa/diminish-20170419.1736/’

Compiling no file at Tue Aug 28 20:00:47 2018
Leaving directory ‘/root/.emacs.d/elpa/easy-kill-20151031.529’

Compiling file /root/.emacs.d/elpa/easy-kill-20151031.529/easy-kill.el 
at Tue Aug 28 20:00:47 2018

Entering directory ‘/root/.emacs.d/elpa/easy-kill-20151031.529/’

Compiling no file at Tue Aug 28 20:00:51 2018
Leaving directory ‘/root/.emacs.d/elpa/editorconfig-20180823.452’

Compiling file 
/root/.emacs.d/elpa/editorconfig-20180823.452/editorconfig-conf-mode.el 
at Tue Aug 28 

Re: [O] Org-mode and koma-script

[Tim Cross]

Sorry, I was in a rush before work and sent you the wrong command!

What you need to do is run emacs --debug-init rather than emacs -q.

Your emacs init is either in the file .emacs in your home directory or
the file init.el in the .emacs.d directory (assuming your not using
something like spacemacs or some other 'canned' setup, which may break
out the config into other files).

The code you posted i.e.

>>> ; CONFIGURATION POUR UTILISER LATEX ;;
>>> ;; Source : https://orgmode.org/worg/org-tutorials/org-latex-export.html
>>>
>>> ;; Pour pouvoir utiliser LaTeX dans un doc. org-mode
>>> (require 'ox-latex)
>>> (unless (boundp 'org-latex-classes)
>>>(setq org-latex-classes nil))
>>> +
>>> (add-to-list 'org-latex-classes
>>>'("article"
>>>"\\documentclass{article}"
>>>("\\section{%s}" . "\\section*{%s}")))
>>>
>>> ;; Pour configurer les subdivisions des articles
>>> (add-to-list 'org-latex-classes
>>>'("article"
>>>"\\documentclass{article}"
>>>("\\section{%s}" . "\\section*{%s}")
>>>("\\subsection{%s}" . "\\subsection*{%s}")
>>>("\\subsubsection{%s}" . "\\subsubsection*{%s}")
>>>("\\paragraph{%s}" . "\\paragraph*{%s}")
>>>("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
>>>
>>> ;; Pour configurer les subdivisions de la classe book (indiquer :
>>> #+LaTeX_CLASS: book)
>>> (with-eval-after-load "ox-latex"
>>> (add-to-list 'org-latex-classes
>>>'("book"
>>>"\\documentclass{book}"
>>>("\\part{%s}" . "\\part*{%s}")
>>>("\\chapter{%s}" . "\\chapter*{%s}")
>>>("\\section{%s}" . "\\section*{%s}")
>>>("\\subsection{%s}" . "\\subsection*{%s}")
>>>("\\subsubsection{%s}" . "\\subsubsection*{%s}"
>>>
>>> ;; Pour utiliser la classe koma-script. Indiquer : #+LaTeX_CLASS:
>>> koma-article
>>> (with-eval-after-load "ox-latex"
>>>(add-to-list 'org-latex-classes
>>>'("koma-article" "\\documentclass{scrartcl}"
>>>("\\section{%s}" . "\\section*{%s}")
>>>("\\subsection{%s}" . "\\subsection*{%s}")
>>>("\\subsubsection{%s}" . "\\subsubsection*{%s}")
>>>("\\paragraph{%s}" . "\\paragraph*{%s}")
>>>("\\subparagraph{%s}" . "\\subparagraph*{%s}"
>>

doesn't look quite right. It should be in your init file i.e. .emacs or
.emacs.d/init.el and it needs to be correctly formed elisp statements,
The --debug-init will check this. Looking at it, you seem to have a
spurious '+' character, but there may be other problems as well.

There is a customize interface you can use to add the korma classes,
which may be easier than writing elisp if your not familiar with
that. Do M-x customize-group  org and have a look around. 

What I use in my init is

  (setq org-latex-classes
'(("beamer"
   "\\documentclass[presentation]{beamer}"
   ("\\section{%s}" . "\\section*{%s}")
   ("\\subsection{%s}" . "\\subsection*{%s}")
   ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
  ("hitec-article"
   "\\documentclass[12pt]{hitec}
  [DEFAULT-PACKAGES]
  [PACKAGES]
  [NO-EXTRA]
  \\settextfraction{0.95}\n"
   ("\\section{%s}" . "\\section*{%s}")
   ("\\subsection{%s}" . "\\subsection*{%s}")
   ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
   ("\\paragraph{%s}" . "\\paragraph*{%s}")
   ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
  ("article" "\\documentclass[11pt]{article}"
   ("\\section{%s}" . "\\section*{%s}")
   ("\\subsection{%s}" . "\\subsection*{%s}")
   ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
   ("\\paragraph{%s}" . "\\paragraph*{%s}")
   ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
  ("korma-article" "\\documentclass[11pt]{scrartcl}"
   ("\\section{%s}" . "\\section*{%s}")
   ("\\subsection{%s}" . "\\subsection*{%s}")
   ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
   ("\\paragraph{%s}" . "\\paragraph*{%s}")
   ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
  ("report"
   "\\documentclass[11pt]{report}"
   ("\\part{%s}" . "\\part*{%s}")
   ("\\chapter{%s}" . "\\chapter*{%s}")
   ("\\section{%s}" . "\\section*{%s}")
   ("\\subsection{%s}" . "\\subsection*{%s}")
   ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
  ("korma-report"
   "\\documentclass[11pt]{scrreport}"
   ("\\part{%s}" . "\\part*{%s}")
   ("\\chapter{%s}" . "\\chapter*{%s}")
   ("\\section{%s}" . "\\section*{%s}")
   ("\\subsection{%s}" . "\\subsection*{%s}")
   ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
  ("korma-book"
   "\\documentclass[11pt]{scrbook}"
   ("\\part{%s}" . "\\part*{%s}")
   ("\\chapter{%s}" . "\\chapter*{%s}")
   ("\\section{%s}" . "\\section*{%s}")
   ("\\subsection{%s}" . "\\subsection*{%s}")
   ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
  

Re: [O] Org-mode and koma-script

[gmx]

Thanks a lot for your answer, Tim. I entered the emacs -q command, which 
started emacs. The only message from the Terminal (before launching 
emacs) is this:


(emacs:3687): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
Did not receive a reply. Possible causes include: the remote application 
did not send a reply, the message bus security policy blocked the reply, 
the reply timeout expired, or the network connection was broken.


But no real problem.

I did't find the init file : where is it, please ?

Frédéric


Le 28/08/2018 à 00:00, Tim Cross a écrit :

If that is a copy of what is in your .emacs or init.el file, then I
think you have a number of errors. Try running emacs -q and see if emacs
reports errors in  your init file.

Tim

gmx  writes:


I forgot the

Le 27/08/2018 à 21:51, gmx a écrit:

Hello,

I'm trying to use the koma class. I found a configuration of the.emacs
file, in the manual and in a Stack Exchange post
(https://tex.stackexchange.com/questions/364914/using-koma-script-article-with-org-mode).


I open a new .org file, and I declare:
#+TITLE: MyTitle
#+DATE: date
#+LANGUAGE: fr
#+LaTeX_CLASS: koma-article

When I want to export my work in .pdf, I get the following answer:
Unknown LaTeX class 'koma-article'.

What to do?
Thank you for your advice

Frédéric (real newbie with org-mode, but I do my best)


contents of the file. Ready ?



;; Added by Package.el. This must come before configurations of
;; installed packages. Don't delete this line. If you don't want it,
;; just comment it out by adding a semicolon to the start of the line.
;; You may delete these explanatory comments.
(package-initialize)

(custom-set-variables
  ;; custom-set-variables was added by Custom.
  ;; If you edit it by hand, you could mess it up, so be careful.
  ;; Your init file should contain only one such instance.
  ;; If there is more than one, they won't work right.
  '(ansi-color-faces-vector
   [default default default italic underline success warning error])
  '(ansi-color-names-vector
   ["#212526" "#ff4b4b" "#b4fa70" "#fce94f" "#729fcf" "#e090d7"
"#8cc4ff" "#ec"])
  '(current-language-environment "UTF-8")
  '(custom-enabled-themes (quote (deeper-blue)))
  '(display-battery-mode t))
(custom-set-faces
  ;; custom-set-faces was added by Custom.
  ;; If you edit it by hand, you could mess it up, so be careful.
  ;; Your init file should contain only one such instance.
  ;; If there is more than one, they won't work right.
  )
(put 'upcase-region 'disabled nil)


; CONFIGURATION POUR UTILISER LATEX ;;
;; Source : https://orgmode.org/worg/org-tutorials/org-latex-export.html

;; Pour pouvoir utiliser LaTeX dans un doc. org-mode
(require 'ox-latex)
(unless (boundp 'org-latex-classes)
   (setq org-latex-classes nil))
+
(add-to-list 'org-latex-classes
   '("article"
   "\\documentclass{article}"
   ("\\section{%s}" . "\\section*{%s}")))

;; Pour configurer les subdivisions des articles
(add-to-list 'org-latex-classes
   '("article"
   "\\documentclass{article}"
   ("\\section{%s}" . "\\section*{%s}")
   ("\\subsection{%s}" . "\\subsection*{%s}")
   ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
   ("\\paragraph{%s}" . "\\paragraph*{%s}")
   ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))

;; Pour configurer les subdivisions de la classe book (indiquer :
#+LaTeX_CLASS: book)
(with-eval-after-load "ox-latex"
(add-to-list 'org-latex-classes
   '("book"
   "\\documentclass{book}"
   ("\\part{%s}" . "\\part*{%s}")
   ("\\chapter{%s}" . "\\chapter*{%s}")
   ("\\section{%s}" . "\\section*{%s}")
   ("\\subsection{%s}" . "\\subsection*{%s}")
   ("\\subsubsection{%s}" . "\\subsubsection*{%s}"

;; Pour utiliser la classe koma-script. Indiquer : #+LaTeX_CLASS:
koma-article
(with-eval-after-load "ox-latex"
   (add-to-list 'org-latex-classes
   '("koma-article" "\\documentclass{scrartcl}"
   ("\\section{%s}" . "\\section*{%s}")
   ("\\subsection{%s}" . "\\subsection*{%s}")
   ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
   ("\\paragraph{%s}" . "\\paragraph*{%s}")
   ("\\subparagraph{%s}" . "\\subparagraph*{%s}"

Re: [O] Org-mode and koma-script

[Tim Cross]

If that is a copy of what is in your .emacs or init.el file, then I
think you have a number of errors. Try running emacs -q and see if emacs
reports errors in  your init file.

Tim

gmx  writes:

> I forgot the
>
> Le 27/08/2018 à 21:51, gmx a écrit:
>> Hello,
>>
>> I'm trying to use the koma class. I found a configuration of the.emacs 
>> file, in the manual and in a Stack Exchange post 
>> (https://tex.stackexchange.com/questions/364914/using-koma-script-article-with-org-mode).
>>  
>>
>>
>> I open a new .org file, and I declare:
>> #+TITLE: MyTitle
>> #+DATE: date
>> #+LANGUAGE: fr
>> #+LaTeX_CLASS: koma-article
>>
>> When I want to export my work in .pdf, I get the following answer: 
>> Unknown LaTeX class 'koma-article'.
>>
>> What to do?
>> Thank you for your advice
>>
>> Frédéric (real newbie with org-mode, but I do my best)
>>
> contents of the file. Ready ?
>
>
>
> ;; Added by Package.el. This must come before configurations of
> ;; installed packages. Don't delete this line. If you don't want it,
> ;; just comment it out by adding a semicolon to the start of the line.
> ;; You may delete these explanatory comments.
> (package-initialize)
>
> (custom-set-variables
>  ;; custom-set-variables was added by Custom.
>  ;; If you edit it by hand, you could mess it up, so be careful.
>  ;; Your init file should contain only one such instance.
>  ;; If there is more than one, they won't work right.
>  '(ansi-color-faces-vector
>   [default default default italic underline success warning error])
>  '(ansi-color-names-vector
>   ["#212526" "#ff4b4b" "#b4fa70" "#fce94f" "#729fcf" "#e090d7" 
> "#8cc4ff" "#ec"])
>  '(current-language-environment "UTF-8")
>  '(custom-enabled-themes (quote (deeper-blue)))
>  '(display-battery-mode t))
> (custom-set-faces
>  ;; custom-set-faces was added by Custom.
>  ;; If you edit it by hand, you could mess it up, so be careful.
>  ;; Your init file should contain only one such instance.
>  ;; If there is more than one, they won't work right.
>  )
> (put 'upcase-region 'disabled nil)
>
>
> ; CONFIGURATION POUR UTILISER LATEX ;;
> ;; Source : https://orgmode.org/worg/org-tutorials/org-latex-export.html
>
> ;; Pour pouvoir utiliser LaTeX dans un doc. org-mode
> (require 'ox-latex)
> (unless (boundp 'org-latex-classes)
>   (setq org-latex-classes nil))
> +
> (add-to-list 'org-latex-classes
>   '("article"
>   "\\documentclass{article}"
>   ("\\section{%s}" . "\\section*{%s}")))
>
> ;; Pour configurer les subdivisions des articles
> (add-to-list 'org-latex-classes
>   '("article"
>   "\\documentclass{article}"
>   ("\\section{%s}" . "\\section*{%s}")
>   ("\\subsection{%s}" . "\\subsection*{%s}")
>   ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
>   ("\\paragraph{%s}" . "\\paragraph*{%s}")
>   ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
>
> ;; Pour configurer les subdivisions de la classe book (indiquer : 
> #+LaTeX_CLASS: book)
> (with-eval-after-load "ox-latex"
> (add-to-list 'org-latex-classes
>   '("book"
>   "\\documentclass{book}"
>   ("\\part{%s}" . "\\part*{%s}")
>   ("\\chapter{%s}" . "\\chapter*{%s}")
>   ("\\section{%s}" . "\\section*{%s}")
>   ("\\subsection{%s}" . "\\subsection*{%s}")
>   ("\\subsubsection{%s}" . "\\subsubsection*{%s}"
>
> ;; Pour utiliser la classe koma-script. Indiquer : #+LaTeX_CLASS: 
> koma-article
> (with-eval-after-load "ox-latex"
>   (add-to-list 'org-latex-classes
>   '("koma-article" "\\documentclass{scrartcl}"
>   ("\\section{%s}" . "\\section*{%s}")
>   ("\\subsection{%s}" . "\\subsection*{%s}")
>   ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
>   ("\\paragraph{%s}" . "\\paragraph*{%s}")
>   ("\\subparagraph{%s}" . "\\subparagraph*{%s}"


-- 
Tim Cross

Re: [O] Org-mode and koma-script

[gmx]

I forgot the

Le 27/08/2018 à 21:51, gmx a écrit :

Hello,

I'm trying to use the koma class. I found a configuration of the.emacs 
file, in the manual and in a Stack Exchange post 
(https://tex.stackexchange.com/questions/364914/using-koma-script-article-with-org-mode). 



I open a new .org file, and I declare:
#+TITLE: MyTitle
#+DATE: date
#+LANGUAGE: fr
#+LaTeX_CLASS: koma-article

When I want to export my work in .pdf, I get the following answer: 
Unknown LaTeX class 'koma-article'.


What to do?
Thank you for your advice

Frédéric (real newbie with org-mode, but I do my best)


contents of the file. Ready ?



;; Added by Package.el.  This must come before configurations of
;; installed packages.  Don't delete this line.  If you don't want it,
;; just comment it out by adding a semicolon to the start of the line.
;; You may delete these explanatory comments.
(package-initialize)

(custom-set-variables
 ;; custom-set-variables was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 '(ansi-color-faces-vector
   [default default default italic underline success warning error])
 '(ansi-color-names-vector
   ["#212526" "#ff4b4b" "#b4fa70" "#fce94f" "#729fcf" "#e090d7" 
"#8cc4ff" "#ec"])

 '(current-language-environment "UTF-8")
 '(custom-enabled-themes (quote (deeper-blue)))
 '(display-battery-mode t))
(custom-set-faces
 ;; custom-set-faces was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 )
(put 'upcase-region 'disabled nil)


; CONFIGURATION POUR UTILISER LATEX ;;
;; Source : https://orgmode.org/worg/org-tutorials/org-latex-export.html

;; Pour pouvoir utiliser LaTeX dans un doc. org-mode
(require 'ox-latex)
(unless (boundp 'org-latex-classes)
  (setq org-latex-classes nil))
+
(add-to-list 'org-latex-classes
 '("article"
   "\\documentclass{article}"
   ("\\section{%s}" . "\\section*{%s}")))

;; Pour configurer les subdivisions des articles
(add-to-list 'org-latex-classes
 '("article"
   "\\documentclass{article}"
   ("\\section{%s}" . "\\section*{%s}")
   ("\\subsection{%s}" . "\\subsection*{%s}")
   ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
   ("\\paragraph{%s}" . "\\paragraph*{%s}")
   ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))

;; Pour configurer les subdivisions de la classe book (indiquer : 
#+LaTeX_CLASS: book)

(with-eval-after-load "ox-latex"
(add-to-list 'org-latex-classes
 '("book"
   "\\documentclass{book}"
   ("\\part{%s}" . "\\part*{%s}")
   ("\\chapter{%s}" . "\\chapter*{%s}")
   ("\\section{%s}" . "\\section*{%s}")
   ("\\subsection{%s}" . "\\subsection*{%s}")
   ("\\subsubsection{%s}" . "\\subsubsection*{%s}"

;; Pour utiliser la classe koma-script. Indiquer : #+LaTeX_CLASS: 
koma-article

(with-eval-after-load "ox-latex"
  (add-to-list 'org-latex-classes
   '("koma-article" "\\documentclass{scrartcl}"
 ("\\section{%s}" . "\\section*{%s}")
 ("\\subsection{%s}" . "\\subsection*{%s}")
 ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
 ("\\paragraph{%s}" . "\\paragraph*{%s}")
 ("\\subparagraph{%s}" . "\\subparagraph*{%s}"

Re: [O] Org Mode Documentation Patch

[Van L]

>> I've printed, signed, scanned and sent the assignment to
>> ass...@gnu.org , waiting for their response.
> 
> Nice.

It should be possible to do without printing and 
scanning, do all of the assignment electronically.

Re: [O] Org Mode Documentation Patch

[Nicolas Goaziou]

Hello,

"Siraphob (Ben) Phipathananunth"  writes:

> I've printed, signed, scanned and sent the assignment to
> ass...@gnu.org , waiting for their response.

Nice.

> In the meantime, please install another patch I wrote, attached.

Done, barring one hunk specified below.

> You may notice that the email and name of the patch author is
> different, this is to correspond with my email and legal name. ("Ben"
> is my nickname)

OK.

> - compilation for /today/, until the entry is marked DONE, i.e.,
> - the task is automatically forwarded until completed.
> + compilation for /today/, until the entry is marked DONE, (i.e.
> + the task is automatically forwarded until completed).

I wasn't convinced by this change so I didn't apply it. The former form
looks correct.

Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] Org Mode Documentation Patch

[Siraphob (Ben) Phipathananunth]

I've printed, signed, scanned and sent the assignment to ass...@gnu.org 
, waiting for their response.


In the meantime, please install another patch I wrote, attached.

You may notice that the email and name of the patch author is different, 
this is to correspond with my email and legal name. ("Ben" is my nickname)


Thanks,

--
Siraphob (Ben) Phipathananunth
From 677ac08a5b11157f59dd5acc73a2bc7103344f22 Mon Sep 17 00:00:00 2001
From: Siraphob Phipathananunth 
Date: Mon, 25 Jun 2018 21:27:05 +0700
Subject: [PATCH] Fix "cursor" to "point", fix grammar and add cross-references

* doc/org-manual : More wording and grammar is fixed, cross-references
to other sections are added when key terms appear (e.g. agenda,
property, completion).
---
 doc/org-manual.org | 323 ++---
 1 file changed, 161 insertions(+), 162 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index f1180458a..caa23be83 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -1145,8 +1145,7 @@ to disable them individually.
  indentation.  When these commands are executed several times in
  direct succession, the initially selected region is used, even if
  the new indentation would imply a different hierarchy.  To use
- the new hierarchy, break the command chain with a cursor motion
- or so.
+ the new hierarchy, break the command chain by moving point.
 
  As a special case, using this command on the very first item of
  a list moves the whole list.  This behavior can be disabled by
@@ -1194,7 +1193,7 @@ to disable them individually.
  #+vindex: org-support-shift-select
  #+kindex: S-LEFT
  #+kindex: S-RIGHT
- This command also cycles bullet styles when point in on the
+ This command also cycles bullet styles when point is in on the
  bullet or anywhere in an item line, details depending on
  ~org-support-shift-select~.
 
@@ -1683,7 +1682,7 @@ you, configure the option ~org-table-auto-blank-field~.
  #+vindex: org-table-copy-increment
  When current field is empty, copy from first non-empty field
  above.  When not empty, copy current field down to next row and
- move cursor along with it.  Depending on the variable
+ move point along with it.  Depending on the variable
  ~org-table-copy-increment~, integer field values can be
  incremented during copy.  Integers that are too large are not
  incremented, however.  Also, a ~0~ prefix argument temporarily
@@ -1919,10 +1918,10 @@ to derive fields from other fields.  While fully 
featured, Org's
 implementation is not identical to other spreadsheets.  For example,
 Org knows the concept of a /column formula/ that will be applied to
 all non-header fields in a column without having to copy the formula
-to each relevant field.  There is also a formula debugger, and
-a formula editor with features for highlighting fields in the table
-corresponding to the references at the point in the formula, moving
-these references by arrow keys.
+to each relevant field.  There is also a formula debugger, and a
+formula editor with features for highlighting fields in the table
+corresponding to the references at point in the formula, moving these
+references by arrow keys.
 
 *** References
 :PROPERTIES:
@@ -3376,7 +3375,7 @@ generally, act on links.
  possible with =~/= for your home directory.  You can force an
  absolute path with two {{{kbd(C-u)}}} prefixes.
 
-- {{{kbd(C-c C-l)}}} (with cursor on existing link) ::
+- {{{kbd(C-c C-l)}}} (with point on existing link) ::
 
  #+cindex: following links
  When point is on an existing link, {{{kbd(C-c C-l)}}} allows
@@ -3391,11 +3390,11 @@ generally, act on links.
  ~browse-url-at-point~), run VM/MH-E/Wanderlust/Rmail/Gnus/BBDB
  for the corresponding links, and execute the command in a shell
  link.  When point is on an internal link, this command runs the
- corresponding search.  When point is on the tags part of
- a headline, it creates the corresponding tags view (see [[*Matching
- tags and properties]]).  If the cursor is on a timestamp, it
- compiles the agenda for that date.  Furthermore, it visits text
- and remote files in =file= links with Emacs and select a suitable
+ corresponding search.  When point is on the tags part of a
+ headline, it creates the corresponding tags view (see [[*Matching
+ tags and properties]]).  If point is on a timestamp, it compiles
+ the agenda for that date.  Furthermore, it visits text and remote
+ files in =file= links with Emacs and select a suitable
  application for local non-text files.  Classification of files is
  based on file extension only.  See option ~org-file-apps~.  If
  you want to override the default application and visit the file
@@ -3867,14 +3866,13 @@ require action.  Your setup would then look like this:
 (sequence "|" "CANCELED")))
 #+end_src
 
-The keywords should 

Re: [O] Org Mode Documentation Patch

[Nicolas Goaziou]

"Siraphob (Ben) Phipathananunth"  writes:

> I just sent an email to ass...@gnu.org with my information,

Great!

> how will I know when copyright assign is completed?

They will let you know. Then, you may let me know. :)

Re: [O] Org Mode Documentation Patch

[Siraphob (Ben) Phipathananunth]

Thank you very much for accepting the patch.

Nicolas Goaziou wrote:
> BTW, what is your status wrt FSF papers?

I just sent an email to ass...@gnu.org with my information, how will I know 
when copyright assign is completed?

Thank you again,

-- 
Siraphob (Ben) Phipathananunth

Re: [O] Org Mode Documentation Patch

[Nicolas Goaziou]

Hello,

"Siraphob (Ben) Phipathananunth"  writes:

> I've begun reading the Org Mode manual, and noticed that the wording
> in some places could be improved (so far I've read up to Section 4.8).
> I've attached my patch.  Some of the more drastic changes:
>
> - Changed all occurrences of "the cursor" to "point", I thought the
>   inconsistency was confusing, especially since the Emacs manual
>   maintains usage of "point" throughout, so too should the Org Mode
>   manual.

Thank you. I applied your patch. 

I'm not totally convinced by the change from "function" to "Lisp
function", since, in the context of Org, an Elisp library, there is no
ambiguity. But I have no strong opinion, so I didn't remove the
occurrences in your patch.

BTW, what is your status wrt FSF papers?

> Section 4.6 "Link abbreviations" in the Org Mode manual link to
> websites that have and/or promote non-free software.  The URLs are
> used to illustrate link abbreviations in Org Mode, but I suppose this
> was purely coincidental because long URLs to websites such as
> gnu.org/some/long/path could be used instead.  Would it be appropriate
> to change the examples in a later patch?

Sure. However, for the sake of clarity, it would be better if not all
examples are similar, i.e., no "gnu.org/some/long/path" everywhere.

> When the PDF version of the Org Mode manual is generated with "make
> docs", the footnotes (3 and 4) around Section 4.3 are incorrectly
> indented, can anyone reproduce this?

I don't see anything like that in the PDF. You may want to try deleting
it and re-generate it.

> Should I submit my patches as smaller ones as I read sections of the
> manual or bulk them together into a larger patch, or is it just a
> matter of preference?

As you wish.

> Please let me know if you have any comments about the patch.  It's my
> first one, I hope I have followed the CONTRIBUTING guide properly.

I fixed a couple of missing capitalization (point at the beginning of
a sentence) and filled modified paragraphs. I also slightly modified
your commit message.

Regards,

-- 
Nicolas Goaziou

Re: [O] Org mode in combination with emacs follow-mode is terrible

[Gerald Wildgruber]

I tried profiling my use of org-mode in conjunction with follow-mode; I
did the following:

1. M-x profiler-start
2. I enabled follow-mode in my buffer
3. I did some editing
4. M-x profiler-report
5. M-x profiler-stop

here's the result:

Collapsed, the report looks like that:

+ command-execute8789  47%
+ follow-post-command-hook   7755  41%
+ ...1976  10%
+ redisplay_internal (C function) 104   0%
+ yas--post-command-handler40   0%
+ timer-event-handler  20   0%
  tooltip-hide  7   0%


And somewhat expanded:

- command-execute8789  47%
 - call-interactively8789  47%
  - byte-code8174  43%
   - read-extended-command   8174  43%
- completing-read8174  43%
 - # 8174  43%
  - apply8174  43%
   - helm--completing-read-default   8174  43%
- helm-completing-read-sync-default-handler   8174  43%
 - helm-completing-read-default-18174  43%
  - helm-comp-read   8174  43%
   - helm8165  43%
- apply  8165  43%
 - helm  8165  43%
  - apply8165  43%
   - helm-internal   8165  43%
- helm-read-pattern-maybe8150  43%
 + read-from-minibuffer  8079  43%
 + helm-update 43   0%
- # 9   0%
 + helm-cleanup 9   0%
+ helm-display-buffer   6   0%
   + helm-make-source   9   0%
  + funcall-interactively 615   3%
- follow-post-command-hook   7755  41%
 - follow-adjust-window  7755  41%
  - follow-windows-start-end 7732  41%
   - follow-calc-win-end 7732  41%
+ pos-visible-in-window-p  25   0%
+ posn-at-x-y   7   0%
+ window-inside-pixel-edges 3   0%
  + follow-all-followers4   0%
follow-avoid-tail-recenter  3   0%

If I understand correctly "follow-calc-win-end" would be the function
that uses most of cpu time.

I can't say how "normal" the other 47% under "command-execute" are,
which mainly seems to be helm-related ("helm-update").

Can anyone give an advice on possible optimizations with this situation?


Gerald.


On Mi, Jun 13 2018, Joost Kremers  wrote:

> Actually, I would suspect it's more of a problem for follow-mode than
> org-mode, because follow-mode needs to keep the different windows in sync.
> For this, it adds a function to `post-command-hook', which means it's run
> after every key press.
>
> It's not inconceivable that `follow-mode' does something that is extra
> time-consuming in an Org buffer. To find out what that might be, you could
> try the Elisp profiler that comes with Emacs. See the section "Profiling"
> in the Elisp manual for details.
>
> Once you've found out which function(s) consume so much time, it might be
> possible to ask in here or on emacs-devel what exactly is causing the
> problem and whether there's a way around it.


--
Dr. Gerald Wildgruber
Institut für Philosophie, Literatur-, Wissenschafts- und Technikgeschichte
Literaturwissenschaft mit Schwerpunkt Literatur und Wissenschaft
Technische Universität Berlin
Straße des 17. Juni 135
D-10623 Berlin
http://www.philosophie.tu-berlin.de/menue/home/
T. +49 (0)30 314 25924
F. +49 (0)30 314 23107
wildgru...@tu-berlin.de
-
Sent with mu4e

Re: [O] Org mode in combination with emacs follow-mode is terrible

[Gerald Wildgruber]

Thanks Joost,

that's interesting! I never used the profiler but I will try and see how
far I get with it and then come back here.

Gerald.

On Mi, Jun 13 2018, Joost Kremers  wrote:

> On Wed, Jun 13 2018, Eric S Fraga wrote:
>> On Wednesday, 13 Jun 2018 at 09:53, Gerald Wildgruber wrote:
>>> Switching to text-mode, with 5 windows and follow-mode still being
>>> active reduces lag significantly.
>>>
>>> So there must be an issue specifically with the combination of org-mode
>>> and follow-mode!
>>
>> I don't think there's an issue per se in the sense of bugs.  Org does
>> much more processing of the text than does text mode so if you have 60k
>> worth of text to process each time you type something, it's probably not
>> surprising that there is a lag.
>
> Actually, I would suspect it's more of a problem for follow-mode than
> org-mode, because follow-mode needs to keep the different windows in sync.
> For this, it adds a function to `post-command-hook', which means it's run
> after every key press.
>
> It's not inconceivable that `follow-mode' does something that is extra
> time-consuming in an Org buffer. To find out what that might be, you could
> try the Elisp profiler that comes with Emacs. See the section "Profiling"
> in the Elisp manual for details.
>
> Once you've found out which function(s) consume so much time, it might be
> possible to ask in here or on emacs-devel what exactly is causing the
> problem and whether there's a way around it.


--
Dr. Gerald Wildgruber
Institut für Philosophie, Literatur-, Wissenschafts- und Technikgeschichte
Literaturwissenschaft mit Schwerpunkt Literatur und Wissenschaft
Technische Universität Berlin
Straße des 17. Juni 135
D-10623 Berlin
http://www.philosophie.tu-berlin.de/menue/home/
T. +49 (0)30 314 25924
F. +49 (0)30 314 23107
wildgru...@tu-berlin.de
-
Sent with mu4e

Re: [O] Org mode in combination with emacs follow-mode is terrible

[Gerald Wildgruber]

Thanks again; I'm always using the latest git checkout of emacs
(v.27, see my first posting).

On Mi, Jun 13 2018, Eric S Fraga  wrote:

> I don't think there's an issue per se in the sense of bugs.  Org does
> much more processing of the text than does text mode so if you have 60k
> worth of text to process each time you type something, it's probably not
> surprising that there is a lag.  60k is a lot of text and I assume there
> are many headings etc.?

Yes, indeed, there are! Actually does this mean that emacs or org-mode
has to take into consideration every single bit of text in the visible
part buffer of the buffer, whenever I press a key? what needs to be
calculated by simple entering of text?

Gerald

--
Dr. Gerald Wildgruber
Institut für Philosophie, Literatur-, Wissenschafts- und Technikgeschichte
Literaturwissenschaft mit Schwerpunkt Literatur und Wissenschaft
Technische Universität Berlin
Straße des 17. Juni 135
D-10623 Berlin
http://www.philosophie.tu-berlin.de/menue/home/
T. +49 (0)30 314 25924
F. +49 (0)30 314 23107
wildgru...@tu-berlin.de
-
Sent with mu4e

Re: [O] Org mode in combination with emacs follow-mode is terrible

[Joost Kremers]

On Wed, Jun 13 2018, Eric S Fraga wrote:

On Wednesday, 13 Jun 2018 at 09:53, Gerald Wildgruber wrote:
Switching to text-mode, with 5 windows and follow-mode still 
being

active reduces lag significantly.

So there must be an issue specifically with the combination of 
org-mode

and follow-mode!


I don't think there's an issue per se in the sense of bugs.  Org 
does
much more processing of the text than does text mode so if you 
have 60k
worth of text to process each time you type something, it's 
probably not

surprising that there is a lag.


Actually, I would suspect it's more of a problem for follow-mode 
than org-mode, because follow-mode needs to keep the different 
windows in sync. For this, it adds a function to 
`post-command-hook', which means it's run after every key press.


It's not inconceivable that `follow-mode' does something that is 
extra time-consuming in an Org buffer. To find out what that might 
be, you could try the Elisp profiler that comes with Emacs. See 
the section "Profiling" in the Elisp manual for details.


Once you've found out which function(s) consume so much time, it 
might be possible to ask in here or on emacs-devel what exactly is 
causing the problem and whether there's a way around it.


--
Joost Kremers
Life has its moments

Re: [O] Org mode in combination with emacs follow-mode is terrible

[Eric S Fraga]

On Wednesday, 13 Jun 2018 at 09:53, Gerald Wildgruber wrote:
> Switching to text-mode, with 5 windows and follow-mode still being
> active reduces lag significantly.
>
> So there must be an issue specifically with the combination of org-mode
> and follow-mode!

I don't think there's an issue per se in the sense of bugs.  Org does
much more processing of the text than does text mode so if you have 60k
worth of text to process each time you type something, it's probably not
surprising that there is a lag.  60k is a lot of text and I assume there
are many headings etc.?  Part of the attraction of org mode is the
visual representation of the text and this unfortunately comes at a
cost.

I cannot remember what version of Emacs you are using.  If not the
latest, it might be worth trying v26.1 or even one of the latest
snapshots in case?


-- 
Eric S Fraga via Emacs 25.2.2, Org release_9.1.13-791-g842002


signature.asc
Description: PGP signature

Re: [O] Org mode in combination with emacs follow-mode is terrible

[Gerald Wildgruber]

Switching to text-mode, with 5 windows and follow-mode still being
active reduces lag significantly.

So there must be an issue specifically with the combination of org-mode
and follow-mode!

Gerald.

On Di, Jun 12 2018, Eric S Fraga  wrote:

> On Tuesday, 12 Jun 2018 at 12:23, Gerald Wildgruber wrote:
>> Hi Eric,
>>
>> thanks for the input: indeed, I always use at least five windows (on a
>> 40" display), as this setup displays simultanously almost 60Kb of text,
>> an entire papaer, which is excellent!
>
> That's a lot of text so maybe it's really not surprising maybe that
> there is a lag.  What happens if you edit the same file in text-mode?
>
>> Elsewise: do you see any reason or issue with both modes enabled that
>> could lead to such behavior: it would seem that emacs tries to
>> calculate something with every new keystroke, that involves all text
>> before point.
>
> Maybe font-lock and org-indent may impact on this?
>
> I also find that the presence of tables often slows org down although
> it's difficult to quantify the actual impact.


--
Dr. Gerald Wildgruber
Institut für Philosophie, Literatur-, Wissenschafts- und Technikgeschichte
Literaturwissenschaft mit Schwerpunkt Literatur und Wissenschaft
Technische Universität Berlin
Straße des 17. Juni 135
D-10623 Berlin
http://www.philosophie.tu-berlin.de/menue/home/
T. +49 (0)30 314 25924
F. +49 (0)30 314 23107
wildgru...@tu-berlin.de
-
Sent with mu4e

Re: [O] Org mode in combination with emacs follow-mode is terrible

[Gerald Wildgruber]

Thanks! actually every single one of the following does help a bit:

- reducing number of windows to 3
- switching to text-mode
- dectivating org-indent-mode, with org-mode still being active

There's still lag, but not as extreme as with my original setup.

Still, the most significant change occurs by deactivating follow-mode:
every lag simply disappears.

Gerald.

On Di, Jun 12 2018, Eric S Fraga  wrote:

> On Tuesday, 12 Jun 2018 at 12:23, Gerald Wildgruber wrote:
>> Hi Eric,
>>
>> thanks for the input: indeed, I always use at least five windows (on a
>> 40" display), as this setup displays simultanously almost 60Kb of text,
>> an entire papaer, which is excellent!
>
> That's a lot of text so maybe it's really not surprising maybe that
> there is a lag.  What happens if you edit the same file in text-mode?
>
>> Elsewise: do you see any reason or issue with both modes enabled that
>> could lead to such behavior: it would seem that emacs tries to
>> calculate something with every new keystroke, that involves all text
>> before point.
>
> Maybe font-lock and org-indent may impact on this?
>
> I also find that the presence of tables often slows org down although
> it's difficult to quantify the actual impact.


--
Dr. Gerald Wildgruber
Institut für Philosophie, Literatur-, Wissenschafts- und Technikgeschichte
Literaturwissenschaft mit Schwerpunkt Literatur und Wissenschaft
Technische Universität Berlin
Straße des 17. Juni 135
D-10623 Berlin
http://www.philosophie.tu-berlin.de/menue/home/
T. +49 (0)30 314 25924
F. +49 (0)30 314 23107
wildgru...@tu-berlin.de
-
Sent with mu4e

Re: [O] Org mode in combination with emacs follow-mode is terrible

[Eric S Fraga]

On Tuesday, 12 Jun 2018 at 12:23, Gerald Wildgruber wrote:
> Hi Eric,
>
> thanks for the input: indeed, I always use at least five windows (on a
> 40" display), as this setup displays simultanously almost 60Kb of text,
> an entire papaer, which is excellent!

That's a lot of text so maybe it's really not surprising maybe that
there is a lag.  What happens if you edit the same file in text-mode?

> Elsewise: do you see any reason or issue with both modes enabled that
> could lead to such behavior: it would seem that emacs tries to
> calculate something with every new keystroke, that involves all text
> before point.

Maybe font-lock and org-indent may impact on this?

I also find that the presence of tables often slows org down although
it's difficult to quantify the actual impact.

-- 
Eric S Fraga via Emacs 25.2.2, Org release_9.1.13-791-g842002


signature.asc
Description: PGP signature

Re: [O] Org mode in combination with emacs follow-mode is terrible

[Gerald Wildgruber]

Hi Eric,

thanks for the input: indeed, I always use at least five windows (on a
40" display), as this setup displays simultanously almost 60Kb of text,
an entire papaer, which is excellent!

I will try the results with fewer windows tomorrow, when back in office.

Elsewise: do you see any reason or issue with both modes enabled that
could lead to such behavior: it would seem that emacs tries to calculate
something with every new keystroke, that involves all text before point.

Gerald.

On Di, Jun 12 2018, Eric S Fraga  wrote:

> On Monday, 11 Jun 2018 at 14:56, Gerald Wildgruber wrote:
>> My typical setup is to use a maximized or full screen emacs frame split
>
> [...]
>
>> portions towards the end of the file. If I deactivate follow-mode, the
>> problem disappears.
>
> I have a 38" monitor and I frequently do what you say.  However, I
> typically only split the frame into 3 windows.  I don't remember seeing
> any lag.  But I am currently away so cannot verify.  What happens if you
> try with less windows?


--
Dr. Gerald Wildgruber
Institut für Philosophie, Literatur-, Wissenschafts- und Technikgeschichte
Literaturwissenschaft mit Schwerpunkt Literatur und Wissenschaft
Technische Universität Berlin
Straße des 17. Juni 135
D-10623 Berlin
http://www.philosophie.tu-berlin.de/menue/home/
T. +49 (0)30 314 25924
F. +49 (0)30 314 23107
wildgru...@tu-berlin.de
-
Sent with mu4e

Re: [O] Org mode in combination with emacs follow-mode is terrible

[Eric S Fraga]

On Monday, 11 Jun 2018 at 14:56, Gerald Wildgruber wrote:
> My typical setup is to use a maximized or full screen emacs frame split

[...]

> portions towards the end of the file. If I deactivate follow-mode, the
> problem disappears.

I have a 38" monitor and I frequently do what you say.  However, I
typically only split the frame into 3 windows.  I don't remember seeing
any lag.  But I am currently away so cannot verify.  What happens if you
try with less windows?

-- 
Eric S Fraga via Emacs 25.2.2, Org release_9.1.13-791-g842002


signature.asc
Description: PGP signature

Re: [O] Org-mode new website accept PR like GitHub?

[Bastien]

Hi,

"numbch...@gmail.com"  writes:

> Can I send PR to add contrib support at new Org-mode source code
> website like this: https://code.orgmode.org/bzg/org-mode/pulls/1

No, but you can send patches against
https://code.orgmode.org/bzg/orgweb on this list.

-- 
 Bastien

Re: [O] Org-Mode babel and gherkin

[Bastien]

"Charles R (Charlie) Martin"  writes:

> gherkin is the specification language used for behavior-driven design
> in tools like Cucumber.

Thanks,

-- 
 Bastien

Re: [O] Org-Mode babel and gherkin

[Bastien]

Hi Charles,

"Charles R (Charlie) Martin"  writes:

> Has anyone set up a babel language for gherkin?

Would you mind sharing more information on what is gherkin?

Thanks,

-- 
 Bastien

Re: [O] Org-Mode babel and gherkin

[Charles R (Charlie) Martin]

gherkin is the specification language used for behavior-driven design in
tools like Cucumber.

https://github.com/cucumber/cucumber/wiki/Gherkin
https://medium.com/@NeotericEU/speak-gherkin-and-learn-how-to-collect-requirements-for-your-project-dad171da8fb

On Thu, Apr 26, 2018 at 5:34 PM, Bastien  wrote:

> Hi Charles,
>
> "Charles R (Charlie) Martin"  writes:
>
> > Has anyone set up a babel language for gherkin?
>
> Would you mind sharing more information on what is gherkin?
>
> Thanks,
>
> --
>  Bastien
>

Re: [O] Org mode bug submission and viewing?

[Bastien]

Dear all,

reflecting upon Allen's question and Kaushal's answer, I would like
to suggest this rule on how to submit bug reports:

  Use M-x org-submit-bug-report RET if you installed Org yourself,
  use M-x report-emacs-bug RET otherwise.

This way, Org maintainers who check Emacs bugs are likely to quickly
spot if the bug from an old Org version has been fixed already, and
users are less likely to share already-fixed bugs on emacs-orgmode.

WDYT?

-- 
 Bastien

Re: [O] org-mode R using xtable produces strange output

[Brian Shine]

Brilliant!  Thank you so much.

Best wishes,
Brian


> On 20 Mar 2018, at 16:47, Berry, Charles  wrote:
> 
> 
> 
>> On Mar 19, 2018, at 4:44 PM, Brian Shine  wrote:
>> 
>> I am using xtable to produce summary tables of linear models, specifying the 
>> output as latex.  If I just run the code in R, I get the correct output.  
>> However, the latex output in the org document contains a lot of “|”s.  I 
>> think this is because the header of the table contains some code to make “p 
>> > |t|”, where the vertical lines are to indicate “absolute value of t”.  My 
>> guess is that when the output is written to the results section, org 
>> interprets the “|” signs as an org-table and tries to be helpful by adding 
>> more of them to make up the correct number of columns. 
> 
> 
> See
> 
>   (info "(org) results")
> 
> and note the difference between `:results output' and `:results value' (the 
> default).
> 
> Since you want the printed version of the R object, you should use 
> 
>   `:results output latex'
> 
> to pass the printed output to the org #+Results or 
> 
>   `:results raw :wrap export latex'
> 
> to pass the unadorned value.  In your use case they seem to produce the same 
> #+Results.
> 
> HTH,
> 
> Chuck

Re: [O] org-mode R using xtable produces strange output

[Berry, Charles]

> On Mar 19, 2018, at 4:44 PM, Brian Shine  wrote:
> 
> I am using xtable to produce summary tables of linear models, specifying the 
> output as latex.  If I just run the code in R, I get the correct output.  
> However, the latex output in the org document contains a lot of “|”s.  I 
> think this is because the header of the table contains some code to make “p > 
> |t|”, where the vertical lines are to indicate “absolute value of t”.  My 
> guess is that when the output is written to the results section, org 
> interprets the “|” signs as an org-table and tries to be helpful by adding 
> more of them to make up the correct number of columns. 


See

(info "(org) results")

and note the difference between `:results output' and `:results value' (the 
default).

Since you want the printed version of the R object, you should use 

`:results output latex'

to pass the printed output to the org #+Results or 

`:results raw :wrap export latex'

to pass the unadorned value.  In your use case they seem to produce the same 
#+Results.

HTH,

Chuck

Re: [O] org mode error "pdf wasn't produced"

[Dereje Tefera]

Hi Everyone,

Thank you for your help. Problem fixed. I had to install MIkTex and
reinstall Emacs and all running well so far.


Thank you very much for time

Regards

Dereje



On Thu, Mar 15, 2018 at 10:09 AM, John Hendy  wrote:

> On Thu, Mar 15, 2018 at 10:06 AM, R Jain  wrote:
> > Hi Dereje,
> >
> > Two things:
> > 1) Pygmentize is a python package. I hope you meant trying to install it
> for
> > python, and not Latex or Emacs.
> > http://pygments.org/docs/cmdline/
> > 2) Which Tex software are you using? I recall having some compilation
> errors
> > (last year) when I was setting this up with org-mode. Though I can't put
> my
> > finger on what solved the problem, it was after I installed TexMaker. A
> > friend suggested that it has a very decent library.
> >
> > So, if you have installed the vanilla Miktex, or something else, I'd
> > recommend giving TexMaker a try. Don't recall ever having to open it up
> > though.
>
> I have successfully used MikTex in the past and definitely remember
> having an initial setup cycle of trying to export, checking the Org
> PDF Latex buffer, identifying the missing package(s), installing via
> the MikTex GUI, and repeating until all the errors went away. This may
> be purely because I default to a lean system and don't go for these
> huge meta-packages. If one chooses to install the [La/Lua/Xe]Tex
> world, this might not be the case! I have the same procedure on linux
> with TexLive where I have a default starting set of pkgs and just run
> tlmgr on whatever errors I encounter.
>
> Just one other data point!
>
> The first step is to make sure "pdflatex" is recognized, period. This
> is still not answered.
>
> John
>
> >
> > Let us know. Good luck.
> >
> > --Rishabh
> >
> >
> > On Mar 14 2018, at 3:24 pm, Dereje Tefera  wrote:
> >
> >
> > I saw that there is one error:
> >
> >  "! Package minted Error: You must have `pygmentize' installed to use
> this
> > package." but   when I try to install from the package list says no
> match.
> > and a warning:
> >
> > "Package inputenc Warning: inputenc package ignored with utf8 based
> > engines."
> >
> >
> >
> > Do you think it would be better to reinstall emacs?
> >
> >
> > Regards
> >
> > Dereje
> >
> >
> > On Wed, Mar 14, 2018 at 12:28 PM, Eric S Fraga 
> wrote:
> >
> > On Wednesday, 14 Mar 2018 at 11:39, Dereje Tefera wrote:
> >> Dear John and R Jain,
> >>
> >> I have done all required installation for the Latex and it worked for a
> >> couple of times but it  then crashes. This is the error message I am
> >> getting while trying to export to Latex PDF or Beamer. I really
> appreciate
> >> your cooperation but I completely if you are busy.
> >
> > So, it looks like LaTeX is now being found but that there are errors in
> > the LaTeX created by org.  Have you looked at the LaTeX output buffer,
> > as the error message suggests?
> >
> >> Debugger entered--Lisp error: (error "File
> >> \"c:/Users/deret/Desktop/examp3.pdf\" wasn’t produced.  See \"*Org PDF
> >> LaTeX Output*\" for details")
> >
> > The error will likely be near the end of the buffer.
> >
> > --
> > Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-303-g6cf5fc.dirty
>

Re: [O] org mode error "pdf wasn't produced"

[John Hendy]

On Thu, Mar 15, 2018 at 10:06 AM, R Jain  wrote:
> Hi Dereje,
>
> Two things:
> 1) Pygmentize is a python package. I hope you meant trying to install it for
> python, and not Latex or Emacs.
> http://pygments.org/docs/cmdline/
> 2) Which Tex software are you using? I recall having some compilation errors
> (last year) when I was setting this up with org-mode. Though I can't put my
> finger on what solved the problem, it was after I installed TexMaker. A
> friend suggested that it has a very decent library.
>
> So, if you have installed the vanilla Miktex, or something else, I'd
> recommend giving TexMaker a try. Don't recall ever having to open it up
> though.

I have successfully used MikTex in the past and definitely remember
having an initial setup cycle of trying to export, checking the Org
PDF Latex buffer, identifying the missing package(s), installing via
the MikTex GUI, and repeating until all the errors went away. This may
be purely because I default to a lean system and don't go for these
huge meta-packages. If one chooses to install the [La/Lua/Xe]Tex
world, this might not be the case! I have the same procedure on linux
with TexLive where I have a default starting set of pkgs and just run
tlmgr on whatever errors I encounter.

Just one other data point!

The first step is to make sure "pdflatex" is recognized, period. This
is still not answered.

John

>
> Let us know. Good luck.
>
> --Rishabh
>
>
> On Mar 14 2018, at 3:24 pm, Dereje Tefera  wrote:
>
>
> I saw that there is one error:
>
>  "! Package minted Error: You must have `pygmentize' installed to use this
> package." but   when I try to install from the package list says no match.
> and a warning:
>
> "Package inputenc Warning: inputenc package ignored with utf8 based
> engines."
>
>
>
> Do you think it would be better to reinstall emacs?
>
>
> Regards
>
> Dereje
>
>
> On Wed, Mar 14, 2018 at 12:28 PM, Eric S Fraga  wrote:
>
> On Wednesday, 14 Mar 2018 at 11:39, Dereje Tefera wrote:
>> Dear John and R Jain,
>>
>> I have done all required installation for the Latex and it worked for a
>> couple of times but it  then crashes. This is the error message I am
>> getting while trying to export to Latex PDF or Beamer. I really appreciate
>> your cooperation but I completely if you are busy.
>
> So, it looks like LaTeX is now being found but that there are errors in
> the LaTeX created by org.  Have you looked at the LaTeX output buffer,
> as the error message suggests?
>
>> Debugger entered--Lisp error: (error "File
>> \"c:/Users/deret/Desktop/examp3.pdf\" wasn’t produced.  See \"*Org PDF
>> LaTeX Output*\" for details")
>
> The error will likely be near the end of the buffer.
>
> --
> Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-303-g6cf5fc.dirty

Re: [O] org mode error "pdf wasn't produced"

[R Jain]

Hi Dereje,

Two things:
1) Pygmentize is a python package. I hope you meant trying to install it for 
python, and not Latex or Emacs.
http://pygments.org/docs/cmdline/
2) Which Tex software are you using? I recall having some compilation errors 
(last year) when I was setting this up with org-mode. Though I can't put my 
finger on what solved the problem, it was after I installed TexMaker. A friend 
suggested that it has a very decent library.
So, if you have installed the vanilla Miktex, or something else, I'd recommend 
giving TexMaker a try. Don't recall ever having to open it up though.
Let us know. Good luck.
--Rishabh

On Mar 14 2018, at 3:24 pm, Dereje Tefera  wrote:
>
> I saw that there is one error:
>
> "! Package minted Error: You must have `pygmentize' installed to use this 
> package." but when I try to install from the package list says no match.
> and a warning:
>
> "Package inputenc Warning: inputenc package ignored with utf8 based engines."
>
>
>
>
> Do you think it would be better to reinstall emacs?
>
>
> Regards
>
> Dereje
>
>
> On Wed, Mar 14, 2018 at 12:28 PM, Eric S Fraga  (mailto:esfli...@gmail.com)> wrote:
> > On Wednesday, 14 Mar 2018 at 11:39, Dereje Tefera wrote:
> > > Dear John and R Jain,
> > >
> > > I have done all required installation for the Latex and it worked for a
> > > couple of times but it then crashes. This is the error message I am
> > > getting while trying to export to Latex PDF or Beamer. I really appreciate
> > > your cooperation but I completely if you are busy.
> >
> > So, it looks like LaTeX is now being found but that there are errors in
> > the LaTeX created by org. Have you looked at the LaTeX output buffer,
> > as the error message suggests?
> >
> > > Debugger entered--Lisp error: (error "File
> > > \"c:/Users/deret/Desktop/examp3.pdf\" wasn’t produced. See \"*Org PDF 
> > > LaTeX Output*\" for details")
> >
> > The error will likely be near the end of the buffer.
> > --
> > Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-303-g6cf5fc.dirty
>
>
>
>

Re: [O] org mode error "pdf wasn't produced"

[John Kitchin]

that probably means run:

pip install pygments

at a command line, assuming you have a working Python installation. If not,
you can either get one, or don't use minted for syntax highlighting.

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 Wed, Mar 14, 2018 at 12:24 PM, Dereje Tefera  wrote:

> I saw that there is one error:
>
>  "! Package minted Error: You must have `pygmentize' installed to use this
> package." but   when I try to install from the package list says no match.
> and a warning:
>
> "Package inputenc Warning: inputenc package ignored with utf8 based
> engines."
>
>
>
> Do you think it would be better to reinstall emacs?
>
>
> Regards
>
> Dereje
>
>
>
> On Wed, Mar 14, 2018 at 12:28 PM, Eric S Fraga  wrote:
>
>> On Wednesday, 14 Mar 2018 at 11:39, Dereje Tefera wrote:
>> > Dear John and R Jain,
>> >
>> > I have done all required installation for the Latex and it worked for a
>> > couple of times but it  then crashes. This is the error message I am
>> > getting while trying to export to Latex PDF or Beamer. I really
>> appreciate
>> > your cooperation but I completely if you are busy.
>>
>> So, it looks like LaTeX is now being found but that there are errors in
>> the LaTeX created by org.  Have you looked at the LaTeX output buffer,
>> as the error message suggests?
>>
>> > Debugger entered--Lisp error: (error "File
>> > \"c:/Users/deret/Desktop/examp3.pdf\" wasn’t produced.  See \"*Org PDF
>> LaTeX Output*\" for details")
>>
>> The error will likely be near the end of the buffer.
>>
>> --
>> Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-303-g6cf5fc.dirty
>>
>
>

Re: [O] org mode error "pdf wasn't produced"

[Dereje Tefera]

I saw that there is one error:

 "! Package minted Error: You must have `pygmentize' installed to use this
package." but   when I try to install from the package list says no match.
and a warning:

"Package inputenc Warning: inputenc package ignored with utf8 based
engines."



Do you think it would be better to reinstall emacs?


Regards

Dereje



On Wed, Mar 14, 2018 at 12:28 PM, Eric S Fraga  wrote:

> On Wednesday, 14 Mar 2018 at 11:39, Dereje Tefera wrote:
> > Dear John and R Jain,
> >
> > I have done all required installation for the Latex and it worked for a
> > couple of times but it  then crashes. This is the error message I am
> > getting while trying to export to Latex PDF or Beamer. I really
> appreciate
> > your cooperation but I completely if you are busy.
>
> So, it looks like LaTeX is now being found but that there are errors in
> the LaTeX created by org.  Have you looked at the LaTeX output buffer,
> as the error message suggests?
>
> > Debugger entered--Lisp error: (error "File
> > \"c:/Users/deret/Desktop/examp3.pdf\" wasn’t produced.  See \"*Org PDF
> LaTeX Output*\" for details")
>
> The error will likely be near the end of the buffer.
>
> --
> Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-303-g6cf5fc.dirty
>

Re: [O] org mode error "pdf wasn't produced"

[Eric S Fraga]

On Wednesday, 14 Mar 2018 at 11:39, Dereje Tefera wrote:
> Dear John and R Jain,
>
> I have done all required installation for the Latex and it worked for a
> couple of times but it  then crashes. This is the error message I am
> getting while trying to export to Latex PDF or Beamer. I really appreciate
> your cooperation but I completely if you are busy.

So, it looks like LaTeX is now being found but that there are errors in
the LaTeX created by org.  Have you looked at the LaTeX output buffer,
as the error message suggests?

> Debugger entered--Lisp error: (error "File
> \"c:/Users/deret/Desktop/examp3.pdf\" wasn’t produced.  See \"*Org PDF LaTeX 
> Output*\" for details")

The error will likely be near the end of the buffer.

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-303-g6cf5fc.dirty


signature.asc
Description: PGP signature

Re: [O] org mode error "pdf wasn't produced"

[Dereje Tefera]

Dear John and R Jain,

I have done all required installation for the Latex and it worked for a
couple of times but it  then crashes. This is the error message I am
getting while trying to export to Latex PDF or Beamer. I really appreciate
your cooperation but I completely if you are busy.



Debugger entered--Lisp error: (error "File
\"c:/Users/deret/Desktop/examp3.pdf\" wasn’t produced.  See \"*Org PDF
LaTeX Output*\" for details")
  signal(error ("File \"c:/Users/deret/Desktop/examp3.pdf\" wasn’t
produced.  See \"*Org PDF LaTeX Output*\" for details"))
  error("File \"c:/Users/deret/Desktop/examp3.pdf\" wasn't produced.  See
\"*Org PDF LaTeX Output*\" for details")
  org-compile-file("examp3.tex" ("xelatex -shell-escape -interaction
nonstopmode -output-directory %o %f" "xelatex -shell-escape -interaction
nonstopmode -output-directory %o %f" "xelatex -shell-escape -interaction
nonstopmode -output-directory %o %f") "pdf" "See \"*Org PDF LaTeX Output*\"
for details" # ((66 . "\"bibtex\"") (76 .
"\"pdflatex\"")))
  (let* ((compiler (or (let ((temp-buffer (generate-new-buffer " *temp*")))
(save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn ...
...) (and ... ... "pdflatex")) (process (if (functionp
org-latex-pdf-process) org-latex-pdf-process (mapcar (function (lambda
(command) (replace-regexp-in-string "%\\(?:bib\\|la\\)tex\\>" ...
command))) org-latex-pdf-process))) (spec (list (cons 66
(shell-quote-argument org-latex-bib-compiler)) (cons 76
(shell-quote-argument compiler (log-buf-name "*Org PDF LaTeX Output*")
(log-buf (and (not snippet) (get-buffer-create log-buf-name))) (outfile
(org-compile-file texfile process "pdf" (format "See %S for details"
log-buf-name) log-buf spec))) (if snippet nil (if org-latex-remove-logfiles
(progn (mapc (function delete-file) (directory-files (file-name-directory
outfile) t (concat (regexp-quote ...) "\\(?:\\.[0-9]+\\)?\\." (regexp-opt
org-latex-logfiles-extensions)) t (let ((warnings
(org-latex--collect-warnings log-buf))) (message (concat "PDF file
produced" (cond ((eq warnings ...) " with errors.") (warnings (concat "
with warnings: " warnings)) (t ".")) outfile)
  org-latex-compile("examp3.tex")
  (closure ((outfile . "examp3.tex") (ext-plist) (body-only) (visible-only)
(subtreep) (async) t) (file) (org-latex-compile file))("examp3.tex")
  funcall((closure ((outfile . "examp3.tex") (ext-plist) (body-only)
(visible-only) (subtreep) (async) t) (file) (org-latex-compile file))
"examp3.tex")
  (and (functionp post-process) (funcall post-process file))
  (or (and (functionp post-process) (funcall post-process file)) file)
  (let ((output (org-export-as backend subtreep visible-only body-only
ext-plist))) (let ((temp-buffer (generate-new-buffer " *temp*")))
(save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn
(insert output) (let ((coding-system-for-write encoding)) (write-file
file))) (and (buffer-name temp-buffer) (kill-buffer temp-buffer) (if
(and (org-export--copy-to-kill-ring-p) (org-string-nw-p output)) (progn
(org-kill-new output))) (or (and (functionp post-process) (funcall
post-process file)) file))
  (if async (let ((with-temp-message "Initializing asynchronous export
process") (current-message)) (unwind-protect (progn (if with-temp-message
(progn (setq current-message (current-message)) (message "%s"
with-temp-message))) (let ((--copy-fun (org-export--generate-copy-script
...)) (--temp-file (make-temp-file "org-export-process")) (--coding
buffer-file-coding-system)) (let ((temp-file --temp-file) (temp-buffer
...)) (unwind-protect (prog1 ... ...) (and ... ...))) (let*
((process-connection-type nil) (--proc-buffer ...) (--process ...))
(org-export-add-to-stack (get-buffer --proc-buffer) nil --process) (let
(...) (set-process-sentinel --process ...) (and with-temp-message (if
current-message (message "%s" current-message) (message nil) (let
((output (org-export-as backend subtreep visible-only body-only
ext-plist))) (let ((temp-buffer (generate-new-buffer " *temp*")))
(save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn
(insert output) (let (...) (write-file file))) (and (buffer-name
temp-buffer) (kill-buffer temp-buffer) (if (and
(org-export--copy-to-kill-ring-p) (org-string-nw-p output)) (progn
(org-kill-new output))) (or (and (functionp post-process) (funcall
post-process file)) file)))
  (let ((ext-plist (org-combine-plists (list (quote :output-file) file)
ext-plist)) (encoding (or org-export-coding-system
buffer-file-coding-system))) (if async (let ((with-temp-message
"Initializing asynchronous export process") (current-message))
(unwind-protect (progn (if with-temp-message (progn (setq current-message
...) (message "%s" with-temp-message))) (let ((--copy-fun ...) (--temp-file
...) (--coding buffer-file-coding-system)) (let (... ...) (unwind-protect
... ...)) (let* (... ... ...) (org-export-add-to-stack ... nil --process)
(let ... ... (and with-temp-message (if current-message 

Re: [O] org mode error "pdf wasn't produced"

[John Hendy]

Oops. Sincere apologies for misspelling your name, Dereje! I misread
in my hasty skim.

John

On Tue, Mar 13, 2018 at 8:28 PM, John Hendy  wrote:
> Dejere,
>
>
> Org-mode is not able to find your latex installation. That's the
> problem, just as it says: it's trying to run the compilation command,
> `pdflatex` and it can find no such thing.
>
> Either it's not installed, or it's not in your path. The more details
> you can provide, the better. For starters 1) what latex variant is
> installed and 2) is it in your path (and how do you know)?
>
>
> Best regards,
> John

Re: [O] org mode error "pdf wasn't produced"

[John Hendy]

Dejere,


Org-mode is not able to find your latex installation. That's the
problem, just as it says: it's trying to run the compilation command,
`pdflatex` and it can find no such thing.

Either it's not installed, or it's not in your path. The more details
you can provide, the better. For starters 1) what latex variant is
installed and 2) is it in your path (and how do you know)?


Best regards,
John

On Tue, Mar 13, 2018 at 7:29 PM, Dereje Tefera  wrote:
>
> Hi Prof. Kitchin and others,
>
> I am using Emacs-org-mode on a windows machine and launch the program from 
> the desktop shortcut.
>
>
>
>
> Regards
>
> Dereje
>
>
>
> On Tue, Mar 13, 2018 at 6:05 PM, John Kitchin  wrote:
>>
>> That means emacs is not finding pdflatex on your path.
>>
>> A little more information might help.
>>
>> 1. In a terminal, if you type:
>>
>> > which pdflatex
>>
>> to you get anything?
>>
>> 2. How do you launch emacs? If you are launching it from some icon, you 
>> might not be getting the same path environment as from a shell.
>>
>> 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 Tue, Mar 13, 2018 at 4:37 PM, Dereje Tefera  wrote:
>>>
>>> Hi Everyone,
>>>
>>> thank you very much for the response.
>>>
>>> Rishabh, yes i have check the link you mentioned.
>>>
>>> the error  says "'pdflatex"' is not recognized as an internal or external 
>>> command,
>>> operable program or batch file." but i have that in my init.el file 
>>> configured.
>>>
>>>
>>>
>>>
>>>
>>>
>>> Regards
>>>
>>> Dereje
>>>
>>>
>>>
>>> On Tue, Mar 13, 2018 at 6:28 AM, R Jain  wrote:

 Hi Dereje,

 Have you already looked at (8) from 
 https://orgmode.org/worg/org-tutorials/org-latex-export.html?

 --Rishabh

 On Mar 12 2018, at 5:40 pm, Dereje Tefera  wrote:
>
> Dear good team of Org-mode,
>
> I am using org-mode in the Emacs, but I have a problem exporting to 
> Latex,  PDF.
>
> "I always have this message that says, PDF was not produced, when i try 
> to export to latex pdf.
>
>
> I can export to HTML or tet latex but not to pdf.
>
>
> Any help would be highly appreciated.
>
>
> Thank you for your time.
>
>
>
> Regards
>
> Dereje
>
>
>>>
>>
>

Re: [O] org mode error "pdf wasn't produced"

[Dereje Tefera]

Hi Prof. Kitchin and others,

I am using Emacs-org-mode on a windows machine and launch the program from
the desktop shortcut.




Regards

Dereje



On Tue, Mar 13, 2018 at 6:05 PM, John Kitchin 
wrote:

> That means emacs is not finding pdflatex on your path.
>
> A little more information might help.
>
> 1. In a terminal, if you type:
>
> > which pdflatex
>
> to you get anything?
>
> 2. How do you launch emacs? If you are launching it from some icon, you
> might not be getting the same path environment as from a shell.
>
> John
>
> ---
> Professor John Kitchin
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803 <(412)%20268-7803>
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
>
>
> On Tue, Mar 13, 2018 at 4:37 PM, Dereje Tefera  wrote:
>
>> Hi Everyone,
>>
>> thank you very much for the response.
>>
>> Rishabh, yes i have check the link you mentioned.
>>
>> the error  says "'pdflatex"' is not recognized as an internal or external
>> command,
>> operable program or batch file." but i have that in my init.el file
>> configured.
>>
>>
>>
>>
>>
>>
>> Regards
>>
>> Dereje
>>
>>
>>
>> On Tue, Mar 13, 2018 at 6:28 AM, R Jain  wrote:
>>
>>> Hi Dereje,
>>>
>>> Have you already looked at (8) from https://orgmode.org/worg/
>>> org-tutorials/org-latex-export.html?
>>>
>>> --Rishabh
>>>
>>> On Mar 12 2018, at 5:40 pm, Dereje Tefera  wrote:
>>>
 Dear good team of Org-mode,

 I am using org-mode in the Emacs, but I have a problem exporting to
 Latex,  PDF.

 "I always have this message that says, PDF was not produced, when i try
 to export to latex pdf.


 I can export to HTML or tet latex but not to pdf.


 Any help would be highly appreciated.


 Thank you for your time.



 Regards

 Dereje



>>
>

Re: [O] org mode error "pdf wasn't produced"

[John Kitchin]

That means emacs is not finding pdflatex on your path.

A little more information might help.

1. In a terminal, if you type:

> which pdflatex

to you get anything?

2. How do you launch emacs? If you are launching it from some icon, you
might not be getting the same path environment as from a shell.

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 Tue, Mar 13, 2018 at 4:37 PM, Dereje Tefera  wrote:

> Hi Everyone,
>
> thank you very much for the response.
>
> Rishabh, yes i have check the link you mentioned.
>
> the error  says "'pdflatex"' is not recognized as an internal or external
> command,
> operable program or batch file." but i have that in my init.el file
> configured.
>
>
>
>
>
>
> Regards
>
> Dereje
>
>
>
> On Tue, Mar 13, 2018 at 6:28 AM, R Jain  wrote:
>
>> Hi Dereje,
>>
>> Have you already looked at (8) from https://orgmode.org/worg/
>> org-tutorials/org-latex-export.html?
>>
>> --Rishabh
>>
>> On Mar 12 2018, at 5:40 pm, Dereje Tefera  wrote:
>>
>>> Dear good team of Org-mode,
>>>
>>> I am using org-mode in the Emacs, but I have a problem exporting to
>>> Latex,  PDF.
>>>
>>> "I always have this message that says, PDF was not produced, when i try
>>> to export to latex pdf.
>>>
>>>
>>> I can export to HTML or tet latex but not to pdf.
>>>
>>>
>>> Any help would be highly appreciated.
>>>
>>>
>>> Thank you for your time.
>>>
>>>
>>>
>>> Regards
>>>
>>> Dereje
>>>
>>>
>>>
>

Re: [O] org mode error "pdf wasn't produced"

[Dereje Tefera]

Hi Everyone,

thank you very much for the response.

Rishabh, yes i have check the link you mentioned.

the error  says "'pdflatex"' is not recognized as an internal or external
command,
operable program or batch file." but i have that in my init.el file
configured.






Regards

Dereje



On Tue, Mar 13, 2018 at 6:28 AM, R Jain  wrote:

> Hi Dereje,
>
> Have you already looked at (8) from https://orgmode.org/worg/
> org-tutorials/org-latex-export.html?
>
> --Rishabh
>
> On Mar 12 2018, at 5:40 pm, Dereje Tefera  wrote:
>
>> Dear good team of Org-mode,
>>
>> I am using org-mode in the Emacs, but I have a problem exporting to
>> Latex,  PDF.
>>
>> "I always have this message that says, PDF was not produced, when i try
>> to export to latex pdf.
>>
>>
>> I can export to HTML or tet latex but not to pdf.
>>
>>
>> Any help would be highly appreciated.
>>
>>
>> Thank you for your time.
>>
>>
>>
>> Regards
>>
>> Dereje
>>
>>
>>

Re: [O] org mode error "pdf wasn't produced"

[Eric S Fraga]

On Monday, 12 Mar 2018 at 15:40, Dereje Tefera wrote:
> I can export to HTML or tet latex but not to pdf.
> Any help would be highly appreciated.

Switch to the buffer "*Org PDF LaTeX Output*" and scroll through it to
see what errors LaTeX generated in trying to generate the PDF.

You could also have a look at the LaTeX file created by org.

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-191-g90607d


signature.asc
Description: PGP signature

Re: [O] org mode error "pdf wasn't produced"

[R Jain]

Hi Dereje,Have you already looked at (8) from https://orgmode.org/worg/org-tutorials/org-latex-export.html?--Rishabh
  

On Mar 12 2018, at 5:40 pm, Dereje Tefera  wrote:


  Dear good team of Org-mode,I am using org-mode in the Emacs, but I have a problem exporting to Latex,  PDF."I always have this message that says, PDF was not produced, when i try to export to latex pdf. I can export to HTML or tet latex but not to pdf. Any help would be highly appreciated.Thank you for your time.RegardsDereje 



  

Re: [O] org-mode source code repo make error

[numbch...@gmail.com]

I did'nt use `make -C lisp compile`. I just use `make` and `make compile`.
Check out my original email, it's the output from command `make`.

I did a search, found this `make -C lisp compile` is from `mk/targets.mk`.

[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter:  @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36  CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/

On Fri, Feb 2, 2018 at 12:18 PM, Yasushi SHOJI 
wrote:

> Hi,
>
> On Fri, Feb 2, 2018 at 10:24 AM, numbch...@gmail.com
>  wrote:
> > When I try to compile with command `make`, but got this output:
> [...]
> > make -C lisp compile
>
> just do `make compile`.
>
> you can't use `-C` in org-mode source tree.
> In my case with `-C`, I get:
>
> $ make -C lisp compile
> make: Entering directory '/home/yashi/src/org-mode/lisp'
> Makefile:4: *** This make needs to be started as a sub-make from the
> toplevel directory..  Stop.
> make: Leaving directory '/home/yashi/src/org-mode/lisp'
>
> $ git describe
> release_9.1.6-419-g4b2006db3
>
>
> `make help` for more option.
> --
>yashi
>

Re: [O] org-mode source code repo make error

[Yasushi SHOJI]

Hi,

On Fri, Feb 2, 2018 at 10:24 AM, numbch...@gmail.com
 wrote:
> When I try to compile with command `make`, but got this output:
[...]
> make -C lisp compile

just do `make compile`.

you can't use `-C` in org-mode source tree.
In my case with `-C`, I get:

$ make -C lisp compile
make: Entering directory '/home/yashi/src/org-mode/lisp'
Makefile:4: *** This make needs to be started as a sub-make from the
toplevel directory..  Stop.
make: Leaving directory '/home/yashi/src/org-mode/lisp'

$ git describe
release_9.1.6-419-g4b2006db3


`make help` for more option.
-- 
   yashi

Re: [O] Org mode bug submission and viewing?

[Adonay Felipe Nogueira]

If I recall correctly, org-mode uses GNU's Debbugs, see
.

Reports are sent to .

The report-emacs-bug procedure already sets almost everything for you,
including the address mentioned above.

I hope this helps. ;)

2017-12-01T20:05:03-0800 Allen Li wrote:
> What's the proper way to submit an Org mode bug, and are the bugs
> collected anywhere for viewing their status?
>
> I see the mailing list has bugs generated using org-submit-bug-report
> (containing "Bug:" in the subject) and other bugs that have numbers
> ("bug#:" in the subject).
>
> Is there a preferred way to submit bugs?
>
> Where are the numbered bugs coming from?
>
> Is there a place to view submitted bugs and their resolution status?

-- 
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
  gratis).
- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar
  instantaneamente comigo no endereço abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
  Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
  GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
  (apenas sem DRM), PNG, TXT, WEBM.

Re: [O] Org mode bug submission and viewing?

[Kaushal Modi]

TL;DR M-x org-submit-bug-report

On Fri, Dec 1, 2017 at 11:05 PM Allen Li  wrote:

> What's the proper way to submit an Org mode bug,


M-x org-submit-bug-report

Then follow the prompts.. you will end up with an email message buffer. If
your emacs is set up to send emails, just send that email after adding
additional information about the bug.

Else. copy the body of that email, paste it in your email client (like
Gmail, Google Inbox, etc), also copy the auto-generated subject like:

Bug: My bug [9.1.3 (release_9.1.3-203-g33d554 @
/home/kmodi/usr_local/apps/6/emacs/emacs-26/share/emacs/site-lisp/org/)]

, and send that email to emacs-orgmode@gnu.org.

Include a MWE (minimum working example) in your bug report on how to
recreate that issue in an emacs -Q session loaded with that specific Org
version.

and are the bugs
> collected anywhere for viewing their status?
>

I don't believe so.


> I see the mailing list has bugs generated using org-submit-bug-report
> (containing "Bug:" in the subject)


That's generated using the above method.


> and other bugs that have numbers ("bug#:" in the subject).
>

Those are the Org related bugs sent by users using M-x report-emacs-bug.
/Those/ get tracked, auto-assigned with a number and you can see those at
http://lists.gnu.org/r/bug-gnu-emacs/.


> Is there a preferred way to submit bugs?
>

As a user, and frequent observer of this list, the first method is
preferred and gets dealt with in a speedy manner. Because not everyone
following the official emacs bug list use Org. Occassionally though,
someone would be kind enough to forward Org-related bugs from that list to
this list.

Where are the numbered bugs coming from?
>

M-x report-emacs-bug


> Is there a place to view submitted bugs and their resolution status?
>

 Not that I know of. This seems to be an unofficial place to list those,
and doesn't look updated.
-- 

Kaushal Modi

Re: [O] org-mode alarms

[Eric S Fraga]

On Friday, 24 Nov 2017 at 20:37, ma343...@openmailbox.org wrote:
> What are good ways of setting up alarms for Deadlines and Scheduling
> in org-mode to integrate with Windows or GNU/Linux environments?

I use the following on Linux and it works very well.  Relies on there
being a notification daemon running (I use dunst as the easiest to
configure).

#+begin_src emacs-lisp
  ;; from Tassilo's blog:
  ;; and from RichardRiley's entry: http://www.emacswiki.org/emacs/OrgMode-OSD
  ;; and from Nick Dokos: http://article.gmane.org/gmane.emacs.orgmode/5271
  (message "ESF-ORG: setting up org->appt link")
  (require 'appt)
  (require 'notifications)
  (defun esf/notification-display (min-to-app new-time msg)
(let (m delay)
  (setq m (string-to-number min-to-app)
delay (if (<= m 0) 0 (* 1000 (- 20 m
  (notifications-notify :title "Agenda"
:body (format "%s\nIn %s minutes." msg min-to-app)
:app-name "emacs"
:app-icon "PATHTOICONS/emacs-icon.xpm"
:timeout delay)))
  (setq appt-display-format 'window)
  (setq appt-disp-window-function (function esf/notification-display))
  (setq appt-delete-window-function '(lambda ()))
  ;; Run once, activate and schedule refresh
  (run-at-time "5 minutes" 3600 'org-agenda-to-appt)
  (appt-activate t)
  (setq appt-time-msg-list nil)
  (defadvice  org-agenda-redo (after org-agenda-redo-add-appts)
"Pressing `r' on the agenda will also add appointments."
(progn 
  (setq appt-time-msg-list nil)
  (org-agenda-to-appt)))
  (ad-activate 'org-agenda-redo)
  (message "ESF-ORG: done setting up org->appt link")
#+end_src

-- 
: Eric S Fraga via Emacs 27.0.50, Org release_9.1.3-170-g51234f


signature.asc
Description: PGP signature

Re: [O] org-mode alarms

[Samuel Wales]

appt in emacs can do a bunch and is integrated.  i use it.

there are various notify programs that i have not gotten to work.

i use crontab updated in a single babel block to run ddccontrol and
redshift.  this is useful for executive function.  you make the screen
unusable until you have taken medicine or whatever.  then you turn off
the monitor with ddccontrol so that its backlight doesn't further
disrupt your melatonin.  [no amount of dimming achieves that with
today's panel tech at my monitor size.]

-- 
The Kafka Pandemic: 

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
.

Re: [O] org-mode gets confused with column widths when 'time-stamp-custom-formats' are applied.

[Ruy Exel]

Wow!  That was quick.  Thanks.

Ruy

On Nov 15, 2017 15:15, "Nicolas Goaziou"  wrote:

> Hello,
>
> Ruy Exel  writes:
>
> > Consider the table below:
> >
> > | Name  | Date of Birth|
> > |---+--|
> > | John  | <1978-11-14 Tue> |
> > | Peter | <1970-11-14 Sat> |
> > |---+--|
> >
> > Suppose we want to format time stamps differently, such as with the
> > following elisp commands:
> >
> > (setq org-time-stamp-custom-formats (quote ("<%d %b %y>" . "<%m/%d/%y %a
> > %H:%M>")))
> > (org-toggle-time-stamp-overlays)
> >
> > After realigning the table you get
> >
> > | Name  | Date of Birth|
> > |---+--|
> > | John  | <14 Nov 1978> |
> > | Peter | <14 Nov 1970> |
> > |---+--|
>
> Fixed. Thank you.
>
> Regards,
>
> --
> Nicolas Goaziou
>

Re: [O] org-mode gets confused with column widths when 'time-stamp-custom-formats' are applied.

[Nicolas Goaziou]

Hello,

Ruy Exel  writes:

> Consider the table below:
>
> | Name  | Date of Birth|
> |---+--|
> | John  | <1978-11-14 Tue> |
> | Peter | <1970-11-14 Sat> |
> |---+--|
>
> Suppose we want to format time stamps differently, such as with the
> following elisp commands:
>
> (setq org-time-stamp-custom-formats (quote ("<%d %b %y>" . "<%m/%d/%y %a
> %H:%M>")))
> (org-toggle-time-stamp-overlays)
>
> After realigning the table you get
>
> | Name  | Date of Birth|
> |---+--|
> | John  | <14 Nov 1978> |
> | Peter | <14 Nov 1970> |
> |---+--|

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] org-mode in French

[Rasmus]

gmx  writes:

> Hello,
> I've been using Org-mode for several months now, with pleasure.
> However, I would like the .tex files use some packages (babel,
> french...), a particular koma-script class (scrartcl), etc., which
> allow me to release a. pdf file with French typographical standards.
>
> How to do this?

For language support, you could do something like

(setq org-latex-packages-alist
'(("AUTO" "babel" nil ("pdflatex"))
  ("AUTO" "polyglossia" nil ("xelatex" "lualatex"

And use the "#+language: fr" keyword to set the document to French.

Rasmus

-- 
Hooray!

Re: [O] org-mode in French

[Thomas S. Dye]

Aloha Frederic,

gmx writes:

> Hello,
> I've been using Org-mode for several months now, with pleasure.
> However, I would like the .tex files use some packages (babel,
> french...), a particular koma-script class (scrartcl), etc., which allow
> me to release a. pdf file with French typographical standards.
>
> How to do this?
>
> Thank you for your help,
> Frederic

Below are two examples that should help you on your way.  See the
documentation for org-latex-classes for an explanation of
[NO-DEFAULT-PACKAGES], etc., which you might or might not want to use.

You can put the (add-to-list ...) functions in your .emacs so they are
always available, or you can call one of the source code blocks from a
buffer you want to export.  I find it convenient to do this:

#Local Variables
# eval: (org-sbe "koma-article-palatino")

You'll also need to specify the LaTeX class in the buffer you want to export:
#+LATEX_CLASS: koma-article-palatino

hth,
Tom

#+name: koma-article-times
#+header: :results silent
#+begin_src emacs-lisp
  (require 'ox-latex)
  (add-to-list 'org-latex-classes
   '("koma-article-times"
 "\\documentclass{scrartcl}
   [NO-DEFAULT-PACKAGES]
   [PACKAGES]
   [EXTRA]
  \\usepackage{microtype}
  \\usepackage{tgtermes}
  \\usepackage[scale=.9]{tgheros}
  \\usepackage{tgcursor}
  \\usepackage{paralist}
  \\usepackage[T1]{fontenc}
  \\usepackage{graphicx}
  \\usepackage{textcomp}
  \\usepackage{hyperref}
  \\newcommand{\\rc}{$^{14}$C}"
 ("\\section{%s}" . "\\section*{%s}")
 ("\\subsection{%s}" . "\\subsection*{%s}")
 ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
 ("\\paragraph{%s}" . "\\paragraph*{%s}")
 ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
#+end_src

#+name: koma-article-palatino
#+header: :results silent
#+begin_src emacs-lisp
   (require 'ox-latex)
   (add-to-list 'org-latex-classes
'("koma-article-palatino"
  "\\documentclass{scrartcl}
   [NO-DEFAULT-PACKAGES]
   [PACKAGES]
   [EXTRA]
   \\usepackage{microtype}
   \\usepackage{tgpagella}
   \\linespread{1.05}
   \\usepackage[semibold]{sourcesanspro}
   \\usepackage{tgcursor}
   \\usepackage{paralist}
   \\usepackage[T1]{fontenc}
   \\usepackage{graphicx}
   \\usepackage{textcomp}
   \\usepackage{hyperref}
   \\newcommand{\\rc}{$^{14}$C}"
  ("\\section{%s}" . "\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}")
  ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
  ("\\paragraph{%s}" . "\\paragraph*{%s}")
  ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
#+end_src


--
Thomas S. Dye
http://www.tsdye.com

Re: [O] Org-mode link returned path is truncated when contains space

[numbch...@gmail.com]

sorry for delay reply. I'm cleaning up my Org tasks, found this task. this
issue seems fixed.

[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter:  @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36  CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/

On Tue, Jun 6, 2017 at 6:49 PM, Nicolas Goaziou 
wrote:

> Hello,
>
> "numbch...@gmail.com"  writes:
>
> > I checked Org-mode package version with `org-version`, get `9.0.7`, still
> > have this issue. I updated to latest org-mode ELPA version.
>
> Odd. You may have better luck with Org 9.0.8 then. In particular, commit
> 2d29269bb1b9af08011e091913798b6598e4b156 should prevent path from being
> truncated.
>
> Please report back if it works better (or not).
>
> Regards,
>
> --
> Nicolas Goaziou
>

Re: [O] Org mode notes collapse parser brittle

[Kaushal Modi]

On Fri, Nov 10, 2017 at 3:44 PM Cody Goodman 
wrote:

> Does anyone else use notes extensively with src blocks and results
> drawers? It seems that the regex to parse src blocks and collapse them
> breaks on drawer :END: markers and possibly other things.
>
> Here's an image of the error: https://i.imgur.com/dqDsO5g.png
>

I don't use LOGBOOK, but I was able to confirm this problem based on your
example.

But then I looked in the manual, and in (org) Drawers node, it's mentioned:

> Sometimes you want to keep information associated with an entry, but you
> normally don’t want to see it.  For this, Org mode has _drawers_.  They
> can contain anything but a headline and another drawer.

*They can contain anything but a headline and another drawer.*

So I guess you have hit a limitation.

-- 

Kaushal Modi

Re: [O] Org-mode icon license

[Grant Rettke]

On Sun, Jul 16, 2017 at 6:49 PM, Konstantin Kliakhandler
 wrote:
> I would like to inquire regarding the copyright/license status of the 
> org-mode icon, and specifically as to whether it is
> permissible to use it in (org-mode related) OSS projects, such as browser 
> capture extensions.

Great question. There are 165 org-mode packages on MELPA. Org2Blog is
one of them https://github.com/org2blog/org2blog and I want a logo for
that, too. So maybe there are 163 other groups also looking for an
icon, or already have one. I'm not a graphic designer so I would be
hiring out the work. I need to tell them something like "It can't look
anything like this (Org-Mode's icon), or it can use the colors and
image, or it can include the image or...".

Hopefully there is a precedent for something like this to which we can
conform? Or maybe we don't need to worry about it at all? Or maybe we
figure it out in this thread?

Re: [O] Org-mode ELPA repository package is not very updated?

[numbch...@gmail.com]

After some tries, I use org-mode source code `master` branch now. use
extension `use-package` to load it. It works very fine.
Thanks.

[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter:  @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36  CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/

On Mon, Jul 3, 2017 at 1:31 PM, Bastien  wrote:

> Hi,
>
> "numbch...@gmail.com"  writes:
>
> > I found Org-mode ELPA released source code is old and does not
> > include some patches and updates.
>
> This should be fixed now -- please confirm in a few days.
>
> --
>  Bastien
>

Re: [O] org mode moves to GNU emacs core

[Phillip Lord]

Tim Cross  writes:

>> I don't see how that would possible once it is integrated in GNU emacs
>> core, there will be no separate makefile or anything of that sort, but
>> maybe I am missing something.
>>
>
> There is going to have to be a way for people to maintain and build org
> independently. When you are maintaining Emacs, you don't want to have to
> re-build the whole system every time you create a change. What you tend
> to find is there are multiple Makefiles with a top level Emacs makefile
> which calls sub-level makefiles as part of the build. It may be
> necessary to modify configure or add a new option to build outside the
> emacs tree, but that shouldn't be too difficult.

Emacs builds all its lisp with a single Makefile, but the build is
incremental. So the rebuild is very quick. To be honest, even if you
modify the C layer, the dump is pretty fast.


> I should emphasise that while I agree org would be good as part of
> Emacs' core, I don't think this should occur until org change velocity
> has stabilised to a point where change velocity is lower than it is
> now. At that point, there will be much less need to be running the most
> recent snapshot.
>
> Maybe my experience is very different. However, I found a lot more
> motivation to go from org 7.x to 8.x than I did from 8.x to 9.x. In
> fact, the only visible changes in 9.x I've had to deal with have been
> about compatibility changes and minor bugs I've had to update
> for/fix. I could still be running 8.x. The only reason I've updated to
> 9.x is to avoid issues with some of the contrib packages that have/may
> have been updated to work with 9.x


This makes the assumption that all of org moves at the same speed. It
seems to me that the things currently in contrib still move fairly fast.

Phil

Re: [O] org mode moves to GNU emacs core

[Phillip Lord]

Tim Cross  writes:

> Just to throw my 2 cents in.
>
> While I can understand the benefits of being able to easily install the
> latest org package via elpa, I think there are some significant benefits
> to org being a part of core Emacs.
>
> I currently find three issues with the current situation which may be
> somewhat resolved if org was part of core emacs.
>
> 1. Problems with mixed versions. Currently, Emacs has org 8.x included
> in the distribution. This is despite 9.x being out before the release of
> 25.2. Something needs to be done to improve coordination and perhaps if
> it was part of the core, this would be more likely. At any rate, the
> current situation means you need to be very careful to ensure no org
> feature is loaded before the ELPA package is loaded or you will get odd
> behaviour and the symbol's value is void errors. 


I've argued on emacs-devel about this. The problem here is that the
distributed org-mode remains in the load path, so you are totally
dependent on load path shadowing to ensure the right package gets
loaded. This doesn't happen with ELPA packages since only the latest
gets added to the load path.

My solution to this would be to have Emacs use package.el to load
files in core as well as elsewhere. Then, when you installed org from
ELPA, package.el would remove the core installed files from the
load-path (or rather never add them). You'd need to restart Emacs after
installation, but otherwise the problem goes away.

Everybody else thought this was a bad idea!

Phil

Re: [O] org mode moves to GNU emacs core

[Phillip Lord]

Bastien Guerry  writes:

> Hi Philip,
>
> phillip.l...@russet.org.uk (Phillip Lord) writes:
>
>> I presume you do see this as an advantage? The issue is, surely,
>> that it's too much of a PITA for the advantage that you gain?
>
> Well, it's not really about PITA-or-not-PITA, it's just that I want
> org-mode to be the default mode for some files in Emacs, and having
> org-mode in Emacs' core is the most simple way to go for this.
>
> Maintainers of projects like Gnus or CEDET don't want their code to
> live outside of Emacs repo neither, so I guess simplicity is a big
> win.


Yes, it would appear that way. But, at the moment, to be distributed
with Emacs you have to be in the emacs repo. We've discussed this
before, I know, but these two things are not an absolute
necessity. Having the Emacs build populate it's source tree with
packages is also possible.

Phil

Re: [O] org mode moves to GNU emacs core

[Bastien Guerry]

Hi Robert,

first of all, my bad: what I should have said in all these discussion
is that any decision regarding moving Org to Emacs' core won't happen
any time soon (I'd say two or three years).

Keeping Emacs master branch in sync with Org maint branch is not a
problem anymore, so the decision of whether Org should go into Emacs
core will not depend on this.

And by the time the decision will be made, I expect Emacs and Org
release cycles will come close.  In other words: when Org will be as
stable as Emacs and when most of Org's development will happen in its
external modules, it will be time to move Org's development to Emacs.

But all this is very hypothetical, right now very much "bikeshed" :)

Best,

-- 
 Bastien

Re: [O] org mode moves to GNU emacs core

[Tim Cross]

Uwe Brauer writes:

 "qTim" == qTim Cross  writes:
>
>> Just to throw my 2 cents in.
>
>> 1. Problems with mixed versions. Currently, Emacs has org 8.x included
>> in the distribution. This is despite 9.x being out before the release of
>> 25.2. Something needs to be done to improve coordination and perhaps if
>> it was part of the core, this would be more likely. At any rate, the
>> current situation means you need to be very careful to ensure no org
>> feature is loaded before the ELPA package is loaded or you will get odd
>> behaviour and the symbol's value is void errors.
>
>> 2. If you just want to load the ELPA version of org (not
>> org-plus-contrib) it can be a real pain. You have to play around with
>> package lists to ensure you actually get the right one. This can be a
>> real hassle if you also use the use-package package as you will often
>> get the older version bundled with Emacs if you don't have your package
>> lists in the right order.
>
>> 3. I would really like to see two completely separate packages rather
>> than having org and org-plus-contrib. Currently, if you have packages
>> which have org as a dependency and you have loaded org-plus-contrib
>> rather than just org, you will end up with both. Not a big issue, unless
>> your on a slow link as now you will download updates for both org and
>> org-plus-contrib. (there is no 'cleverness' with ELPA dependency
>> specifications - you cannot specify alternative dependencies).
>
> But this critics could be applied to any emacs package and therefore to
> the package system itself.
>
Yes. It is a weakness of the package system not org. However, while I
have quite a few packages installed, org is the only one where I have
two versions installed at once.

>> A lot will depend on when org becomes part f core. The trick will be to
>> do it once development of org slows down. I've been using org for a long
>> time now and have noticed that the rate of new features being added has
>> slowed down. Much of the changes now is about improvement and refinement
>> of the code base. I would imagine that at some point, things will become
>> even more stable with fewer releases. This would be the point at which
>> it would make sense to bring into core.
>
>> The other advantage of being part of core is that updates and changes to
>> Emacs will be integrated into org much better. We won't see situations
>> where new versions of Emacs require a rush to update org. for the end
>> user, this should create a much more stable org environment.
>
> Well I update GNU emacs every 6 months it is not difficult but needs
> considerable longer to compile and install than org mode.
>

I use to do that - actually, probably even more frequently. I still run
from my own build rather than distribution versions because they are
even further behind (generally). However, these days, I just run the
most recent Emacs release i.e. now 25.2

>> Then of course, there will always be the option to run org straight from
>> the git repository for those who really want the latest version. I find
>> that once you have the path added to load-path, running from the git
>> repo is not much more effort than installing the latest ELPA package.
>
> I don't see how that would possible once it is integrated in GNU emacs
> core, there will be no separate makefile or anything of that sort, but
> maybe I am missing something.
>

There is going to have to be a way for people to maintain and build org
independently. When you are maintaining Emacs, you don't want to have to
re-build the whole system every time you create a change. What you tend
to find is there are multiple Makefiles with a top level Emacs makefile
which calls sub-level makefiles as part of the build. It may be
necessary to modify configure or add a new option to build outside the
emacs tree, but that shouldn't be too difficult.

I should emphasise that while I agree org would be good as part of
Emacs' core, I don't think this should occur until org change velocity
has stabilised to a point where change velocity is lower than it is
now. At that point, there will be much less need to be running the most
recent snapshot.

Maybe my experience is very different. However, I found a lot more
motivation to go from org 7.x to 8.x than I did from 8.x to 9.x. In
fact, the only visible changes in 9.x I've had to deal with have been
about compatibility changes and minor bugs I've had to update
for/fix. I could still be running 8.x. The only reason I've updated to
9.x is to avoid issues with some of the contrib packages that have/may
have been updated to work with 9.x

The other point to keep in mind is that this change won't happen
quickly. It will take some time before this can occur and we probably
need to start thinking/talking about it now so that when the right time

Re: [O] org mode moves to GNU emacs core

[Adonay Felipe Nogueira]

Indeed I admit that I might have exagerated when I called it
"average". Please excuse my wrong doing. :)

Re: [O] org mode moves to GNU emacs core

[Nick Dokos]

Adonay Felipe Nogueira  writes:

> I have just thought of some more advantages and disadvantages too.
>
> * Strengths
>
> ** One less split in development effort
>
> This one explains itself. Also, for a related article against "forking",
> "bundling", and "reinventing the wheel" practices, see
> [[https://wingolog.org/archives/2015/11/09/embracing-conways-law]].
>
> * Threats
>
> ** People who still refuse to contribute to GNU Emacs for some reason
>
> I have seem people making completely separated projects from GNU Emacs
> due to concerns of being required to assign copyright to the
> FSF. However, first and foremost, I must add that I'm in favor of doing
> such assignment, because FSF is a charity organization --- not just a
> non-profit ---, and they, together with other organizations, do
> community-oriented copyleft enforcement, not the
> "average"/"extortion-based" copyleft enforcement.
>

Whoa: some of what you describe exists (see e.g.
https://sfconservancy.org/blog/2016/jul/19/patrick-mchardy-gpl-enforcement/),
but it is a distant outlier. Calling it "average" is as inaccurate as
calling Pele an "average" footballer.

-- 
Nick