Case sensitivity

[rnc]

If I have a list with e.g. Current and current listing on Current should not return current

[Thor77]

Why do you think so?
I think most people expect a search to be case-insensitive and I'm for keeping it like that.
@wayneashleyberry what to you think?

[wayneashleyberry]

I far prefer case insensitivity, @rnc is there a specific reason you need an exact match?

[rnc]

@wayneashleyberry I understand people have differing opinions on this. I am simply used to case sensitivity. If I recall (its a while since I've tried it) I think part of the problem was I had added a list entitled "Current" via the app/web api but there was some inconsistencies when attempting to list/modify it via the CLI. I wonder if a configuration option would help here?

[Thor77]

Can you elaborate on your specific problem?
I don't really see the problem, because when adding a task on a specific list via wunderline, the list-name is converted to lowercase and listing of tasks on a specific list is currently not supported.

[rnc]

@Thor77 @wayneashleyberry As having multiple lists differing only in case is such a edge-case I would suggest just closing this?

[wayneashleyberry]

I actually wouldn't mind implementing this in a similar manner as smartcase in vim.

When 'ignorecase' and 'smartcase' are both on, if a pattern contains an uppercase letter, it is case sensitive, otherwise, it is not. For example, /The would find only "The", while /the would find "the" or "The" etc. (http://vim.wikia.com/wiki/Searching)

So by default search's are case insensitive, unless the search term contains an uppercase character. How's that sound @rnc?

[rnc]

@wayneashleyberry +1

[rnc]

@Thor77 I wonder if similar should apply to the search facility. From what I can see currently it is also case insensitive but is also using a fuzzy matching algorithm which means searching for e.g. RCM will return
"Update RCM"
and
"Handle releasing in config and new document"

The latter is a bit unintuitive. Either an explicit regexp of ability to quote would be useful. (Perhaps this is better as a separate issue?)

[Thor77]

Yeah, please open an seperate issue for the search-command. We should extract this functionality into an own function then to provide a consistent experience throughout the application.