Re: [FR] :noweb-wrap header arg

2024-05-11 Thread Amy Grinn
Ihor Radchenko writes: > Amy Grinn writes: > >> First of all, I would like to change (defalias) the function name >> org-babel-noweb-wrap to org-babel-noweb-make-regexp. I think this in >> more in line with other functions which create regular expressions. > >

Re: Update contact info

2024-05-11 Thread Amy Grinn
Bastien Guerry writes: > Ihor Radchenko writes: > >> Bastien, may you check which name is used in the FSF records? > > I've taken this offlist. The name in the FSF records should be correct now. -- Best, Amy

Re: [FR] :noweb-wrap header arg

2024-04-11 Thread Amy Grinn
Ihor Radchenko writes: > Amy Grinn writes: > >> +(insert raw) >> +(goto-char (point-min)) >> +(while (< (point) (point-max)) >> + (unless (looking-at " *\"\\([^\"]+\\)\" *") >> +(looki

Update contact info

2024-04-08 Thread Amy Grinn
I would like to update my old contact info in this project. Best, Amy diff --git a/.mailmap b/.mailmap new file mode 100644 index 0..0110f4597 --- /dev/null +++ b/.mailmap @@ -0,0 +1 @@ +Amy Grinn Tyler Grinn

[FR] :noweb-wrap header arg

2024-04-08 Thread Amy Grinn
ot determine which noweb syntax is being used for any given source file, if :noweb-wrap was specified in the original Org file. """ Best, Amy >From 1dc8aebcc45447d3b5b38ea3c7700ae2b2686c9d Mon Sep 17 00:00:00 2001 From: Amy Grinn Date: Mon, 8 Apr 2024 09:05:02 -0400 Subject: [P

Re: noweb-start and noweb-end header args

2024-03-07 Thread Amy Grinn
Ihor Radchenko writes: > Amy Grinn writes: > >> Here is a simple way to implement this feature. > > Since you are adding a new feature, it should have (1) test coverage; > (2) be documented in the manual; (3) be announced in etc/ORG-NEWS. Thank you for the tips, will do!

Re: noweb-start and noweb-end header args

2024-03-07 Thread Amy Grinn
Ihor Radchenko writes: > :noweb yes <<< >>> is actually backwards-incompatible. Consider > third-party code that makes assumptions about possible values of > :noweb > header argument. If third-party code does a check like > (equal noweb-value "yes"), the new syntax can break such code. I kinda

Re: noweb-start and noweb-end header args

2024-03-06 Thread Amy Grinn
Amy Grinn writes: > Ihor Radchenko writes: > >> Amy Grinn writes: >> >>> I would like to add support for setting 'org-babel-noweb-wrap-start and >>> 'org-babel-noweb-wrap-end for each src block individually >> >> May you please explain the use ca

Re: noweb-start and noweb-end header args

2024-03-06 Thread Amy Grinn
Ihor Radchenko writes: > Amy Grinn writes: > >> How much does org mode modify the fontification for an indirect buffer? >> Without having looked into it, I assume not much or at all. >> ... I think >> that approach could be more complex, especially when dealing wi

Re: noweb-start and noweb-end header args

2024-03-06 Thread Amy Grinn
Ihor Radchenko writes: > Amy Grinn writes: > >>>> #+name: firewall >>>> #+begin_src sh :noweb yes :noweb-start <<< :noweb-end >>> >>> >>> May you please explain the use case when changing the default values >>> is use

Re: noweb-start and noweb-end header args

2024-03-06 Thread Amy Grinn
Ihor Radchenko writes: > Amy Grinn writes: > >> I would like to add support for setting 'org-babel-noweb-wrap-start and >> 'org-babel-noweb-wrap-end for each src block individually using the >> header args :noweb-start and :noweb-end: >> ... >> #+name: fi

noweb-start and noweb-end header args

2024-03-05 Thread Amy Grinn
I would like to add support for setting 'org-babel-noweb-wrap-start and 'org-babel-noweb-wrap-end for each src block individually using the header args :noweb-start and :noweb-end: #+name: firewall-safe-mode #+begin_src sh echo "Firewall is now in safe mode." #+end_src #+name: firewall