Hi Bastien,
2014ko urriak 12an, Bastien-ek idatzi zuen:
>
> Hi Aaron,
>
> Aaron Ecay writes:
>
>> FWIW, I also think the present behavior is too magical, and am in favor
>> of the proposed change.
>
> Feel free to push this change. Thanks!
AFAIK this was just an idea and a patch never mater
Hi Aaron,
Aaron Ecay writes:
> FWIW, I also think the present behavior is too magical, and am in favor
> of the proposed change.
Feel free to push this change. Thanks!
--
Bastien
Hello,
2014ko abuztuak 18an, Sebastien Vauban-ek idatzi zuen:
>
> Pierre-Henry FRÖHRING wrote:
>> I would like to back this proposition with our use case :
>>
>> #+BEGIN_SRC js
>> REACTIVE_STATE = TYPE_BUILDER(
>> <>
>> , "reactive_state"
>> , <>
>> )
>> #+END_SRC
>>
>> Where `<>` is expanded a
Pierre-Henry FRÖHRING wrote:
> I would like to back this proposition with our use case :
>
> #+BEGIN_SRC js
> REACTIVE_STATE = TYPE_BUILDER(
> <>
> , "reactive_state"
> , <>
> )
> #+END_SRC
>
> Where `<>` is expanded as e
I would like to back this proposition with our use case :
#+BEGIN_SRC js
REACTIVE_STATE = TYPE_BUILDER(
<>
, "reactive_state"
, <>
)
#+END_SRC
Where `<>` is expanded as expected,
and `, <>` is not, leading to `, ` pref
Hi Michael,
Pontus Michael writes:
> You make a valid point that change of this nature will inevitably
> break existing code that has been taking advantage of this
> functionality. From my point of view this is an argument in favor
> of having this issue addressed as soon as possible.
I'll wai
Pontus Michael wrote:
> I recommend to introduce a change that will replace the inserted prefix
> with whitespace of equal length. If it was the case then provided
> example would produce the following code after expansion:
>
> #+begin_src emacs-lisp
> (concat "foo"
> "bar")
> #+end_src
>
>
Hello, Charles.
Thank you for your reply.
I appreciate your suggestion, however the example which I used is not a
limiting factor which I seek help in overcoming. Instead I'm trying to
address a potential design flaw.
You make a valid point that change of this nature will inevitably break
existi
Pontus Michael gmail.com> writes:
>
> I would like to propose a change to the behavior of noweb expansion in
> relation to prefix handling.
[snip]
> I recommend to introduce a change that will replace the inserted prefix
> with whitespace of equal length.
[snip]
The behavior you desire ca
I would like to propose a change to the behavior of noweb expansion in
relation to prefix handling. Current behavior intends to insert the text
preceding noweb reference before every successive line of referenced
code.
For instance the expansion of following source block:
#+begin_src emacs-lisp :
10 matches
Mail list logo
