Re: [O] org-annotate/collaboration?

[Alan E. Davis]

I am looking for something a little different than this: annotated ls
listings.  I have been searching blindly for years for this.

Back in the 90s was a Dos clone called 4dos, which featured directory
listings with annotations, such that typing whatever the command was
(dir?), gave a listing with the file name just like "dir" but also a
description of the file.

It was exceedingly useful for me, in keeping track of a large number of
files.  I have never seen anything like it.

Could org-annotate fulfill at least part of this requirement?  (I have
posted to this list a similar question quite some years ago.)

Alan Davis

On Wed, Feb 8, 2017 at 9:21 PM, Eric Abrahamsen 
wrote:

> Matt Price  writes:
>
> > Does anyone use org-annotate actively? I'm wondering what your
> > workflow is, how you incorporate comments, etc.
>
> I wrote it, and I don't use it that much. I do use it for quick
> notes-to-self when writing, but footnotes do the job just as well.
>
> > I'm hoping to embark on a book project with a colleague. I would like
> > to use org-mode if I can, but I need to get a sense of the
> > collaboration workflow. When you work on projects together, do you use
> > annotations? Or git pull requests? If the latter, od you use any
> > filters, or any magit tricks, to approve or modify suggested changes
> > chunk by chunk?
>
> It's a huge problem, and one that org-annotate isn't going to solve. I
> do a lot of manuscript editing, and passing files around, and have only
> barely gotten some people to accept my "weird" workflow, which is to
> send them a clean version of an edited file, and along with that an HTML
> file containing htmlized word-diff output, where the insertions and
> deletions are colorized. They make further edits on the clean copy, and
> I do another go-around. It's a huge pain.
>
> > My colleague is familiar with markdown but for major projects has only
> > ever used word. I'm trying to figure out how best to help her move to
> > a text--based mode of production; the markdown ecosystem seems a lot
> > larger, and I don't want the transition to be too painful. But OTOH I
> > really want to stay in org if I can!
>
> I wish there were better solutions out there!
>
> Eric
>
>
>


-- 
[I do not] carry such information in my mind since it is readily
available in books. …The value of a college education is not the
learning of many facts but the training of the mind to think.
  ---Albert Einstein



"Sweet instruments hung up in cases. . . keep their sounds to themselves."

 ---Shakespeare, _Timon of Athens_

Re: [O] org-annotate/collaboration?

[Eric Abrahamsen]

Matt Price  writes:

> Does anyone use org-annotate actively? I'm wondering what your
> workflow is, how you incorporate comments, etc.  

I wrote it, and I don't use it that much. I do use it for quick
notes-to-self when writing, but footnotes do the job just as well.

> I'm hoping to embark on a book project with a colleague. I would like
> to use org-mode if I can, but I need to get a sense of the
> collaboration workflow. When you work on projects together, do you use
> annotations? Or git pull requests? If the latter, od you use any
> filters, or any magit tricks, to approve or modify suggested changes
> chunk by chunk?  

It's a huge problem, and one that org-annotate isn't going to solve. I
do a lot of manuscript editing, and passing files around, and have only
barely gotten some people to accept my "weird" workflow, which is to
send them a clean version of an edited file, and along with that an HTML
file containing htmlized word-diff output, where the insertions and
deletions are colorized. They make further edits on the clean copy, and
I do another go-around. It's a huge pain.

> My colleague is familiar with markdown but for major projects has only
> ever used word. I'm trying to figure out how best to help her move to
> a text--based mode of production; the markdown ecosystem seems a lot
> larger, and I don't want the transition to be too painful. But OTOH I
> really want to stay in org if I can!

I wish there were better solutions out there!

Eric

[O] %( in capture template

[Samuel Wales]

with the new org maint code, i still occasionally get the literal string.

it occurs when the region spans a blank line.

like

  %(concat
"http://whatever.whatever/building-a-mold-free-house/whatever;
"Building a mold free house" "

these remplates [don't know if first does anything]

  (add-to-list 'org-capture-templates
   `("L" "Protocol L for link" entry
 (file+headline ,org-default-notes-file "xyzzy-remember")
 ;; fixme perhaps i do not need the %i, if it is for no text
 "%(concat \"%:link\"
\"%:description\" \"%i\") L"
 :prepend t :immediate-finish t :jump-to-captured t))
  ;; this seems to get called by org capture whether selection or not
  (add-to-list 'org-capture-templates
   `("p" "Protocol p" entry
 (file+headline ,org-default-notes-file "xyzzy-remember")
 "%(concat \"%:link\"
\"%:description\" \"%i\")"
 :prepend t :immediate-finish t :jump-to-captured t))

-- 
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." --- very true words by Johanna Kaiser spoken to US NIH in
conference call with Walter Koroshetz, NINDS director


Denmark: free Karina Hansen NOW.
  UPDATE 2016-10: home, but not fully free

Re: [O] Adding #+LATEX: \newpage before section header using org-export-before-parsing-hook

[Joon Ro]

> So you'll have to manipulate org-map-continue-from appropriately.

Thanks a lot! Adding (setq org-map-continue-from (outline-next-heading)) after 
insert-string seemed to solve the problem.
(I added "newpage" to org-tags-exclude-from-inheritance, so the newpage does 
not get applied to subheadings)

(defun org/parse-headings-latex-newpage (backend)
  ; add \newpage to headings with :newpage: tag
  (if (member backend '(latex))
  (org-map-entries
   (lambda ()
 (progn
   (insert-string "#+LATEX: \\newpage\n")
   (setq org-map-continue-from (outline-next-heading))
   ))
   "+newpage"))
)

(add-hook 'org-export-before-parsing-hook 'org/parse-headings-latex-newpage)
(add-to-list 'org-tags-exclude-from-inheritance '"newpage")

Best,
Joon

Re: [O] Help checking orgcard.pdf

[Kyle Meyer]

Kyle Meyer  writes:

> Kaushal Modi  writes:
>
>> Thanks. Please push that for me.
>
> OK, will do.  I'll wait a day or two for comments on other sections and
> apply your patch when I commit those changes.

Pushed (4340cc78).

-- 
Kyle

Re: [O] Adding #+LATEX: \newpage before section header using org-export-before-parsing-hook

[Eric Abrahamsen]

Nick Dokos  writes:

> Joon Ro  writes:
>
>> So far I have done:
>>
>> (defun org/parse-headings (backend)
>>   (if (member backend '(latex))
>>   (org-map-entries
>>(lambda ()
>>  (progn
>>(insert-string "#+LATEX: \\newpage")
>>))
>>"+newpage")
>> )
>> )
>>
>> (add-hook 'org-export-before-parsing-hook 'org/parse-headings)
>>
>> This puts #+LATEX: \\newpage before the subheading, but the problem is if I 
>> try to do (insert-string "#+LATEX: \\newpage"), exporting gets stuck with 
>> the message "org-babel-exp process txt
>> at position 280541...". I suspect inserting a string messes up the position. 
>> How would I insert string with the newline character before a heading?
>>
> See the doc for org-map-entries - it says:
>
> ,
> | The call to FUNC will be wrapped into a save-excursion form, so FUNC
> | does not need to preserve point.  After evaluation, the cursor will be
> | moved to the end of the line (presumably of the headline of the
> | processed entry) and search continues from there.  Under some
> | circumstances, this may not produce the wanted results.  For example,
> | if you have removed (e.g. archived) the current (sub)tree it could
> | mean that the next entry will be skipped entirely.  In such cases, you
> | can specify the position from where search should continue by making
> | FUNC set the variable ‘org-map-continue-from’ to the desired buffer
> | position.
> `
>
> So you'll have to manipulate org-map-continue-from appropriately.

I would think it would be easier to add at export time using
`org-export-filter-headline-functions'.

Eric

Re: [O] Adding #+LATEX: \newpage before section header using org-export-before-parsing-hook

[Nick Dokos]

Joon Ro  writes:

> So far I have done:
>
> (defun org/parse-headings (backend)
>   (if (member backend '(latex))
>   (org-map-entries
>(lambda ()
>  (progn
>(insert-string "#+LATEX: \\newpage")
>))
>"+newpage")
> )
> )
>
> (add-hook 'org-export-before-parsing-hook 'org/parse-headings)
>
> This puts #+LATEX: \\newpage before the subheading, but the problem is if I 
> try to do (insert-string "#+LATEX: \\newpage"), exporting gets stuck with the 
> message "org-babel-exp process txt
> at position 280541...". I suspect inserting a string messes up the position. 
> How would I insert string with the newline character before a heading?
>
See the doc for org-map-entries - it says:

,
| The call to FUNC will be wrapped into a save-excursion form, so FUNC
| does not need to preserve point.  After evaluation, the cursor will be
| moved to the end of the line (presumably of the headline of the
| processed entry) and search continues from there.  Under some
| circumstances, this may not produce the wanted results.  For example,
| if you have removed (e.g. archived) the current (sub)tree it could
| mean that the next entry will be skipped entirely.  In such cases, you
| can specify the position from where search should continue by making
| FUNC set the variable ‘org-map-continue-from’ to the desired buffer
| position.
`

So you'll have to manipulate org-map-continue-from appropriately.

-- 
Nick

[O] org-annotate/collaboration?

[Matt Price]

Does anyone use org-annotate actively? I'm wondering what your workflow is,
how you incorporate comments, etc.

I'm hoping to embark on a book project with a colleague. I would like to
use org-mode if I can, but I need to get a sense of the collaboration
workflow. When you work on projects together, do you use annotations? Or
git pull requests? If the latter, od you use any filters, or any magit
tricks, to approve or modify suggested changes chunk by chunk?

My colleague is familiar with markdown but for major projects has only ever
used word. I'm trying to figure out how best to help her move to a
text--based mode of production; the markdown ecosystem seems a lot larger,
and I don't want the transition to be too painful. But OTOH I really want
to stay in org if I can!

Thanks,
Matt

Re: [O] Adding #+LATEX: \newpage before section header using org-export-before-parsing-hook

[Joon Ro]

So far I have done:


(defun org/parse-headings (backend)
  (if (member backend '(latex))
  (org-map-entries
   (lambda ()
 (progn
   (insert-string "#+LATEX: \\newpage")
   ))
   "+newpage")
)
)

(add-hook 'org-export-before-parsing-hook 'org/parse-headings)

This puts #+LATEX: \\newpage before the subheading, but the problem is if I try 
to do (insert-string "#+LATEX: \\newpage"), exporting gets stuck with the 
message "org-babel-exp process txt at position 280541...". I suspect inserting 
a string messes up the position. How would I insert string with the newline 
character before a heading?

Best,
Joon




From: Thomas S. Dye 
Sent: Wednesday, February 8, 2017 2:48:47 PM
To: Joon Ro
Cc: emacs-orgmode@gnu.org
Subject: Re: [O] Adding #+LATEX: \newpage before section header using 
org-export-before-parsing-hook

Aloha Joon,

Joon Ro writes:

> Hi,
>
>
> In latex export, sometimes I want to make sure a section starts in a new page.
>
> It seems I should be able to add a hook to org-export-before-parsing-hook, so 
> if it sees a section with :newpage: tag (for example), it adds #+LATEX: 
> \newpage before the section header so I would get
>
>
> \newpage
>
> \section{Section Name}
>
> in the exported file.
>
> I have a couple of hooks already so in general I'm using the following code:
>
>   (org-map-entries
>(lambda ()
>  (progn
>
>))
>"+newpage")
>
> but I'm not sure how to add #+LATEX: \newpage before the section header - .
>
> Best Regards,
> Joon

I use this:

 Ignore headline and/or start newpage on export

#+name: ignoreheading-and-or-newpage-on-export
#+BEGIN_SRC emacs-lisp :results silent
  (defun tsd-ignore-headline-and-or-newpage (contents backend info)
"Ignore headlines with tag `ignoreheading' and/or start
  headline on LaTeX new page with tag `newpage'."
(cond ((and (org-export-derived-backend-p backend 'latex 'beamer)
(string-match "\\`.*newpage.*\n" (downcase contents))
(string-match "\\`.*ignoreheading.*\n" (downcase contents)))
   (replace-match "newpage" nil nil contents))
  ((and (org-export-derived-backend-p backend 'latex 'html 'ascii 
'beamer)
(string-match "\\`.*ignoreheading.*\n" (downcase contents)))
   (replace-match "" nil nil contents))
  ((and (org-export-derived-backend-p backend 'latex)
  (string-match "\\(\\`.*\\)newpage\\(.*\n\\)" (downcase 
contents)))
   (replace-match "newpage\\1\\2"  nil nil contents
  ;; add function to filter list
  ;; (add-to-list 'org-export-filter-headline-functions
  ;;  'tsd-ignore-headline-and-or-newpage)
#+END_SRC

hth,
Tom


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

Re: [O] Adding #+LATEX: \newpage before section header using org-export-before-parsing-hook

[Thomas S. Dye]

Aloha Joon,

Joon Ro writes:

> Hi,
>
>
> In latex export, sometimes I want to make sure a section starts in a new page.
>
> It seems I should be able to add a hook to org-export-before-parsing-hook, so 
> if it sees a section with :newpage: tag (for example), it adds #+LATEX: 
> \newpage before the section header so I would get
>
>
> \newpage
>
> \section{Section Name}
>
> in the exported file.
>
> I have a couple of hooks already so in general I'm using the following code:
>
>   (org-map-entries
>(lambda ()
>  (progn
>
>))
>"+newpage")
>
> but I'm not sure how to add #+LATEX: \newpage before the section header - .
>
> Best Regards,
> Joon

I use this:

 Ignore headline and/or start newpage on export

#+name: ignoreheading-and-or-newpage-on-export
#+BEGIN_SRC emacs-lisp :results silent
  (defun tsd-ignore-headline-and-or-newpage (contents backend info)
"Ignore headlines with tag `ignoreheading' and/or start
  headline on LaTeX new page with tag `newpage'."
(cond ((and (org-export-derived-backend-p backend 'latex 'beamer)
(string-match "\\`.*newpage.*\n" (downcase contents))
(string-match "\\`.*ignoreheading.*\n" (downcase contents)))
   (replace-match "newpage" nil nil contents))
  ((and (org-export-derived-backend-p backend 'latex 'html 'ascii 
'beamer)
(string-match "\\`.*ignoreheading.*\n" (downcase contents)))
   (replace-match "" nil nil contents))
  ((and (org-export-derived-backend-p backend 'latex)
  (string-match "\\(\\`.*\\)newpage\\(.*\n\\)" (downcase 
contents)))
   (replace-match "newpage\\1\\2"  nil nil contents
  ;; add function to filter list
  ;; (add-to-list 'org-export-filter-headline-functions
  ;;  'tsd-ignore-headline-and-or-newpage)
#+END_SRC

hth,
Tom


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

Re: [O] Adding #+LATEX: \newpage before section header using org-export-before-parsing-hook

[Joon Ro]

Hi,


(I'm sorry for a duplicated email - it was sent my a mistake)


In latex export, sometimes I want to make sure a section starts in a new page.

It seems I should be able to add a hook to org-export-before-parsing-hook, so 
if it sees a section with :newpage: tag (for example), it adds #+LATEX: 
\newpage before the section header so I would get


\newpage

\section{Section Name}

in the exported file.

I have a couple of hooks already so in general I'm using the following code:

  (org-map-entries
   (lambda ()
 (progn

   ))
   "+newpage")

but I'm not sure how to add #+LATEX: \newpage before the section header - any 
help would be greatly appreciated.

Best,
Joon




From: Joon Ro 
Sent: Wednesday, February 8, 2017 1:52:42 PM
To: emacs-orgmode@gnu.org
Subject: Adding #+LATEX: \newpage before section header using 
org-export-before-parsing-hook


Hi,


In latex export, sometimes I want to make sure a section starts in a new page.

It seems I should be able to add a hook to org-export-before-parsing-hook, so 
if it sees a section with :newpage: tag (for example), it adds #+LATEX: 
\newpage before the section header so I would get


\newpage

\section{Section Name}

in the exported file.

I have a couple of hooks already so in general I'm using the following code:

  (org-map-entries
   (lambda ()
 (progn

   ))
   "+newpage")

but I'm not sure how to add #+LATEX: \newpage before the section header - .

Best Regards,
Joon

[O] Adding #+LATEX: \newpage before section header using org-export-before-parsing-hook

[Joon Ro]

Hi,


In latex export, sometimes I want to make sure a section starts in a new page.

It seems I should be able to add a hook to org-export-before-parsing-hook, so 
if it sees a section with :newpage: tag (for example), it adds #+LATEX: 
\newpage before the section header so I would get


\newpage

\section{Section Name}

in the exported file.

I have a couple of hooks already so in general I'm using the following code:

  (org-map-entries
   (lambda ()
 (progn

   ))
   "+newpage")

but I'm not sure how to add #+LATEX: \newpage before the section header - .

Best Regards,
Joon

Re: [O] [Ann] Tool to hack time

[Samuel Wales]

it's great to have such a mechanism.

my preference for such things is to use no-time for ones that are done later.

On 2/8/17, Marco Wahl  wrote:
>> |:LAST_REPEAT: [2017-02-08 Tue 12:01]

nix the 12:01.

-- 
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." --- very true words by Johanna Kaiser spoken to US NIH in
conference call with Walter Koroshetz, NINDS director

Re: [O] org manual not updating when pulling from git

[Achim Gratz]

Marco Wahl writes:
> Ah!  I didn't see target 'compile-dirty'.  Thank you for the hint.
>
> So for now I'm happy with the build process with the existence of
>
> make compile-dirty
>
> and further
>
> make test-dirty
>
> Also the names are well chosen AFAICT.
>
> I agree that the commit should be reverted and I already did the revert.
> Please accept my apology for the irritation about the build behavior.

No problem.  But in the future, please ask here first if you think you
find something in the build system that you can optimize.  Maybe it was
an oversight or it's a workaround that has become obsolete, but usually
there's an actual reason behind.


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

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [O] org manual not updating when pulling from git

[Marco Wahl]

Charles Millar  writes:
> I use make update. Now it is "working" as before.

Good!  This indicates that the revert of the commit in question has been
applied.

This is the commit message:

#v+
 Revert commit c90c7a33f53ad88dfcc583ad4c77bec306da0b22

 targets.mk: Revert to cleanup at every compile for 'standard' targets.

 Note: You can do 'dirty' builds with 'make compile-dirty' and 'make
 test-dirty'.
 - Disadvantage: these builds may fail due to the missing clean.
 - Advantage: typically the 'dirty' builds are much faster.
#v-


Best regards

   Marco

Re: [O] org manual not updating when pulling from git

[Charles Millar]

On 02/08/2017 11:39 AM, Nick Dokos wrote:

Charles Millar  writes:


So, how do you update?


I forgot about make doc; in the past I used it whenever I had to
recompile org from source; after that the pdf "just updated" each time
I pulled from git.


The question was: *how* do you pull from git? If you use one of the make
targets (e.g. make update), that's one thing; but if you use "git pull" or
some variant thereof that does *not* involve make, then the pdf would *not*
"just update" (unless you've set up some git hook to do some post-processing).


I use make update. Now it is "working" as before.

Charlie

Re: [O] org manual not updating when pulling from git

[Nick Dokos]

Charles Millar  writes:

>> So, how do you update?
>>
> I forgot about make doc; in the past I used it whenever I had to
> recompile org from source; after that the pdf "just updated" each time
> I pulled from git.
>

The question was: *how* do you pull from git? If you use one of the make
targets (e.g. make update), that's one thing; but if you use "git pull" or
some variant thereof that does *not* involve make, then the pdf would *not*
"just update" (unless you've set up some git hook to do some post-processing).

-- 
Nick

[O] org-table: Can't assign numbers to range

[Karl Voit]

Hi!

| foo |
|-|
| |
| |
|-|
| |
| |
|-|
#+TBLFM: @I$1..@II$1=1 :: @II$1..@III$1=2

Results in "user-error: Can't assign to hline relative reference"

Why?

I assumed to get following table as a result:

| foo |
|-|
|   1 |
|   1 |
|-|
|   2 |
|   2 |
|-|
#+TBLFM: @I$1..@II$1=1 :: @II$1..@III$1=2

-- 
get mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML into Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <
Personal Information Management > http://Karl-Voit.at/tags/pim/
Emacs-related > http://Karl-Voit.at/tags/emacs/

Re: [O] [Ann] Tool to hack time

[Marco Wahl]

Hi Stig,

Thanks for your feedback!

>> https://gitlab.com/marcowahl/hack-time is a little tool to forge the
>>[...]
>> Comments welcome, as always.
>
> I gave it a quick spin. The first thing that struck me was sadness at
> not finding an elpa package :-(

You are right, I think.  I'll propose the hack-time code soon as elpa
package.  Possibly in the form of a minor mode.  You are invited to
contribute to the realization as package.

> Anyway, I obtained it from its repo and I positioned calendar on 7th of
> February, and invoked it on an entry I forgot to mark as done yesterday.
> This is the result:
>
> ,
> | ** TODO Practice guitar
> |SCHEDULED: <2017-02-08 Wed ++1d/3d>
> |:PROPERTIES:
> |:STYLE:habit
> |:LAST_REPEAT: [2017-02-08 Tue 12:01]
> |:END:
> |:LOGBOOK:
> |- State "DONE"   from "TODO"   [2017-02-07 Tue 11:55] \\
> `
>
> Note that:
>
> - new scheduled time is correct
> - logbook entry is correct
> - LAST_REPEAT property is *incorrect*; I expect this too to be
>   [2017-02-07 Tue 11:55]

Yes.  I also noticed the issue with LAST_REPEAT.  I should have told in
the announcement that 'hack-time' depends on the Org 'master' branch
since about two weeks to handle LAST_REPEAT reliably.

Unfortunately 'hack-time' in its current form is not strong enough to
hack ANY time in Emacs.  Up to now 'hack-time' only applies to elisp
code when it calls 'current-time'.


Best regards,

   Marco

Re: [O] No priority cookies in html export despite setting pri:t option

[Nicolas Goaziou]

Hello,

Gez  writes:

> This happens even with a fresh "portable-style" installation of emacs
> and org-mode and no customisations
>
> When I export to plain text I can see the prioity cookies,  When I
> export to html there are none, even though I have created a local for
> that file and changed pri:nil to pri:t
>
> The html source file doesn't show the cookies - it's not just the html
> rendering or css.
>
> Any idea why?
>
> Gez
> Org-mode version 8.2.10
> Emacs version GNU Emacs 25.1.1 (x86_64-w64-mingw32)

I cannot reproduce the problem with latest Org. You may want to update
it.

Regards,

-- 
Nicolas Goaziou

Re: [O] Tables not converted to markdown format with markdown exporter

[Nicolas Goaziou]

Hello,

Joost Kremers  writes:

> There are certainly markdown variants that support tables,
> MultiMarkdown, PHP Markdown Extra and Pandoc markdown do, for example.

Org only supports vanilla markdown out of the box. So there is no table
conversion available (it is exported as HTML since vanilla markdown
does support raw HTML).

Various ELPA provide more advanced markdown conversion. The OP may use
those.

Since Org table and expected markdown tables are identical, another
option is to force to export raw tables by surronding them within
a #+begin_export md...#+end_export md block.

This can be done automatically in a dedicated hook, e.g.,
`org-export-before-parsing-hook'. See manual for details.


Regards,

-- 
Nicolas Goaziou

Re: [O] [Ann] Tool to hack time

[Stig Brautaset]

Hi Marco,

Marco Wahl  writes:

> Dear Orgers,
>
> https://gitlab.com/marcowahl/hack-time is a little tool to forge the
> `current-time' in Emacs.  This allows to mark todo-items done
> conveniently at another date.
>
> Maybe you want to play with that time forgery.
>
> Comments welcome, as always.

I gave it a quick spin. The first thing that struck me was sadness at
not finding an elpa package :-(

Anyway, I obtained it from its repo and I positioned calendar on 7th of
February, and invoked it on an entry I forgot to mark as done yesterday.
This is the result:

,
| ** TODO Practice guitar
|SCHEDULED: <2017-02-08 Wed ++1d/3d>
|:PROPERTIES:
|:STYLE:habit
|:LAST_REPEAT: [2017-02-08 Tue 12:01]
|:END:
|:LOGBOOK:
|- State "DONE"   from "TODO"   [2017-02-07 Tue 11:55] \\
`

Note that:

- new scheduled time is correct
- logbook entry is correct
- LAST_REPEAT property is *incorrect*; I expect this too to be
  [2017-02-07 Tue 11:55]


Stig

Re: [O] Tables not converted to markdown format with markdown exporter

[Joost Kremers]

On Wed, Feb 08 2017, Sharon Kimble wrote:

Roland Everaert  writes:


Hi,

Since a few weeks we use mattermost at work and I had recently 
to post a table to a team channel. I have created my table with 
org-mode, but when I export it to markdown format, the table is 
converted to html instead of markdown.


Is there any reason to that, except the simple fact that table 
conversion is not implemented yet?


As the markdown format is quite similar to the org-mode format 
regarding tables, I don't really see where could lie the 
difficulty.


Example:
- org format

| column 1 | column 2 | column 3 |
|---++-|
| some text | some more text | event more text |
| blah | 45 | fgf |

- markdown format
| column 1 | column 2 | column 3 |
|---||-|
| some text | some more text | event more text |
| blah | 45 | fgf |

This is obviously a very simple example, but usually, with 
mattermost, one doesn't post very complex messages.


Regards.


AFAIK markdown can't do tables. Any search of google won't show 
any ways

of doing markdown-tables because its not available on markdown.


There are certainly markdown variants that support tables, 
MultiMarkdown, PHP Markdown Extra and Pandoc markdown do, for 
example.


Roland, if Org export won't work, you may want to take a look at 
Pandoc. It accepts Org files as input and can produce Markdown 
files as output, and it supports a number of different types of 
tables. The kinds of tables you're looking for are called pipe 
tables in Pandoc's documentation:


http://pandoc.org/MANUAL.html#tables

HTH

--
Joost Kremers
Life has its moments

Re: [O] Tables not converted to markdown format with markdown exporter

[Sharon Kimble]

Roland Everaert  writes:

> Hi,
>
> Since a few weeks we use mattermost at work and I had recently to post a 
> table to a team channel. I have created my table with org-mode, but when I 
> export it to markdown format, the table is converted to html instead of 
> markdown.
>
> Is there any reason to that, except the simple fact that table conversion is 
> not implemented yet?
>
> As the markdown format is quite similar to the org-mode format regarding 
> tables, I don't really see where could lie the difficulty.
>
> Example:
> - org format
>
> | column 1  | column 2   | column 3    |
> |---++-|
> | some text | some more text | event more text |
> | blah  | 45 | fgf |
>
> - markdown format
> | column 1  | column 2   | column 3    |
> |---||-|
> | some text | some more text | event more text |
> | blah  | 45 | fgf |
>
> This is obviously a very simple example, but usually, with mattermost, one 
> doesn't post very complex messages.
>
> Regards.

AFAIK markdown can't do tables. Any search of google won't show any ways
of doing markdown-tables because its not available on markdown.

Sorry. I guess its back to the drawing board then?

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.6, fluxbox 1.3.5-2, emacs 25.1.1.1


signature.asc
Description: PGP signature

Re: [O] sub-files in org-mode problems

[Sharon Kimble]

Sharon Kimble  writes:

> I've now split my current working document up into four unequal parts
> because although it was only 1.6mbs if I made virtually any mistake,
> then emacs crashed! After it had crashed three times in very quick
> succession I'd had enough and spilt it up.
>
> And two things are causing problems.
>
> - How can I have a file split into two parts where the first part starts
>   with a chapter heading and then a minitoc, but the second part starts
>   with a section heading. I wasn't able to get it to work so I had to
>   create a new chapter heading which doesn't look right in the whole
>   document. So how can I have the second part starting with a section
>   heading please?
>
> - I'm currently getting error reports like this "Warning (:warning):
>   Bibtex-completion couldn't find entry with key "0340"." All my
>   bibliographic references are numbered and it looks like the sub-file
>   can't see or read the bibtex file, even though they're both in the
>   same directory. So how can I stop these error reports happening at
>   almost every key press please?

I've found the solution to this is to include the header line including
the bib database into the new include file, which effectively silences
its incessant bleating.

Like this -

╭
│#+LATEX_HEADER: \addbibresource{~/research/drugs/drugs17.bib}
│
│* Drugs - A to L
╰

Thanks
Sharon.


>
> Thanks
> Sharon.

-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.6, fluxbox 1.3.5-2, emacs 25.1.1.1


signature.asc
Description: PGP signature

[O] Tables not converted to markdown format with markdown exporter

[Roland Everaert]

Hi,

Since a few weeks we use mattermost at work and I had recently to post a
table to a team channel. I have created my table with org-mode, but when I
export it to markdown format, the table is converted to html instead of
markdown.

Is there any reason to that, except the simple fact that table conversion
is not implemented yet?

As the markdown format is quite similar to the org-mode format regarding
tables, I don't really see where could lie the difficulty.

Example:
- org format

| column 1  | column 2   | column 3|
|---++-|
| some text | some more text | event more text |
| blah  | 45 | fgf |

- markdown format
| column 1  | column 2   | column 3|
|---||-|
| some text | some more text | event more text |
| blah  | 45 | fgf |


This is obviously a very simple example, but usually, with mattermost, one
doesn't post very complex messages.

Regards.