It is a minor thing, but it sort of bugs me:
When I press in a new plain list item it demotes it, as it should.
But when I press again, it does not move to the parent level, like
a new headline would. Rather, it goes to the initial level first, before
moving on to the parent levels.
Is
stardiviner writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> George Mauer writes:
>
>> With VSCode becoming ever-popular it seems like there might be some value
>> in getting org mode working there simply as a way of promoting org as an
>> excellent literate coding notebook.
> I remember I found this code on emacs.stackexchange.com website.
>
> I did a Google search now, I found someone indeed proposed this feature. Here
> is
> the email archive:
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2019-08/msg00013.html
>
> I saw this thread is stopped. Seems no
Apologies, one last patch.
On Sat, May 23, 2020 at 7:02 PM Nick Daly wrote:
> : "^\\*?[[:upper:]][\\._[:alnum:]]*\\(?:
> \\*?[[:upper:]][\\._[:alnum:]]*\\)*\\( λ\\)?> "
>
> =comint-prompt-regexp='s variable documentation calls out much simpler
> regexps
>
> : "^[^>]+\\(> \\)?"
This simplified
Hi Kyle, thanks for the thoughtful analysis.
On Wed, May 20, 2020 at 12:51 AM Kyle Meyer wrote:
> So it looks like the member call above is returning nil because the
> prompt markers are corrupting the element. If that's the case, it seems
> like the output cleansing should happen upstream of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John Kitchin writes:
> Where did you find that code? I recall this was some kind of prototype
> code, and maybe it never got fully developed. I think desk was shorthand
> for description.
I remember I found this code on emacs.stackexchange.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
George Mauer writes:
> With VSCode becoming ever-popular it seems like there might be some value
> in getting org mode working there simply as a way of promoting org as an
> excellent literate coding notebook.
>
> VSCode already has a halfway
Consider the following example:
#+begin_src org
,#+title: Test
,#+options: H:2
,* Section
:PROPERTIES:
:CUSTOM_ID: section
:END:
,** Frame
:PROPERTIES:
:CUSTOM_ID: frame
:END:
,*** Block
:PROPERTIES:
:CUSTOM_ID: block
:END:
#+end_src
If I export this to Beamer,
Hi.
This looks quite similar to my approach to producing course material,
which is documented here : https://olberger.gitlab.io/org-teaching
including the use of Docker (see
https://gitlab.com/olberger/docker-org-teaching-export/ )
Hth,
Best regards,
Jens Lechtenboerger writes:
> On
Kyle Meyer writes:
> * lisp/org-agenda.el (org-agenda-filter-make-matcher): Combine filter
> forms with `and' unless multiple positive categories are given.
Thanks Jorge for reporting this and Kyle for fixing my mistakes here!
--
Bastien
Hi George,
George Mauer writes:
> Any thoughts on the feasibility of this?
Well, I suggest you discuss with the developers of VS Code themselves.
Best,
--
Bastien
Bastien writes:
> Axel Kielhorn writes:
>
>> while exchanging mails with Uwe Brauer I discovered some errors in
>> the manual:
>
> just a note to say it has been fixed by Kyle a while ago:
> https://code.orgmode.org/bzg/org-mode/commit/861ffb31
>
> Sorry if a confirmation has already been sent,
Github link to the patch:
https://gist.github.com/yantar92/6447754415457927293acda43a7fcaef
Ihor Radchenko writes:
> The patch is attached
>
> diff --git a/contrib/lisp/org-notify.el b/contrib/lisp/org-notify.el
> index 9f8677871..ab470ea9b 100644
> --- a/contrib/lisp/org-notify.el
> +++
Hi Roland,
Roland Coeurjoly writes:
> Please find patch attached.
Thanks -- I'll let Nicolas apply it, since he has been following this,
but just some nitpicking for later contributions below:
> From 4d8660eea35ea13809914271562f0ff73507f967 Mon Sep 17 00:00:00 2001
> From: Roland Coeurjoly
>
Hi Gijs,
> Looking in my init.el "customisation" section, I see org-bbdb,
> org-bibtex, org-docview, org-gnus, org-info, org-irc, org-mhe,
> org-rmail, and org-w3m. Did I put those there? I guess.
>
> So, I remove these, but even though I restarted Emacs, now the value of
> org-modules is nil.
Hi Tory,
thanks for reporting this here.
torys.ander...@gmail.com (Tory S. Anderson) writes:
> Per alphapapa's suggestion to bring this up to this list, it seems
> that everyone (doom, spacemacs, and individuals) are rolling their own
> of a functionality that should be included in core: the
Sorry, I was working on the emacs git repo, which seems to be a bit behind
the org mode one.
Please find patch attached.
On Sat, May 23, 2020 at 4:02 PM Bastien wrote:
> Hi Roland,
>
> Roland Coeurjoly writes:
>
> > I have done a clean clone and I still don't see a 9.4 section in
> > master.
>
Hi Roland,
Roland Coeurjoly writes:
> I have done a clean clone and I still don't see a 9.4 section in
> master.
> Is it in another branch?
It is here in the master branch:
https://code.orgmode.org/bzg/org-mode/src/master/etc/ORG-NEWS#L13
--
Bastien
Where did you find that code? I recall this was some kind of prototype
code, and maybe it never got fully developed. I think desk was shorthand
for description.
On Sat, May 23, 2020 at 8:24 AM stardiviner wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> I found some examples
Hi Vladimir,
Vladimir Alexiev writes:
> org-babel-uppercase-example-markers says whether to insert BEGIN_SRC
> or begin_src.
Not really, it says whether to insert BEGIN_EXAMPLE or begin_example.
FWIW I think we should stick to the convention that Org inserts
lower-case #+begin* keywords as a
The patch is attached
diff --git a/contrib/lisp/org-notify.el b/contrib/lisp/org-notify.el
index 9f8677871..ab470ea9b 100644
--- a/contrib/lisp/org-notify.el
+++ b/contrib/lisp/org-notify.el
@@ -246,7 +246,7 @@ seconds. The default value for SECS is 20."
(switch-to-buffer
Hello,
[The patch itself will be provided in the following email]
I have five updates from the previous version of the patch:
1. I implemented a simplified version of element parsing to detect
changes in folded drawers or blocks. No computationally expensive calls
of org-element-at-point or
Hi,
stardiviner writes:
> I found some examples setting org-link-parameters with ":desk", like this:
>
> #+begin_src emacs-lisp
> (defun org-id-link-desk (link desk)
> "Description function for id: link."
> (let ((id (cadr (split-string link ":"
> (org-with-point-at (org-id-find id
Hi,
ndame writes:
> I tried to add stuck projects to my block agenda, but I did not find the
> relevant
> keyword. Then I googled and it found this discussion which mentions the stuck
> keyword:
>
>
org-babel-uppercase-example-markers says whether to insert BEGIN_SRC or
begin_src.
org-babel-demarcate-block doesn't respect this setting:
https://code.orgmode.org/bzg/org-mode/src/master/lisp/ob-core.el#L1893
makes this check
(lower-case-p (and block
(let (case-fold-search)
On Sat, May 23, 2020 at 02:57:26PM +0200, Roland Everaert wrote:
> There must be also some kind of "protocol" to transition between the
> various discussions, like
> - from bug to a normal question
> - normal question to a feature request
>
You are aware this is how the Emacs bug mailing list
Thank you for the suggestions, but my main problem is to define the network
interface correctly, and, probably, the firewall correctly.
With regard to nomachine, it seems more about accessing remote hosts than
the guest OS of a host OS. So it seems more of an overkill to me, anyway,
can still be
Nicolas Goaziou writes:
> This looks hackish.
Any bit in particular? AFAICT hack-local-variables-hook is the expected
way to perform plumbing that might be affected by file/directory-local
variables. It is used by e.g. shell-script-mode, cc-mode, markdown-mode
and AUCTeX, to name a few. The
I have to admit that I am kind of a state tracking freak, so, your proposal
is welcomed to keep that tendency at bay.
However, I would add a "category" for bugs/issues and feature requests, in
the subject, else, the bot, the readers and the maintainer will have still
to dig deep into threads to
Bastien (b...@gnu.org) wrote:
> Hi Karl,
Hi Bastien,
> I fixed this here:
> https://code.orgmode.org/bzg/org-mode/commit/ceb0ef95fb
> Thanks for the report,
Perfect timing for the fix - thank you!
--
Karl Voit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I found some examples setting org-link-parameters with ":desk", like this:
#+begin_src emacs-lisp
(defun org-id-link-desk (link desk)
"Description function for id: link."
(let ((id (cadr (split-string link ":"
(org-with-point-at
Thanks for the response, Bastien. No one has answered up, suggesting that
there's not widespread interest.
On Sat, May 23, 2020 at 4:29 AM Bastien wrote:
> Hi,
>
> "D. C. Toedt" writes:
>
> > For an ongoing pro bono project, it would be nice if there were an
> > in-buffer #+OPTION:
I have done a clean clone and I still don't see a 9.4 section in master.
Is it in another branch?
On Sat, May 23, 2020 at 7:12 AM Kyle Meyer wrote:
> Hi Roland,
>
> Roland Coeurjoly writes:
>
> > I added version 9.4 to ORG-NEWS.
> > Please tell me if that's OK or I should instead put it in 9.3.
tecos...@gmail.com writes:
> Don't worry, I haven't faded out of exitance!
Well, I was not worried :)
> I've also now completed the FSF copyright assignment. Let me know if
> you need any details on that front.
If you confirm that the FSF confirmed that you're all set, then no.
> I'm yet to
Hello Bastien,
thanks for replying. I am considering this post:
http://duncan.codes/posts/2019-09-03-migrating-from-jekyll-to-org/index.html
But I still need to figure out how I will try to avoid loosing too much
traffic due to 404 caused by blog posts not pointing to the same url.
Will keep you
Hi,
"D. C. Toedt" writes:
> For an ongoing pro bono project, it would be nice if there were an
> in-buffer #+OPTION: configuration for footnotes, when exporting to
> HTML (or DOCX or PDF), to have the footnote text in small print just
> below the paragraph in which the footnote reference
Hi Axel,
Axel Kielhorn writes:
> while exchanging mails with Uwe Brauer I discovered some errors in
> the manual:
just a note to say it has been fixed by Kyle a while ago:
https://code.orgmode.org/bzg/org-mode/commit/861ffb31
Sorry if a confirmation has already been sent, I could not find it
Bastien writes:
I hope you will have time to move forward with sending patches
so that
we can discuss the feature proposals against something we can
actually
test.
Thanks again,
Don't worry, I haven't faded out of exitance! I've merely become
(as usual)
distracted. In this case I've
Hi Alejandro,
Alejandro Alcalde writes:
> Hello, I am looking to migrate from Hugo to org-publish, is there an
> easy way? I’ve have found several guides to migrate from jekyll, like
> this one: https://duncan.codes/posts/
> 2019-09-03-migrating-from-jekyll-to-org/index.html 2
I don't have any
Hello,
"Thomas S. Dye" writes:
> Barring a guru's user-end customization, Rasmus's figure :environment
> attribute idea is a good one.
FWIW, I also think this is a good idea.
Thanks to those who help with this thread!
--
Bastien
Hi Timothy,
thanks for the various feature requests! It's always interesting to
discuss use cases and possible features.
Timothy writes:
> I'm also a uni student a few weeks off from exams so I am not able to
> really need to resist the urge to jump in and work on implementing
> these ideas.
Hi Stefan,
thanks for this refactoring, it is indeed useful.
I applied you patch against current master.
Best,
--
Bastien
Hi Dieter,
Dieter Faulbaum writes:
> I think it would be nice if this function would have some (customizable)
> variables.
thanks for the suggestion.
Org's interface is in english. Org supports partial localization for
the exporter (see `org-export-dictionary') and for clock tables. The
43 matches
Mail list logo
