Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Menu name inconsistency: Lines vs. Line(s) #1916

Closed
peterflynn opened this issue Oct 22, 2012 · 11 comments
Closed

Menu name inconsistency: Lines vs. Line(s) #1916

peterflynn opened this issue Oct 22, 2012 · 11 comments

Comments

@peterflynn
Copy link
Member

We have several menu items with inconsistent names:
Delete Line(s)
Move Line(s) Up
Move Line(s) Down
Comment/Uncomment Lines

I propose renaming as following:
Delete Line
Move Line Up
Move Line Down
Line Comment/Uncomment (or: Toggle Line Comment?)
(future: Block Comment/Uncomment) (or: Toggle Block Comment?)

Other editors use the singular form for "Line" in these commands even though they all also support multiple lines. The behavior is a common enough convention that I don't think users will be thrown by the labels not explicitly mentioning multiple lines.

@peterflynn
Copy link
Member Author

@njx, any thoughts?

@jeffslofish
Copy link
Contributor

Maybe it should say:

Move Line Up

when there is one line selected, and:

Move Lines Up

when multiple lines are selected, for this and all the line commands.

@KraigWalker
Copy link
Contributor

It should probably be changed to "Move Line Up"

However this would be because, like in other editors, the item describes the unit of distance that your moving the selection up by (a line)

I wouldn't recommend changing the description based on the user's selection however, as this could lead to user confusion (even if it's a very subtle variation)

Changing the title based on what the user has selected could also wreck search-based help in the future (click Help in Mac and you'll see a nifty little search bar - I use it all the time in Photoshop 🐼 )

I guess I'll fork the latest build and see about fitting it in?

@KraigWalker
Copy link
Contributor

Actually... Looking at it more closely (in the root strings file) and then comparing it with other stuff. It Should just be "Lines"

Much more sure, solid language, and implies that it's the 'lines' you have selected. Where actually having singular could also create confusion. So normal plural is best.

@KraigWalker
Copy link
Contributor

Sorted. See issue #1928

@njx
Copy link
Contributor

njx commented Oct 24, 2012

Hi there--thanks for putting some thought (and a pull request) into this. Looking at a few other editors, though, it seems like it's standard to just use the singular here, and I don't think people will be too confused by it. I agree with you that we shouldn't change it based on the selection.

Would you be willing to modify your pull request to make these singular? Thanks!

@KraigWalker
Copy link
Contributor

Modification has now been made on issue #1928

@pthiess
Copy link
Contributor

pthiess commented Oct 29, 2012

Reviewed.

@ghost ghost assigned njx Oct 29, 2012
njx added a commit that referenced this issue Oct 30, 2012
Fix issue #1916 - Menu Name Inconsistency
@ghost ghost assigned peterflynn Nov 19, 2012
@njx
Copy link
Contributor

njx commented Nov 19, 2012

FBNC to @peterflynn (forgot to do this when I merged it a long time ago)

@peterflynn
Copy link
Member Author

Oops, fell through the cracks a second time. Definitely fixed though, so closing.

@peterflynn
Copy link
Member Author

Btw, @KraigWalker: you mentioned way earlier in this thread that you like the feature other apps have where you can search all menu comments. Fyi, there's a actually a Brackets extension for that exact functionality: https://github.com/peterflynn/brackets-commands-guide

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants