1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
|
PCURSES
-------
A curses frontend to libalpm.
FEATURES
--------
Package browsing in a curses frontend, including:
* regexp filtering and searching any package property
* customizable colorcoding
* customizable sorting
* external command execution with package list string replacements
* user defined macros and hotkeys
QUICK TUTORIAL
--------------
Navigation and queue management
-------------------------------
The package list and queue can be navigated using the up/down arrows, page
up/down, and the home and end keys. The tab key switches focus between the
package and queue lists.
Adding packages to the queue is done by pressing the right arrow key while the
package list is focused. Left arrow removes the selected package from the
queue.
Filtering
---------
Keybindings are displayed by pressing the 'h' (Help) key in pcurses.
Filtering takes the following syntax:
nd!:game
1 234
1 is a list of field specifiers. These tell pcurses which fields to search.
Field specifiers are the highlighted characters in the field names in the info
pane. In this example, this means that the Name and Description are searched
for the phrase 'game'. To keep all _non_matching packages instead, append '!'
to the field list..
2 negates the following query, i.e. a filter expression of /nd!:gnome will
return all packages NOT matching 'gnome'.
3 the character ':' separates the field specifier list from the search phrase.
If this character is not present, the entire string is interpreted as the
search phrase.
4 is the actual search phrase. If it contains only alphanumeric characters, a
simple and quick string search is used. Otherwise, it is treated as a regular
expression (which is a bit slower). The search is case INSENSITIVE.
1, 2 and 3 are OPTIONAL.
These searches can be chained. This means that a search for 'n:^a', followed by
'b:2010' will show all packages beginning with the letter 'a' and having a
build date in the year 2010.
Previous filters are cleared by pressing the 'c' key.
Pressing the up and down keys while in input mode will scroll through all
previous history.
Sorting and colorcoding
-----------------------
Colorcoding and sorting use the same syntax as filtering, but only accept a
single field specifier.
Command execution
-----------------
Command execution can be entered by pressing the '!' key. The token '%p' will
be replaced by the current contents of the package queue. For example, with a
current package selection of pcurses and pacman,
!sudo pacman -S '%p'
will be expanded to 'sudo pacman -S pcurses pacman' and executed with 'bash'.
A few useful commands could be
!pacman -Sy
!sudo pacman -S %p
!sudo pacman -Rs %p
Caution: package infos are not reloaded automatically. After db changes,
trigger a manual reload by pressing 'r'.
Control commands
----------------
Control commands may be used to trigger keyboard shortcut actions such as
'scroll up' from macros. Available commands are:
scroll_up, scroll_down, scroll_home, scroll_end, scroll_pageup,scroll_pagedown,
switch_focus, queue_push, queue_pop, queue_clear, help, quit, reload,
filter_clear.
Macros
------
Macros are defined in /etc/pcurses.conf using the syntax 'macroname=command'.
Macros can be chained by separating them with a comma. A few examples:
sortbyname=.n
colorbyrepo=;r
filterupdates=/d:update available
chainedmacro=@sortbyname,colorbyrepo,filterupdates
If defined, the macro named 'startup' will be executed on each application
start. Hotkeys can be defined by creating macros named '1', '2', [...], and are
triggered by pressing the corresponding key in pcurses.
All macros can be executed in pcurses by pressing the '@' key and entering the
macro name.
FURTHER READING
---------------
For some of the things I've been thinking about or am planning on doing, read
the CONCEPTS file.
BUGS
----
Please report all bugs and feature requests to
https://github.com/schuay/pcurses/issues
CONTACT
-------
Visit the pcurses github page at https://github.com/schuay/pcurses or write me
a mail at jakob.gruber@gmail.com
|