On Tuesday, 6 Nov 2018 at 19:32, Nik Clayton wrote:
> Hoi,
>
> I've been writing a few things using Org where I'm making frequent use of
> noweb references in SRC blocks, and decided that completion would be handy
> for them.
Thanks for this. Very useful. I'll incorporate it into my config and
What about passive date stamps?
TODO Thing
?
-k.
Please excuse brevity. Sent from tiny pocket computer with non-haptic
feedback keyboard.
On Tue, Nov 6, 2018, 17:19 Leo Gaspard Eric S Fraga writes:
> > On Tuesday, 6 Nov 2018 at 22:59, Leo Gaspard wrote:
> >> It is a task, so I want to be
Eric S Fraga writes:
> On Tuesday, 6 Nov 2018 at 22:59, Leo Gaspard wrote:
>> It is a task, so I want to be able to mark it as done and not see it for
>> the rest of the day. But at the same time I can't SCHEDULE <> it,
>> because otherwise if I don't do it the right day then it still bothers
>>
On Mon, Nov 5, 2018, 13:59 Nicolas Goaziou
> What would be the expected output?
>
There is no output. It doesn't even export. It's a showstopper. No
references to equations allowed or the exporter fails.
-k.
So, this really isn't ready for anyone else to use yet, but I've spent the
last day or so exploring the API for the Canvas Learning Management System
and adapting my grading system to interact with it. My results are rough
and I think a little buggy (I'm worried about timeouts and how to manage
the
On Mon, 5 Nov 2018 at 21:46, Nicolas Goaziou wrote:
>
> Philip Hudson writes:
>
> > On Sun, 4 Nov 2018 at 14:03, Nicolas Goaziou wrote:
>
> >> No, it is not the case. AFAIU, in the minimal failing case, you capture
> >>
> >> #+FOO: bar
> >> * Baz
> >>
> >> This is _not_ a node. A node st
Hoi,
I've been writing a few things using Org where I'm making frequent use of
noweb references in SRC blocks, and decided that completion would be handy
for them.
This function will complete "^<<" with a list of the defined named blocks
in the current file, if you're in a SRC block.
It could be
On Tuesday, 6 Nov 2018 at 22:59, Leo Gaspard wrote:
> It is a task, so I want to be able to mark it as done and not see it for
> the rest of the day. But at the same time I can't SCHEDULE <> it,
> because otherwise if I don't do it the right day then it still bothers
> me the day after, at which I
Hello,
Calvin Beck writes:
> I have this problem where I have a capture template like this:
>
>> ("t" "Todo" entry (file+headline "~/org/todo.org" "Tasks")
>>"* TODO %?\n SCHEDULED: %t\n %a\n")
>
> And then if I have another heading under Tasks...
>
>> * Tasks
>> * HEADING2
>
> Then when
On 06-11-18 16:35, Christian Moe wrote:
>
> I believe the need to use quotation marks around the style file name was
> removed at some point
I didn't know that. I had a quick look at the changes to ox-odt.el for
the last few months, but it doesn't seem to be mentioned in any of the
commit messag
AH, THISI S SUPER-HELPFUL, aARON. MANY THANK. i'M HOPING THAT BY THE TIME
i RETIRE i WILL BEGIN TO UNDERSTAND LEXICAL SCOPING IN LISP...
On Tue, Nov 6, 2018 at 10:35 AM Aaron Ecay wrote:
> Hi Matt,
>
> 2018ko azaroak 6an, Matt Price-ek idatzi zuen:
> >
> > Hi,
> >
> > I was writing a function
I believe the need to use quotation marks around the style file name was
removed at some point, and the manual is out of date. Instead of
#+ODT_STYLES_FILE: "template.ott"
the manual ought now to read:
#+ODT_STYLES_FILE: template.ott
Yours,
Christian
L.C. Karssen writes:
> Hi list,
>
> No
Hi Matt,
2018ko azaroak 6an, Matt Price-ek idatzi zuen:
>
> Hi,
>
> I was writing a function to quickly post the ocntents of subtrees to the
> Canvas Learning Management System. I was trying to strip down the exported
> HTML to an absolute minimum and had forgotten about the body-only paramter
Hi list,
Not sure if this is related (or fixed with the aforementioned patch)
because I'm not using a list for the ODT style file.
Today, after upgrading from Org 9.1.13 (actually installed from melpa on
20180625) to melpa version 20181105 exporting to ODT stopped working. In
my org file the styl
Hi Julius,
Julius Dittmar writes:
> if you want a task to re-open at a later date upon closing, add a line of
> :REPEAT_TO_STATE: TODO
> to the PROPERTIES drawer of that task.
Well, I guess I stated my problem poorly, sorry :)
Here is a translated example task from my .org file:
*** TODO Check
Hi,
I was writing a function to quickly post the ocntents of subtrees to the
Canvas Learning Management System. I was trying to strip down the exported
HTML to an absolute minimum and had forgotten about the body-only paramter
to org-export-as (!!). So, my solution was to try to rebind
'org-html-
Hello world,
I am trying to figure out a way to represent, in org-mode, tasks that
should be performed exactly on one day of the week. For instance, taking
out the garbage.
It is a task, so I want to be able to mark it as done and not see it for
the rest of the day. But at the same time I can't S
Hi Leo,
if you want a task to re-open at a later date upon closing, add a line of
:REPEAT_TO_STATE: TODO
to the PROPERTIES drawer of that task.
Hth,
Julius
Hello all!
It's been ~2 weeks so I hope you'll forgive me bumping my post :)
Do you have an opinion about this idea?
Cheers,
Leo
Leo Gaspard writes:
> Hello all!
>
> I have been using org-mode for a few days (switching over from
> todo.txt [1]), and for the time being my experience has been
Hi fellow people :)
So like a lot of you, I'd love to write all my documentation in orgmode.
However I work with gitlab flavoured markdown a lot in our environment.
Wishfully one can convert easily between orgmode and markdown and back
again.
Therefore I need to be able to convert easily back an
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
21 matches
Mail list logo
