On Thursday, 1 Nov 2018 at 18:49, Nicolas Goaziou wrote:
> As I was offline for a few days, I toyed a bit with this. I wrote the
> following library. I didn't test it thoroughly. I didn't write
> regression tests either.
Although I probably won't use this often, I have tried it out and it
seems t
Nicolas Goaziou writes:
>> ---
>> lisp/org-src.el | 9 -
>> lisp/org.el | 9 ++---
>> 2 files changed, 14 insertions(+), 4 deletions(-)
>>
>> diff --git a/lisp/org-src.el b/lisp/org-src.el
>> index 42e1225ed..0426ff96a 100644
>> --- a/lisp/org-src.el
>> +++ b/lisp/org-src.el
>
Greetings all,
I am looking into using `org-invoice` to generate some invoices. It uses
the CLOCKSUM property, which according to the docs gets auto-generated when
the clock entries are summed in a subtree.
Concretely, docs say: "CLOCKSUM: The sum of CLOCK intervals in the
subtree. ‘org-clock-sum
On Thu, Nov 1, 2018 at 9:58 AM Eric S Fraga wrote:
> Cannot help you on this but I did enjoy reading the references for the
> students! :-)
> --
> Eric S Fraga via Emacs 27.0.50, Org release_9.1.11-620-ga548e4
>
Having @ckelty on the CC: list inspires me no end.
Philip Hudson writes:
> Here's a minimal failing capture-completed template:
>
> --- Cut here --
>
> #+FOO: bar
>
> * Baz
> -- Cut here --
I would like to see you capture template in its elisp form, i.e., as set
in `org-capture-templates'.
Thank you.
Hello,
"Garreau, Alexandre" writes:
> This is an argument in favor of immobility.
True. Immobility is sometimes good, too.
> Yes, if only each user of each piece of software took the time to read
> the integrality of documentation each time they used something: I don’t
> and only did partially
On Thu, 1 Nov 2018 at 22:12, Nicolas Goaziou wrote:
>
> Philip Hudson writes:
>
> Could you show your template? Could you explain how you initiate the
> capture process (e.g., with arguments)? Also, could you show the desired
> output?
Here's a minimal failing capture-completed template:
--
timestamps in link descriptions use {} instead of []. are there
functions to get the time from those?
org-entry-get on "TIMESTAMP_IA" will get the time from this:
* CONVERSATION [2018-11-01 Thu 11:09] cleaned using generic cetaphil
analogously, if the keyword is CONVLINK, i want to get the ti
Hello,
Nils Gustafsson writes:
> I stubled upon this while trying to work out why my clocktables
> weren't behaving as expected. In one of my org files I have several
> large trees set up to use different archive files via :ARCHIVE:
> properties, and the clocktable I added with :scope file-with-
Hello,
Philip Hudson writes:
> I expected my (previously working) org-capture template to be
> inserted into a newly-created empty Org file. The file name and
> location are the output of a function specified in the template
> (sequentially numbered filename).
Could you show your template? Coul
Leo Gaspard writes:
> Nicolas Goaziou writes:
>>> Small issue I've been having with org-mode: full-width characters
>>> (eg. 何か) appear to be breaking column display.
>>
>> Org tables assume a fixed-width font. You need to use one, if such
>> thing exists for these characters.
>
> Well, it is f
Hello,
Jared Windover writes:
> I was still seeing this error. Switching signum to cl-signum in org.el
> fixed it.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Matt Price writes:
> On Tue, Oct 30, 2018 at 5:41 PM Tim Cross wrote:
>
>>
>> I've never delved into the XML nightmare that is ODT and stick with
>> latex/PDF export.
>>
>> Here is how I handled needing to have a logo and banner at the top of my
>> documents. Essentially, it involves using the
Hello,
This LaTex code to put before \begin{document} :
\AtBeginSection[]{\begin{frame}\frametitle{}\tableofcontents[currentsection,hideothersubsections]\end{frame}}
is very useful, because it recalls the steps of your presentation and
focuses on the current section.
I hope that helps.
Bes
Nicolas Goaziou writes:
>> Small issue I've been having with org-mode: full-width characters
>> (eg. 何か) appear to be breaking column display.
>
> Org tables assume a fixed-width font. You need to use one, if such
> thing exists for these characters.
Well, it is fixed-width, but twice the width
I was still seeing this error. Switching signum to cl-signum in org.el
fixed it.
-Jared
Hello,
Kevin Brubeck Unhammer writes:
> The attached patch solves this, as far as I can tell.
I rewrote `org-clocktable-steps' in "next" branch, and the bug doesn't
seem to appear there. Therefore, I applied your patch in master, but
dropped it in next, except for the test.
Thank you.
Regards
On 2018-10-31 15:27, John Kitchin wrote:
You do have to close the org-file, and then reopen it after you make
that file, and when I do that I am prompted whether to apply or ignore
the settings.
Oh! may be I need to re-open the file. I tried with reloading dir-local
variables and reverting the
the bibliography link is just for bibtex. If you are using biblatex/biber I
think you would put that in a latex header, e.g.
#+latex_header: \addbibresource{References.bib}
Both of these are file-local though, and won't affect other files in that
directory.
John
Hello,
"Garreau, Alexandre" writes:
> No it doesn’t update anything, and doesn’t color number compatibly with
> outlining. Also it’s not integrated in org and only available in melpa,
> unsigned.
As I was offline for a few days, I toyed a bit with this. I wrote the
following library. I didn't
Hello,
stardiviner writes:
> I regenerated the patch.
Thank you. Some more comments.
> * org-src.el (org-src-source-file): Add a variable to get the file path
>at the beginning of the function `org-src--edit-element'.
> * org.el (org-insert-link): support option org-link-file-path-type
>
Hello,
Will Pierce writes:
> * add brief docstring pointing to outline-on-heading
> From 41796f33d083367bf99303cb8d33f289472825b5 Mon Sep 17 00:00:00 2001
> From: pierwill <19642016+pierw...@users.noreply.github.com>
> Date: Thu, 1 Nov 2018 10:08:35 -0500
> Subject: [PATCH] document org-at-headi
Hello,
Leo Gaspard writes:
> Small issue I've been having with org-mode: full-width characters
> (eg. 何か) appear to be breaking column display.
Org tables assume a fixed-width font. You need to use one, if such
thing exists for these characters.
Regards,
--
Nicolas Goaziou
Hi Gustav,
I played a bit with your proposition. I like it; in particular the
completion function to insert links from the attachment directory with
C-c C-l attached RET
It seems natural to me to have a more specific link type for attached
files.
In my opinion your patch should be applied
Hello,
Small issue I've been having with org-mode: full-width characters
(eg. 何か) appear to be breaking column display.
Does anyone know of a workaround for this?
Cheers, and thank you for making org-mode as great as I'm currently
discovering it is!
Leo
The attached patch solves this, as far as I can tell.
I have signed the FSF copyright papers.
best regards,
Kevin Brubeck Unhammer
From e818cd5d1c651a516a0e791a10d91fe1e310cde9 Mon Sep 17 00:00:00 2001
From: Kevin Brubeck Unhammer
Date: Thu, 1 Nov 2018 13:59:09 +0100
Subject: [PATCH] org-clock
* add brief docstring pointing to outline-on-heading
0001-document-org-at-heading-p.patch
Description: Binary data
Cannot help you on this but I did enjoy reading the references for the
students! :-)
--
Eric S Fraga via Emacs 27.0.50, Org release_9.1.11-620-ga548e4
This isn't really an answer to your question, but I keep all my lectures
for each course in a single file, then export subtrees when I need them.
For me, this works well. I have recently started using a -dwim export
scope based on Kaushal's org-hugo-export-dwim functions. But... I seem to
have l
OK, so I'm getting close to being able to do this. My almost-working
example doc is at the bottom of this email, I have a question about
suppressing the headline text.
On Tue, Oct 30, 2018 at 11:50 PM ckelty ckelty wrote:
> Matt,
>
>
> > On Oct 30, 2018, at 6:26 PM, Matt Price wrote:
> >
> > Hi
Hoi,
What's the best way to process (ideally using the org-element API) a
collection of .org files as one larger file?
I'm using Org + ox-reveal to write the course material for a three month
course. This is a lot of material, so keeping it in one Org file is not
practical (exporting it to the sl
Two further thoughts:
1. That regexp works but it should really start with "^":
(org-capture-verify-tree (replace-regexp-in-string "^#\+[^\n]*\n" ""
template))
2. The fix I propose is a kludge. The real problem is the semantics of
function `org-capture-insert-template-here'. My assertion: ther
32 matches
Mail list logo
