unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Sébastien Gendre" <seb@k-7.ch>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: GNU Emacs text editor <help-gnu-emacs@gnu.org>
Subject: Re: Using Org-mode for literate Emacs configuration with use-package
Date: Mon, 15 Jul 2024 19:13:18 +0200	[thread overview]
Message-ID: <87ttgqshn5.fsf@k-7.ch> (raw)
In-Reply-To: <CALEYq09JimcRku95BgGTj8gm0J-0-koT6aaz0oSjthDVaTJnGg@mail.gmail.com> (John Kitchin's message of "Sat, 13 Jul 2024 09:45:27 -0400")

[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]


Thank you. It's a very nice feature.

I need to look how it work with tangle.


John Kitchin <jkitchin@andrew.cmu.edu> writes:

> This sounds like a use case for noweb. Check out 
> https://orgmode.org/manual/Noweb-Reference-Syntax.html
>
> John
>
> -----------------------------------
> Professor John Kitchin (he/his)
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> https://kitchingroup.cheme.cmu.edu
> https://pointbreezepubs.gumroad.com/ pycse bookstore
>
> On Sat, Jul 13, 2024 at 8:45 AM Sébastien Gendre <seb@k-7.ch> wrote:
>
>  Hello,
>
>  I am using Org-mode and the elisp function `(org-babel-load-file)` to
>  write my Emacs configuration into an Org-mode document. It's very
>  useful to document my configuration and I can quickly do exports to HTML
>  or PDF when a friend want to know more about my configuration.
>
>  But, I have a problem.
>
>  Sometimes, I need to split a package configuration into multiple
>  sections of my Org-mode document. For example Org-mode, because I set a
>  lot of settings. By spiting my config, I can correctly document each
>  option and organize it in a more comprehensible way.
>
>  But with the elisp function `(use-package)`, I need to join each package
>  configuration into the call of `(use-package)` function. Which prevent
>  me from splitting my config into Org-mode sections.
>
>  I was thinking of writing Org-mode source block with different parts of
>  my `(use-package)` call, so I can distribute it into different section of my
>  Org-mode document. But in this case, I can no-longer evaluate my
>  `(use-package)` call directly from my Org-mode document.
>
>  Do you have any suggestion ? How do you manage this problem ?
>
>  Best regards
>
>  -------
>  Gendre Sébastien

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

  reply	other threads:[~2024-07-15 17:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 19:39 Using Org-mode for literate Emacs configuration with use-package Sébastien Gendre
2024-07-13 13:45 ` John Kitchin
2024-07-15 17:13   ` Sébastien Gendre [this message]
2024-07-13 14:36 ` Ihor Radchenko
2024-07-15 17:17   ` Sébastien Gendre
2024-07-15 17:32     ` Ihor Radchenko
2024-07-13 17:56 ` Dominic Martinez
2024-07-15 17:20   ` Sébastien Gendre
2024-07-15  9:37 ` Rens Oliemans
2024-07-15 17:20   ` Sébastien Gendre
2024-07-16  6:02 ` Björn Bidar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ttgqshn5.fsf@k-7.ch \
    --to=seb@k-7.ch \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).