The community Taskforce initiative has now come to a close.
Thanks to everyone who made thoughtful and genuine contributions to the website.
All submissions will be kept publically available for the forseeable future for reference purposes.

This website is part of the community Taskforce initiative

Submission details

36 +38/-2 votes

Moving cursor to the left while renaming exits renaming mode

Submitted by dmnd on September 8, 2008 to Annoyance, Usability

With Finder in list mode, select a file and press return to enter rename mode. The cursor is placed at the end of the file name. Edit the end of the file name so that the entire file name is not selected. Now press the left arrow to move the cursor to the front of the file name. If you hold down the left arrow, Finder exits rename mode and closes all folders up until the root of the Finder window. This is incredibly annoying when trying to rename lots of files.

Only exit rename mode when the user presses return or escape.

High

Low

Not fixed

Discussion (8 comments)

abitgone wrote on September 8, 2008, 8:50am

Can't replicate that on my setup (10.5.4 9E17) in any of Finder's views.

ion wrote on September 8, 2008, 12:07pm

It's a very old and annoying bug and i can reproduce it on 5 different macs.

polycat33 wrote on September 8, 2008, 11:00pm

I was able to replicate it on mine, 10.5.4. The bug is specific to list view, according to the author.

Grey_Podder wrote on September 9, 2008, 9:07pm

I was also able to replicate it; I'm running 10.5.4 and could only replicate it in List View, as with polycat33.

alistairmcmillan wrote on October 5, 2008, 5:29pm

The important part is to hold the left arrow down to move the cursor (aka text insertion point). If you just tap it to move left a character at a time you won't see the bug.

Kuro-to wrote on December 20, 2008, 4:21am

Seems to be fixed in 10.5.6

jay314 wrote on December 29, 2008, 8:12pm

I was able to reproduce this easily in 10.5.5, especially when cover flow was on in the Finder window.

Kuro-to is correct -- After the update to 10.5.6, this seems to be fixed!

connerat wrote on June 13, 2009, 3:25pm

I can replicate this problem on a MacBook Pro 2.8 GHZ Intel Core Duo running the latest software updates. Mac OS X 10.5.7 (9J61). It happened in prior versions too, going back several iterations. It never happened on my MacBook Pro, 15-inch, 2.33GHz, but it's obviously a software bug. Still, I can't figure out what's different about my current configuration. This bug drives me crazy.

You might also be interested in...