[O] some publish html options gone

[Manuel Koell]

When I try to use `M-x customize` and search for `org-html-doctype` or
`org-html5-fancy` I don't get any match. I still have them in my custom.el
file, generated from an older emacs version (24.3). Were they removed?

Emacs: 25.1.50.2
Org: 8.3.2

[O] Bug: IRC links translate wrong

[Manuel Koell]

>From org docs: http://orgmode.org/manual/External-links.html

If you want to link some irc channel with irc:/ or
[[irc://freenode/#emacs][emacs]] the link won't translate to irc:// as
expected, instead a file:/// link will be created.

Re: [O] prevent auto appending #+INCLUDE files title

[Manuel Koell]

Oh, you're right!

Your example opened my eyes thanks!

Thanks a lot, Rasmus!

2015-11-23 18:33 GMT+01:00 Rasmus <ras...@gmx.us>:

> Manuel Koell <man.ko...@gmail.com> writes:
>
> > I think you got me wrong or I don't understand correctly ^^
>
> I don’t think so.
>
> > The problem is, when I export a file which uses #+INCLUDE inside, for
> > example my index.org where I want to include the latest 5 posts
> (generated
> > from sitemap.org). The exported index.html has the wrong title/h1 then:
> > My title Sitemap. The files I used to include append their
> > title to the index.org document then. This is not something I would
> expect
> > if I already set the #+TITLE option. Idk if this is a bug or a feature.
>
> This is a feature.  Basically, it follows from the fact that you can write
> something like this:
>
> #+title: the first part of long title
> #+title: and the second part
>
> #+include works by inserting the included document at the right place.
> So the buffer ox parses looks something like this.
>
> #+Title: main title
> # ...
> #+Title: sitemap
> # ...
>
> > Do you've any workaround? I dont know why orgmode is mess up my title.
>
> Use :lines "2-", since your unwanted #+title is probably at line 1.
>
> Rasmus
>
> --
> Er du tosset for noge' lårt!
>

[O] add publish option :with-setupfile

[Manuel Koell]

I would like to see such option so someone can create a setupfile with
macros/options per project or target (component). The setupfiles can be
located in the project directory then. I dont know how to set macros in
publishing components. Otherwise, you'd have to insert the #+SETUPFILE
option in each file manually.

[O] prevent auto appending #+INCLUDE files title

[Manuel Koell]

I tried to use #+INCLUDE "sitemap.org" :only-contents t with the
:auto-sitemap option on my publishing project, but whenever I include a
file this way the title appends to the exported document title.

example file (test.org)

```
#+TITLE: My title

#+INCLUDE "sitemap.org" :only-contents t
```

Now the exported document title test.html contains the title: My title
Sitemap
Expected behaviour: the title I set with #+TITLE

Why is orgmode doingt such "smart" things for me?

Re: [O] prevent auto appending #+INCLUDE files title

[Manuel Koell]

Hello Rasmus,

I think you got me wrong or I don't understand correctly ^^

The problem is, when I export a file which uses #+INCLUDE inside, for
example my index.org where I want to include the latest 5 posts (generated
from sitemap.org). The exported index.html has the wrong title/h1 then:
My title Sitemap. The files I used to include append their
title to the index.org document then. This is not something I would expect
if I already set the #+TITLE option. Idk if this is a bug or a feature. Do
you've any workaround? I dont know why orgmode is mess up my title.

2015-11-23 18:13 GMT+01:00 Rasmus <ras...@gmx.us>:

> Hi Manuel,
>
> Manuel Koell <man.ko...@gmail.com> writes:
>
> > I tried to use #+INCLUDE "sitemap.org" :only-contents t with the
> > :auto-sitemap option on my publishing project, but whenever I include a
> > file this way the title appends to the exported document title.
> >
> > example file (test.org)
> >
> > ```
> >
> > #+TITLE: My title
> >
> > #+INCLUDE "sitemap.org" :only-contents t
> > ```
> >
> > Now the exported document title test.html contains the title: My title
> > Sitemap
> > Expected behaviour: the title I set with #+TITLE
>
> Currently :only-contents is just referring to a headline or so.  E.g.
>
>   #+include: "test.org::#head1" :only-contents t
>
> will limit the input to the sense of contents as understood by
> org-element.
>
> I agree that it might extend the meaning of :only-contents to also work on
> full files, though it’s not clear what the proper behavior is.  In
> particular, what keywords would it extend to?  E.g. what about
> #+backend_header lines, e.g. #+html_header?  To me, this sounds like a
> difficult problem to get right...
>
> An easy fix in your problem in this case is probably :lines "2-".
>
> Rasmus
>
> --
> I feel emotional landscapes they puzzle me
>
>
>

[O] exported html: src block missing pseudo-elements

[Manuel Koell]

I exported some html with defaut style and a javascript src block:

```
#+BEGIN_SRC javascript
var x = {}
#+END_SRC
```

The exported html contains the default styles and pseudo-elements for
following languages only:

```

  pre.src:hover:before { display: inline;}  pre.src-sh:before{
content: 'sh'; }  pre.src-bash:before  { content: 'sh'; }
pre.src-emacs-lisp:before { content: 'Emacs Lisp'; }  pre.src-R:before
{ content: 'R'; }  pre.src-perl:before  { content: 'Perl'; }
pre.src-java:before  { content: 'Java'; }  pre.src-sql:before   {
content: 'SQL'; }

```

Why is javascript not included? I know I could write the
`pre.src-javascript:before { content: 'Javascript'; } myself.
Syntax-highlighting looks fine but the upper right label on hover is
missing.

Thanks!

Re: [O] html export: what do codehighlighton/off functions do?

[Manuel Koell]

Sorry, I didn't know such feature exists in org mode! It's just kinda
weird, these function still get called from onmouseover/onmouseout bindings.

2015-11-12 18:02 GMT+01:00 Rasmus <ras...@gmx.us>:

> Manuel Koell <man.ko...@gmail.com> writes:
>
> > Can someone please tell me what these functions do?
> >
> > ```
> >
> > function CodeHighlightOn(elem, id) {   var target =
> > document.getElementById(id);   if(null != target) {
> > elem.cacheClassElem = elem.className; elem.cacheClassTarget =
> > target.className; target.className = "code-highlighted";
> > elem.className   = "code-highlighted";   } } function
> > CodeHighlightOff(elem, id) {   var target =
> > document.getElementById(id);   if(elem.cacheClassElem)
> > elem.className = elem.cacheClassElem;   if(elem.cacheClassTarget)
> > target.className = elem.cacheClassTarget; }
> >
> >
> > ```
> >
> > The only thing I could think of is to toggle some classes, but I can't
> seem
> > to find some real world example out there. This javascript code is
> included
> > on every export, doesn't matter if you've src/example blocks in your org
> > file or not.
>
> It is used for "coderefs" links.  Example from unit tests:
>
> #+BEGIN_SRC emacs-lisp
> (+ 1 1)  (ref:sc)
> #+END_SRC
> [[(sc)]]
>
> It will highlight the appropriate line in the html export.
>
> Are you asking us to remove the javascript conditionally on whether we
> think it will be used?  This sounds hard.
>
> You can remove the JS via the buffer option html-scripts or via
> org-html-head-include-scripts.
>
> Hope it helps,
> Rasmus
>
> --
> I hear there's rumors on the, uh, Internets. . .
>
>
>

[O] org-html-postamble: %d empty date

[Manuel Koell]

I set up a publishing project including a custom postamble :html-postamble
"Date: %d, Last modification: %C". When I export this file The %d date is
empty. From `C-h v org-html-postamble-format` I got the info about the
available elements to use:

```
  %t stands for the title.
  %s stands for the subtitle.
  %a stands for the author's name.
  %e stands for the author's email.
  %d stands for the date.
  %c will be replaced by `org-html-creator-string'.
  %v will be replaced by `org-html-validation-link'.
  %T will be replaced by the export time.
  %C will be replaced by the last modification time.
```

I tried to set both, :html-postamble and :html-postamble-format. Which date
is meant with the %d variable? Do I've to set it manually? I thought %d
will output the creation date of the file itself and %C the last updated
time (btw I get german weekdays and idk why & how to change).

[O] html export: what do codehighlighton/off functions do?

[Manuel Koell]

Can someone please tell me what these functions do?

```

function CodeHighlightOn(elem, id) {   var target =
document.getElementById(id);   if(null != target) {
elem.cacheClassElem = elem.className; elem.cacheClassTarget =
target.className; target.className = "code-highlighted";
elem.className   = "code-highlighted";   } } function
CodeHighlightOff(elem, id) {   var target =
document.getElementById(id);   if(elem.cacheClassElem)
elem.className = elem.cacheClassElem;   if(elem.cacheClassTarget)
target.className = elem.cacheClassTarget; }


```

The only thing I could think of is to toggle some classes, but I can't seem
to find some real world example out there. This javascript code is included
on every export, doesn't matter if you've src/example blocks in your org
file or not.

Thanks

Re: [O] Bug: bold text followed by footnote not bold

[Manuel Koell]

Upgraded to latest org 8.3.2 from "org" package archive (used 8.2.10
before) and now it works after I did M-x org-reload and
uninstall/reinstalled latest org. Thanks!

2015-11-11 10:35 GMT+01:00 Nicolas Goaziou <m...@nicolasgoaziou.fr>:

> Hello,
>
> Manuel Koell <man.ko...@gmail.com> writes:
>
> > I just encountered following behaviour:
> >
> > *foo bar*[fn:1] will export as *foo bar*1 (not bold, with stars)
> >
> > *foo bar* [fn:2] will export as foo bar 1 (bold, but you've to use a
> space
> > between bold text and marker)
> >
> > I may be wrong, but I thought a footnote marker will follow immediately
> > after the word ends. Both examples exported to html.
>
> I cannot reproduce it in latest Org.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>

[O] Bug: bold text followed by footnote not bold

[Manuel Koell]

I just encountered following behaviour:

*foo bar*[fn:1] will export as *foo bar*1 (not bold, with stars)

*foo bar* [fn:2] will export as foo bar 1 (bold, but you've to use a space
between bold text and marker)

I may be wrong, but I thought a footnote marker will follow immediately
after the word ends. Both examples exported to html.

Re: [O] convert a simple list of lines each to a orgmode header

[Manuel Koell]

I know how to do in vim. Select all text and hit I (uppercase i), then
start type.
There is also a way in emacs, but I never tried before:

https://www.gnu.org/software/emacs/manual/html%5Fnode/emacs/Rectangles.html

2015-09-29 5:30 GMT+02:00 Nick Dokos :

> Xebar Saram  writes:
>
> > Hi all
> >
> > im looking for a simple way to convert a simple list of lines (i can
> > mark it first if needed) each to a orgmode header anyone has such a
> > way?
> >
>
> Maybe I'm missing something, but can't you just add asterisks in front
> of each line? Maybe with a keyboard macro? Or even a sed script?
>
> There's a reason that org files are plain text.
>
> Nick
>
>
>

Re: [O] A book produced using Org

[Manuel Koell]

Beautiful! I would love to see the org file! How did emacs perform which
such huge file?

2015-09-20 3:06 GMT+02:00 Vikas Rawal :

>
> > On 20-Sep-2015, at 4:20 am, Pascal Fleury  wrote:
> >
> > Great! Congrats!
> >
> > I was actually wondering: you are 3 authors. How did you collaborate, in
> practice ? There was a thread about using org for collaborative work, but
> it seemed to end in discussing other tools...
> > Was it plain git/emacs and the tools used usually for code management ?
>
>
> Well, unfortunately, the other two authors are not familiar with emacs,
> org-mode, or LaTeX.
>
> The parts they wrote were sent as MS-Word files. I converted them into
> Org-mode.
>
> For the parts I wrote, I sent them PDFs. The first time, I also sent them
> a Word version. I offered them that they could comment in word (with track
> changes) and send me, or better still, work on hard copies and send me the
> scans. The PDFs were so far superior to those word files, that could not
> resist them :). So, their comments came as scans of the commented hard
> copies, and I incorporated them in. Once they were comfortable with this,
> in subsequent rounds, I had to send them only PDFs.
>
> We followed the same process with the copy editors. The copy editors
> worked on hard copies, and I incorporated the comments. This actually had a
> huge advantage since, in the process of incorporating their edits, I went
> through every single change they wanted to make. I do not know if they had
> done this on their software, how I would have gone through every sentence
> to check if and what had been modified.
>
> The publisher usually works with InDesign, but was willing to let me deal
> with production of the print-ready PDF if I could meet her specifications.
> Again, this meant additional work for me. But this was also far more
> efficient than converting everything into Word, and then letting her set it
> up on InDesign. Both these steps would have been far more laborious. For
> example, I doubt if InDesign can make an author index automatically from
> citations in the way biblatex does.
>
> So, the barrier in our case was not to find the most appropriate
> version-control software. The problem was that the other two authors were
> completely unfamiliar with any of these tools. But, even with that, using
> Org-mode was so far superior to shifting to Word or anything of that kind.
> No question.
>
>  Vikas
>
>
>
>

[O] capture append entries, not prepend

[Manuel Koell]

I've a capture template like this:

 '(org-capture-templates
   (quote
((j Journal plain
  (file+datetree ~/org/journal.org)
   %? :unnarrowed t)...

Current behaviour:

* 2015
** 2015-07 July
*** 2015-07-24 Friday
 3rd entry bla bla bla
 2nd entry foo bar
 1st entry test

Expected behaviour:

* 2015
** 2015-07 July
*** 2015-07-24 Friday
 1st entry test
 2nd entry foo bar
 3rd entry bla bla bla

I didn't set the 'prepend' key and also tried to set
'org-reverse-notes-order' to always.

Re: [O] capture append entries, not prepend

[Manuel Koell]

Thank you, Nick. I didn't know this is a feature. It is usual for me to go
from top to bottom. So the only way to accomplish this order would be to
use file+headline or file+olp?


2015-07-25 17:00 GMT+02:00 Nick Dokos ndo...@gmail.com:

 Manuel Koell man.ko...@gmail.com writes:

  I've a capture template like this:
 
   '(org-capture-templates
 (quote
  ((j Journal plain
(file+datetree ~/org/journal.org)
 %? :unnarrowed t)...
 
  Current behaviour:
 
  * 2015
  ** 2015-07 July
  *** 2015-07-24 Friday
   3rd entry bla bla bla
   2nd entry foo bar
   1st entry test
 
  Expected behaviour:
 
  * 2015
  ** 2015-07 July
  *** 2015-07-24 Friday
   1st entry test
   2nd entry foo bar
   3rd entry bla bla bla
 
  I didn't set the 'prepend' key and also tried to set
 'org-reverse-notes-order' to always.
 

 I don't think you can do what you want: datetrees are always in the
 first form. They don't obey :prepend or reverse notes order.

 Not that it cannot be done, but the design has to be changed: it's not
 a bug, it's a feature.

 --
 Nick

Re: [O] Schedule more roughly

[Manuel Koell]

I tried the random scatter. This is a really good method for
procrastination! I ended up with the method you said. I schedule those
things now on the beginning of the week or month (or year?) and maybe add a
special tag or todo keyword.

The habits method looks nice! I dont know if I can tweak the visibility of
those tasks in my agenda? I dont want to display those tasks on my agenda
so I would need to filter them out using its own keyword?

2015-07-16 21:18 GMT+02:00 Subhan Michael Tindall subhan.mich...@gmail.com
:


 On Wed, Jul 15, 2015 at 1:19 PM Manuel Koell man.ko...@gmail.com wrote:

 How can I schedule my todo's more roughly? Say, I know I want to do it
 next week or in a few months but I don't know the exact date nor time to do
 it. I just want a way to plan more foresighted. If the week starts or the
 month I could always set a more accurate timestamp then. Any idea? I tried
 to remove the day number in a timestamp but this would destroy the
 timestamp.


 Take a look at habits.  It has something similar IE you can set a due date
 for a habit to be completed for say at least 3 days, but not more than 5
 days.
 Not exactly what you are looking for but might be adaptable.

 http://orgmode.org/manual/Tracking-your-habits.html

Re: [O] Org assumes scheduled/deadline time from headline

[Manuel Koell]

I provided an example here https://github.com/bastibe/org-journal/issues/48

Re: [O] Org assumes scheduled/deadline time from headline

[Manuel Koell]

Thank you, problem solved!

2015-07-17 14:32 GMT+02:00 Rasmus ras...@gmx.us:

 Manuel Koell man.ko...@gmail.com writes:

  I provided an example here
 https://github.com/bastibe/org-journal/issues/48

 I see.

   (setq org-agenda-search-headline-for-time nil)

 Rasmus

 --
 With monopolies the cake is a lie!

[O] Org assumes scheduled/deadline time from headline

[Manuel Koell]

I'm using the org-journal extension from Bastian Berchtold to write my
daily stuff down. Some of my journal entries (headlines) start with a time
like 12:17 or 20:33. When I make a TODO out of it and set a
schedule/deadline date, orgmode assumes the time for the schedule/deadline
date from the headline. How can I prevent this (wrong) behaviour? I guess
it is a feature rather than a bug...

[O] Timestamp range view in agenda

[Manuel Koell]

I have a date/timestamp range:

2015-07-13 Mon 09:00-12:00--2015-07-17 Fri 09:00-12:00 and
2015-07-20 Mon 09:00-12:00--2015-07-24 Fri 09:00-12:00

When I view it in the agenda:

Monday, 13 July 2015
09:00-12:00 (1/5): Some appt

...

Friday, 17 July 2015
09:00-12:00 (5/5): Some appt

But all the days between the beginning and the end of this range look like:

(n/5): Some appt

without the time in front of.

Is there a way to force org-mode to show the time on all days?
Or at least an option to customize e.g: `org-range-force-time` t

Thank ya!

Manu

[O] Schedule more roughly

[Manuel Koell]

How can I schedule my todo's more roughly? Say, I know I want to do it next
week or in a few months but I don't know the exact date nor time to do it.
I just want a way to plan more foresighted. If the week starts or the month
I could always set a more accurate timestamp then. Any idea? I tried to
remove the day number in a timestamp but this would destroy the timestamp.