Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option for delete key to delete last character instead of entire entry #177

Closed
sinewave opened this issue Apr 12, 2011 · 11 comments · Fixed by #2249
Closed

Option for delete key to delete last character instead of entire entry #177

sinewave opened this issue Apr 12, 2011 · 11 comments · Fixed by #2249

Comments

@sinewave
Copy link

@sinewave sinewave commented Apr 12, 2011

No description provided.

@HenningJ
Copy link
Contributor

@HenningJ HenningJ commented Apr 27, 2011

Link to the thread on the mailinglist.

@sinewave
Copy link
Author

@sinewave sinewave commented Feb 9, 2013

Bump :)

Any thoughts on this ever making its way into QS? I still get frustrated by this on a daily basis. You would think after two years my typing would've improved :)

This is also atypical behavior for the delete key and most other launchers use the standard behavior which i think is more forgiving to new user as well.

@pjrobertson
Copy link
Member

@pjrobertson pjrobertson commented Feb 17, 2013

Alright... :)
#1395

@sinewave
Copy link
Author

@sinewave sinewave commented Feb 17, 2013

Woohoo, thx!!!

On Sun, Feb 17, 2013 at 11:22 AM, Patrick Robertson
notifications@github.com wrote:

Alright... :)

#1395

Reply to this email directly or view it on GitHub:
#177 (comment)

@sinewave
Copy link
Author

@sinewave sinewave commented Jun 17, 2013

Hi, is this feature avail in QS? Couldn't find it anywhere in the settings.

@pjrobertson
Copy link
Member

@pjrobertson pjrobertson commented Jun 17, 2013

The changes to fix this are currently in review. See #1395. It's just waiting for another dev (maybe @skufer... :D) to take a look at it and approve it.

@sinewave
Copy link
Author

@sinewave sinewave commented Jun 17, 2013

Got it. @skurfer, any chance this can make it into the next release? It seems like an easy fix and has been marinating for 4 months :)

On Mon, Jun 17, 2013 at 4:09 AM, Patrick Robertson
notifications@github.com wrote:

The changes to fix this are currently in review. See #1395. It's just waiting for another dev (maybe @skufer... :D) to take a look at it and approve it.

Reply to this email directly or view it on GitHub:
#177 (comment)

@skurfer
Copy link
Member

@skurfer skurfer commented Jun 18, 2013

It'll get looked at before the next release. I can at least promise that. 😃

sinewave pushed a commit to sinewave/Quicksilver that referenced this issue Jun 27, 2013
…default deleteRemovesLastCharacter (quicksilver#177)

- also resets the search results as keys are deleted including when there are no search characters entered (quicksilver#252)
@skurfer
Copy link
Member

@skurfer skurfer commented Jul 27, 2016

As I said on the pull request’s discussion, I’ll go along with making this the default, but I have to say I really, really don’t get it. I mean, you’re replacing this:

  1. Typo
  2. Type abbreviation again (most likely effortless due to muscle memory)

with this:

  1. Typo
  2. Press ⌫ enough times to remove the mistake
  3. What did I mean to type?
  4. What is left undeleted?
  5. What is the difference between those?
  6. Type the difference (for which you have no muscle memory)

@pjrobertson
Copy link
Member

@pjrobertson pjrobertson commented Jul 27, 2016

Thanks for chiming in @hmelman over on the pull request.

Rob - what's your argument for every other search field (including Spotlight and I'm assuming other app launchers) using 'delete removes a single character'?

What you outlined in your second set of steps is what I have to do everywhere (URL bar, Google, Spotlight, Contacts...).
I think you have a case arguing that it might not be best for short strings where you might be typing abbreviations, but I think deleting the whole string and starting from scratch is more of a 'power user' thing, and is why it should still be an option, just not the default

@skurfer
Copy link
Member

@skurfer skurfer commented Jul 28, 2016

Rob - what's your argument for every other search field (including Spotlight and I'm assuming other app launchers) using 'delete removes a single character’?

Those are text boxes, just like Quicksilver is in text-entry mode. The behavior makes sense in those contexts because you’re “editing” text.

You can also see what you’re working on, where in QS you’d have to parse out which characters are highlighted in the first pane, and they could jump around as you add/remove characters if the result changed. It just never felt like “entering text” to me.

I think you have a case arguing that it might not be best for short strings where you might be typing abbreviations

What else would you be typing when searching with Quicksilver? 😃

but I think deleting the whole string and starting from scratch is more of a 'power user' thing, and is why it should still be an option, just not the default

Maybe it would help to know that I rarely need to type more than 2 characters to find what I’m after, and 5 characters is like a crazy edge case that annoys me. So losing all of it and starting over is pretty low cost.

Is that “power user” behavior? I thought that was the whole point of this app!

Anyway, no one needs to convince anyone else here. I’ve already said I’ll go along with the new default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants