git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] gitk: Rename "next" and "prev" buttons to "older" and "newer".

From
Marc Branchaud <marcnarc@xiplink.com>
Date
Oct 8, 2013, 20:49 UTC
Message-ID
<1381265361-10147-1-git-send-email-marcnarc@xiplink.com>
In-Reply-To
<525445FB.6000806@xiplink.com>

Users often find that "next" and "prev" do the opposite of what they expect. For example, "next" moves to the next match down the list, but that is almost always backwards in time. Renaming "next" to "older" and "prev" to "newer" makes it clear where the buttons will take the user. ---

(Apologies to Lucas and Paul -- my previous patch email didn't include the git list.)

 gitk | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gitk b/gitk
index 5cd00d8..e610010 100755
--- a/gitk
+++ b/gitk
@@ -2244,8 +2244,8 @@ proc makewindow {} {
 
     # build up the bottom bar of upper window
     ${NS}::label .tf.lbar.flabel -text "[mc "Find"] "
-    ${NS}::button .tf.lbar.fnext -text [mc "next"] -command {dofind 1 1}
-    ${NS}::button .tf.lbar.fprev -text [mc "prev"] -command {dofind -1 1}
+    ${NS}::button .tf.lbar.fnext -text [mc "older"] -command {dofind 1 1}
+    ${NS}::button .tf.lbar.fprev -text [mc "newer"] -command {dofind -1 1}
     ${NS}::label .tf.lbar.flab2 -text " [mc "commit"] "
     pack .tf.lbar.flabel .tf.lbar.fnext .tf.lbar.fprev .tf.lbar.flab2 \
 	-side left -fill y
-- 
1.8.4.dirty
Previous: Junio C Hamano
Message 12 of 12 in “gitk next/prev buttons”
  1. Lucas Sandery [three am design]Oct 1, 2013
  2. Lucas SanderyOct 2, 2013
  3. Marc BranchaudOct 8, 2013
  4. Jonathan NiederOct 8, 2013
  5. Marc BranchaudOct 8, 2013
  6. [PATCHv2] gitk: Replace "next" and "prev" buttons with down and up arrows.Marc Branchaud, Dec 18, 2013
  7. Marc BranchaudJan 21, 2014
  8. Paul MackerrasJan 22, 2014
  9. Junio C HamanoJan 22, 2014
  10. Paul MackerrasJan 23, 2014
  11. Junio C HamanoJan 23, 2014
  12. gitk: Rename "next" and "prev" buttons to "older" and "newer".Marc Branchaud, Oct 8, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.