Dear
emacs-orgmode,
Your Email Account was just signed in on a new Windows device from this IP
185.232.21.169.
You're getting this email to make sure it was you.
If you don't recognize this activity, it means someone else may have accessed your Email Account.
For your protection, pleas
Matt Price writes:
> On Tue, Sep 8, 2020 at 11:27 AM Matt Price wrote:
>> On Tue, Sep 8, 2020 at 10:53 AM Bastien wrote:
>>
>>> Matt Price writes:
>>>
>>> > In a new org file, add these lines:
>>> >
>>> > #+begin_src python
>>> > print
>>> > #+end_src
>>> >
>>> > position cursor inside block a
On 2020-09-10 21:06, Ihor Radchenko wrote:
I do appreciate all the replies so far. However as I plan on relying
on this to implement some quite critical functionality for a package I
am working on (a sort of Zettelkasten / TiddlyWiki in Orgmode if you
will) I would feel a lot more comfortable wi
> I do appreciate all the replies so far. However as I plan on relying
> on this to implement some quite critical functionality for a package I
> am working on (a sort of Zettelkasten / TiddlyWiki in Orgmode if you
> will) I would feel a lot more comfortable with some additional
> reassurences tha
On 2020-09-10 18:20, Samuel Wales wrote:
this or something similar has definitely been discussed on this
mailing list. so you are not alone.
Yes, I also thought certainly this must have been discussed before. I
did try searching the list, but I think the relevant search terms are
too common,
i see the problem. but i get confused about the real-world purpose of
this feature. is the idea that technically someplace in the real
world you are supposed to work on it but you have decided not to and
you don't want the agenda to show it until you will work on it?
On 9/10/20, Bastien wrote:
the problem for eldoc for me is that for some reason it gets pretty
confusing trying to implement lots of things all at once, at least
when emacs is already using it for something, or so.
here is my current jumble of code. it does work. and has comments
but idk if it is of any use. or even unde
Hi TRS-80,
Your approach should work just fine. So fine, in fact, that it's already kind
of built in! Configure org-id-method and set it to 'ts and you'll get
timestamps as ID instead of uuid.
I do believe the manual lacks a description for this. Not entirely sure though,
and can't check atm.
this or something similar has definitely been discussed on this
mailing list. so you are not alone.
although i undersatnd the whole thing as readable id's. dunno if that
is the prupose.
maybe something like a timestamp and then the usual id would give you
pretty good uniqueness.
On 9/10/20, T
On 2020-09-10 18:00, Gustav Wikström wrote:
Hi TRS-80,
Your approach should work just fine. So fine, in fact, that it's
already kind of built in! Configure org-id-method and set it to 'ts
and you'll get timestamps as ID instead of uuid.
I do believe the manual lacks a description for this. No
more than one clock can be useful, but maybe need not be org-related,
even if that would be nice? for example, your laundry is due in 45m,
tea will be steeped in 8m, etc.
i believe there is a package that allow many non-org clocks and has a
list-timers or so that shows you what you have running.
On 2020-09-06 22:52, Daryl Manning wrote:
PS> As an outside feature though, interoperability of the org-contact
formats with other operating system address books, most notable gnome
contacts/evolution, goog contacts, and OSX address book would be high
on my list in terms of improving org-contacts
On 2020-09-04 13:14, Bastien wrote:
Hi Carlo,
Carlo Tambuatco writes:
how long something takes to compile
I have set my shell prompt with a timestamp for exactly this reason. I
have also seen someone who set it to reflect elapsed time since last
command, instead.
But I guess maybe you
Bastien writes:
> Hi Brett,
>
> thanks for sharing this! I had no chance yet to test this but it
> looks useful. I added a link to https://orgmode.org/worg/org-tools/
>
> Best,
Hello Bastien,
Thank you for the addition! I appreciate your support.
Brett Gilio
First, I want to express my sincere and heart-felt gratitude to Carsten
(and other contributors) for making and sharing this wonderful piece of
software. I have come to refer to it as "one of the gateway drugs to
Emacs" (the other being Magit, IMHO). It was certainly one of (if not
/the/) mai
Hi there,
First thanks again guys for all the works you doing on org-mode !
I'm searching a way or an example of workflow for such a thing i consider as a
common pattern for reproductibility
(reproductible papers in science for example).
For example, i'm starting writing a blog post with org-m
Hi Bastien,
Thanks! I agree it would be nice to have a comprehensive list of org
exporters in worg - although usually a search for "org export "
points in the correct direction :)
Best,
--Diego
On Thu, Sep 10, 2020 at 3:53 PM Bastien wrote:
> Hi Diego,
>
> Diego Zamboni writes:
>
> > I'm hap
Hi Bastien,
As far as I can tell, with 8a083514a7 from master, the situation is now
as follows.
The org-block face is applied
- to src blocks, when the language is recognized
- to example, export blocks
- to verse and quote blocks, if ~org-fontify-quote-and-verse-blocks~
is ~t~.
It isn't
I'll keep researching and see if I can come up with anything.
This is particularly difficult.
When instrumenting `org-add-planning-info` with edebug the
resulting timestamp always has its time portion (given and/or
end-time) ignored.
Tried it with both my personal setup and emacs -q. No lu
06.09.2020 21:18, Kévin Le Gouguec wrote:
Boruch Baum writes:
In org-mode, when POINT is moved over an org-mode link, wouldn't it be
reasonable for the value of that link to appear in the mini-buffer? The
advantage of that is the user would know where the link points and what
would happen if t
09.09.2020 11:52, Maxim Nikulin wrote:
Capture templates allow calling of arbitrary lisp code, so you could
take value from kill ring or call low level gui-get-selection function.
The latter would allow separate templates for primary selection and for
clipboard.
Today I have noticed that th
Hi Brett,
thanks for sharing this! I had no chance yet to test this but it
looks useful. I added a link to https://orgmode.org/worg/org-tools/
Best,
--
Bastien
Hi Russell,
Russell Adams writes:
> I saw a cool Org related project come up on Reddit, but no announcement
> here. This is a repost for community interest, I claim no credit.
I added a link in https://orgmode.org/worg/org-tools/
Thanks!
--
Bastien
Hi Diego,
Diego Zamboni writes:
> I'm happy to announce that my package ox-leanpub is now available in
> MELPA.
I added a link to https://orgmode.org/worg/org-tools/
Links to Org external exporters should perhaps have a dedicated
section and/or page, especially if/when we will move some out of
Hi Timothy,
TEC writes:
> I've just pushed the initial version of a package I think is pretty nifty (no
> bias here ;) and thought it might me nice to mention it to the mailing list.
>
> https://github.com/tecosaur/org-pandoc-import
I've added a note to https://sr.ht/~brettgilio/org-webring/
T
Hi,
h...@protonmail.com writes:
> It says:
> "If you want to delay the display of this task in the agenda, use
> ‘SCHEDULED: <2004-12-25 Sat -2d>’: the task is still scheduled on the
> 25th but will appear two days later. In case the task contains a
> repeater, the delay is considered to affect a
Hi Gustavo,
Gustavo Barros writes:
> Thank you for keeping track of this. But this issue is currently not
> affecting us any longer.
... and thanks for double-checking this.
> Some of the relevant messages are:
>
> - Kyle's message stating the commit was reverted, with the
> corresponding
Hello Sharon,
Unfortunately I cannot reproduce your issue. I created a list of 56 sub heading
and I
can view the heading Still a sample 0 until Still a sample 56.
** TODO * etc and onwards
** TODO * and another one
** Still a sample 0
** Still a sample 1
** Still a sample 2
** Still a sample
Hi Bastien,
On Thu, 10 Sep 2020 at 02:34, Bastien wrote:
Hi Gustavo,
Gustavo Barros writes:
As of recently, repeating tasks are no longer showing up in the
agenda
for future dates. Below a minimal example of the issue:
Just confirming this issue, to make sure we don't forget it.
Thank
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'm having major problems with my imenu setup, and its like this.
- --8<---code one---start->8---
* Outlining and Plotting
** Level 2 heading
** etc and onwards
- --8<---cut here---end
Hello, Bastien,
Thanks for getting back to me.
In ob-core.el, function org-babel-expand-noweb-references, line 2747,
there is a 'mapconcat, that is commented as ";; Interpose PREFIX
between every line."
It prepends the "prefix", that is the content of the block to be
expanded from the beginning of
>> You are right. I missed that \\ is also a newline for LaTeX export.
>
> It is a line break in any export back-end.
I did not know this and I cannot find any reference about such behaviour
in manual (info:org#Markup for Rich Contents).
>> However, it is unused it unordered lists. We might defin
Hi Nicolas,
Nicolas De Jaeghere writes:
> As of commit 7769518f3, source code blocks are no longer natively
> fontified when org-src-fontify-natively is set to t.
Fixed, thanks.
The original "bug" I was trying to fix with 7769518f3 seems like a
documentation bug, so I enhanced the docstring o
As of commit 7769518f3, source code blocks are no longer natively
fontified when org-src-fontify-natively is set to t.
To reproduce, create an org-mode buffer and insert:
#+BEGIN_SRC emacs-lisp
(setq foo 'foo)
#+END_SRC
Expected: setq is fontified according to font-lock-keyword-face. Actual:
s
I don't know how to debug this.
The *Org-Babel Error Output* emerges when the control flow returns
from the following sexp:
(org-babel-execute-src-block
current-prefix-arg (org-babel-get-src-block-info nil context))
It is line 17862 in the org.el
I do not understand what causes its appear
Vladimir Nikishkin writes:
> So, my point is the following. A shebang is an almost universally
> accepted way to specify which interpreter should be used for code
> evaluation.
>
> In the ob-core.el, at line 787, the function called
> org-babel-expand-src-block makes a buffer out of the noweb-e
Well, why exactly Racket people decided to introduce the #lang
directive in such a way that it looks like a shell comment or a
shebang line seems to elude my understanding.
(declare :lang 'whatever), at least to me, seems much more lispy, and
even (read) able by a standard reader (which could later
Hi Vladimir,
I have encountered similar issues with wanting to have a racket
#lang line included in a tangled block while also allowing org to know
exactly which #lang it is working with. I haven't found a good
solution. One issue with embedding the shebang when editing a buffer
is that it is ve
It still behaves as described.
Let me describe it in more detail:
suppose you have the following file
```
# -*- mode:org; -*-
#+name: empty
#+begin_quote
#+end_quote
#+begin_src shell :stdin empty
#+end_src
```
the #+end_src line should be the line number 8 in the file.
Place the point at the
39 matches
Mail list logo
