Re: [O] org-annotate/collaboration?

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

Re: [O] org-annotate/collaboration?

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

[O] %( in capture template

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-l

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

> 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 subheading

Re: [O] Help checking orgcard.pdf

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

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") >

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

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-expo

[O] org-annotate/collaboration?

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

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

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)

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 th

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

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

[O] 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

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

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.

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

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 sho

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

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 c

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

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?

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

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

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

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 | |-| #+T

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

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

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

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 p

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

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 m

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

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

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

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

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

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

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

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

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

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