On Fri, Oct 15, 2021 at 2:54 AM Juha Manninen
wrote:
> Noticable the ability to NOT interpret [] as a set in the mask has now
>> disappeared.
>>
>
> How should a range / set [] be interpreted?
>
Ok, forget that question. I will study this more tomorrow.
Juha
--
On Thu, Oct 14, 2021 at 7:57 PM Bart via lazarus <
lazarus@lists.lazarus-ide.org> wrote:
> You have changed the existing interface for both TMask and the
> Matches(Windows)Mask(List) functions.
> TMaskOptions has been removed.
>
It can be added for compatibility.
Noticable the ability to NOT in
On Thu, Oct 14, 2021 at 12:53 AM Maxim Ganetsky via lazarus <
lazarus@lists.lazarus-ide.org> wrote:
> Don't know if it is related but just noticed that `Find in files` dialog
> now "ignores" file masks.
>
> E. g. I have the following file mask: `*.pas;*.pp;*.inc;*.lpr;*.lfm`,
> but it also finds (
On Thu, Oct 14, 2021 at 6:54 PM Bart wrote:
> This was discussed at length in february.
From the discussion in february:
Feb 24 11:22 AM
> And also define if a compatibility break is a bug in the new code or in
> the old code. In example my mask supports (there is a define to disable)
> "[z-a]"
On Wed, Oct 13, 2021 at 5:16 PM Juha Manninen via lazarus
wrote:
> Please test everybody. I will read the old posts more carefully later.
You have changed the existing interface for both TMask and the
Matches(Windows)Mask(List) functions.
TMaskOptions has been removed.
Noticable the ability to
