Changes between Version 3 and Version 9 of Ticket #414


Ignore:
Timestamp:
08/07/24 04:38:03 (12 months ago)
Author:
Olly Betts
Comment:

Replying to Olly Betts:

~foo:"abc def" [...] should probably do a multi-word synonym expansion.

I actually have a patch which implements this part so we can easily do this part for 1.5.0.

Applied in 8c723ec78753e9ae701261eb388ef4b7855aff5e. The other case probably isn't for 1.5.0.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #414

    • Property Status new → assigned
    • Property Milestone 1.3.x → 2.0.0

  • Ticket #414 – Description

    v3 v9  
    11There are quite a few cases which we probably don't handle as well as we could (sometimes it's not totally clear what the behaviour should be), so let's make a list here and see if we can find resolutions, or decide the current behaviour is fine.
    22
    3 With FLAG_SYNONYM these cause reparsing so parse as {{{foo abc def}}} (we just ignore ~ unless the next character is a word character, so without the "foo:" prefix, ~ is just ignored):
     3With FLAG_SYNONYM this causes reparsing so parse as {{{foo abc def}}} (we just ignore ~ unless the next character is a word character, so without the "foo:" prefix, ~ is just ignored):
    44
    55{{{
    66~foo:(abc def)
    7 ~foo:"abc def"
    87}}}
    98
    10 Assuming "foo" is set as a non-boolean prefix, the first should probably parse as synonyms for the two terms, so the same as:
     9Assuming "foo" is set as a non-boolean prefix, it should probably parse as synonyms for the two terms, so the same as:
    1110
    1211{{{
    1312~foo:abc ~foo:def
    1413}}}
    15 
    16 And the second should probably do a multi-word synonym expansion.