Re: How should we handle neg*space insets in find?

Am Sat, 22 Jul 2023 19:36:06 -0400 schrieb Scott Kostyshak : > On Sat, Jul 22, 2023 at 05:30:16PM +0200, Kornel Benko wrote: > > Am Sat, 22 Jul 2023 06:54:37 -0400 > > schrieb Scott Kostyshak : > > > > > On Sat, Jul 22, 2023 at 11:57:58AM +0200, Kornel Benko wrote: > > > > > > > > * Should

Re: How should we handle neg*space insets in find?

On Sat, Jul 22, 2023 at 05:30:16PM +0200, Kornel Benko wrote: > Am Sat, 22 Jul 2023 06:54:37 -0400 > schrieb Scott Kostyshak : > > > On Sat, Jul 22, 2023 at 11:57:58AM +0200, Kornel Benko wrote: > > > > > > * Should we discard them > > > * Handle like white space > > > > > > If using in findadv

Re: How should we handle neg*space insets in find?

Am Sat, 22 Jul 2023 06:54:37 -0400 schrieb Scott Kostyshak : > On Sat, Jul 22, 2023 at 11:57:58AM +0200, Kornel Benko wrote: > > > > * Should we discard them > > * Handle like white space > > > > If using in findadv with selected 'Adhere to search string formatting of' > > they are treated as

Re: How should we handle neg*space insets in find?

On Sat, Jul 22, 2023 at 11:57:58AM +0200, Kornel Benko wrote: > > * Should we discard them > * Handle like white space > > If using in findadv with selected 'Adhere to search string formatting of' > they are treated as ordinary non-word chars. > Without this option, the are discarded. > > I am

How should we handle neg*space insets in find?

* Should we discard them * Handle like white space If using in findadv with selected 'Adhere to search string formatting of' they are treated as ordinary non-word chars. Without this option, the are discarded. I am unsure, how to proceed. Using them as white spaces disables the specific search