Menu

#34 FIND begining with blank line not correctly process

v1.0.0_CVS
closed-fixed
5
2006-01-15
2006-01-12
Pierre ROGE
No

#
#---[ FIND ]------
#

foo
#
#--

is dealt the same than :
#
#---[ FIND ]-----
#
foo
#
#---

This cause the code to not be inserted at the expected
place. Same thing for the ADD's, what is really a more
serious issue : linefeeds are not muted chars when it
goes into a string that will be outputed.

Discussion

  • Eric Faerber

    Eric Faerber - 2006-01-12

    Logged In: YES
    user_id=657440

    Empty lines in FINDs are removed. Your FIND shouldn't rely
    on whitespace to find the correct line.

    White space shouldn't be removed from the ADDs and other
    actions like that so I'll keep this open.

     
  • Eric Faerber

    Eric Faerber - 2006-01-12
    • status: open --> open-accepted
     
  • Pierre ROGE

    Pierre ROGE - 2006-01-13

    Logged In: YES
    user_id=902793

    Sorry, but empty lines prior text in the FIND means
    something (also after, but it is less sensible) : please
    propose a way to get from
    ________________________
    something to do;
    and another one;
    ________________________

    to

    ________________________
    something to do;

    // let's process something
    with our own commands;

    and another one;
    ________________________

    without having to use replace. This is particulary a severe
    issue in ie emails tpl, pure text tpls, strings that will be
    sent to browser as-is, ie overview tags, lang entries, etc.

     
  • Eric Faerber

    Eric Faerber - 2006-01-15
    • assigned_to: nobody --> wgeric
    • status: open-accepted --> closed-fixed
     
  • Eric Faerber

    Eric Faerber - 2006-01-15

    Logged In: YES
    user_id=657440

    I think you misunderstood me. The whitespace in FINDs is
    removed. So any spaces you have above or below and even in
    the middle aren't used to FIND the correct line.

    In the ADDs, and REPLACE WITH the whitespace should still be
    there. It was getting removed which I have made a commit
    which fixes the problem.

     

Log in to post a comment.

MongoDB Logo MongoDB