emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Ihor Radchenko <yantar92@posteo.net>
To: Doerthous <doerthous@gmail.com>
Cc: emacs-orgmode@gnu.org, "Sébastien Miquel" <sebastien.miquel@posteo.eu>
Subject: Re: Support for whitespace prefix for :noweb-prefix
Date: Fri, 29 Mar 2024 09:43:36 +0000	[thread overview]
Message-ID: <875xx5fk53.fsf@localhost> (raw)
In-Reply-To: <CAC265ywaKsB4Qf_v5sZTG6aPF8kJbgh5GDyfq1L=OtcPSSOaAw@mail.gmail.com>

Doerthous <doerthous@gmail.com> writes:

>> Do you mean that you want the code to be indented according to the major
>> mode rules?
>>
>
> Why it relates to major mode,
>
> Currently, with :noweb-prefix set to yes, the above code will be expand to
> #+begin_src elisp
> (let ((a 0)
> (let ((b 1))
>    `(,a ,b))
> #+end_src
>
> ~(let (~ is the prefix of <<varable-bindings>>.
>
> I thought we can replace just the prefix in current code[1]  with
> ~(setq prefix (replace-regexp-in-string "[^ \t]" " " prefix))~ ?

I see.
So, you want a custom prefix before the expanded noweb reference lines.

I think that a more general approach could be allowing :noweb-prefix to
have a value of string that will be appended to each line on the
expansion.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

next prev parent reply	other threads:[~2024-03-29  9:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 12:44 Support for whitespace prefix for :noweb-prefix Doerthous
2024-03-28 19:25 ` Ihor Radchenko
2024-03-29  2:55   ` Doerthous
2024-03-29  9:43     ` Ihor Radchenko [this message]
2024-03-29 12:47       ` Doerthous
2024-03-29 12:51         ` Ihor Radchenko
2024-03-29 13:30           ` Doerthous
2024-03-29 13:42             ` Ihor Radchenko
2024-03-29 14:01               ` Doerthous
2024-04-03 12:27       ` Fraga, Eric
2024-04-03 13:01         ` Ihor Radchenko
2024-04-03 13:25           ` Fraga, Eric

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.orgmode.org/

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

  git send-email \
    --in-reply-to=875xx5fk53.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=doerthous@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastien.miquel@posteo.eu \
    /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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).