newsticker: use M-j/M-k to avoid confusion
This commit is contained in:
parent
d65bdedb52
commit
dc2f7922df
|
@ -71,17 +71,21 @@
|
||||||
;; move
|
;; move
|
||||||
"[[" 'newsticker-treeview-prev-feed
|
"[[" 'newsticker-treeview-prev-feed
|
||||||
"]]" 'newsticker-treeview-next-feed
|
"]]" 'newsticker-treeview-next-feed
|
||||||
(kbd "C-j") 'newsticker-treeview-next-item
|
;; The items in Newsticker List buffer has a particular keymap by text
|
||||||
(kbd "C-k") 'newsticker-treeview-prev-item
|
;; property, where CR (C-m) and LF (C-j) are bound to
|
||||||
|
;; `newsticker-treeview-show-item'. According to the keymap precedence page,
|
||||||
|
;; the text property based keymap has a higher priority.
|
||||||
|
;;
|
||||||
|
;; Eval (info "(elisp)Searching Keymaps") if you have interests.
|
||||||
|
;;
|
||||||
|
;; Use M-j/M-k instead.
|
||||||
|
(kbd "M-j") 'newsticker-treeview-next-item
|
||||||
|
(kbd "M-k") 'newsticker-treeview-prev-item
|
||||||
"gj" 'newsticker-treeview-next-new-or-immortal-item
|
"gj" 'newsticker-treeview-next-new-or-immortal-item
|
||||||
"gk" 'newsticker-treeview-prev-new-or-immortal-item
|
"gk" 'newsticker-treeview-prev-new-or-immortal-item
|
||||||
(kbd "SPC") 'newsticker-treeview-next-page
|
(kbd "SPC") 'newsticker-treeview-next-page
|
||||||
"J" 'newsticker-treeview-jump
|
"J" 'newsticker-treeview-jump
|
||||||
|
|
||||||
;; If it's not defined, C-j will implicitly converts to RET that shadows the
|
|
||||||
;; C-j binding.
|
|
||||||
(kbd "RET") 'newsticker-treeview-show-item
|
|
||||||
|
|
||||||
;; mark
|
;; mark
|
||||||
"o" 'newsticker-treeview-mark-item-old
|
"o" 'newsticker-treeview-mark-item-old
|
||||||
"O" 'newsticker-treeview-mark-list-items-old
|
"O" 'newsticker-treeview-mark-list-items-old
|
||||||
|
|
Loading…
Reference in New Issue