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
|
BUGS:
? - (?) add docs (texi, smgl...)
- install-menu:
? -sort= doesn't work for submenus
! -String index error, menu-1.4_0a, with "my" dwww method.
!T -give sane errormessage for missing section= in menuentry (now it coredumps, apparently).
!T -give sane errormessage for completely empty menu-entry:
> #!/usr/sbin/install-menu
> #I need menu-1!
> compat="menu-1"
-example fvwm95 menu-method doesn't have examplerc file etc.
- update-menus:
? -package($p) is not general enough!
(Joey: file(/usr/local/bin/vim))
? -translate section->section\n System Apps/System
doesn't work. You'll have to make do with
"substitute section->section\n System Apps/System"
for now.
-"\n" should be escaped as "\\n". (not as "\n", if you get what I mean)
-Should have a --menu-method option (only run that menu-method)
-should have config file to turn off "forking to background" (Joey)
- --quiet option!
-should have configurable:
output={stderr,stdio,"syslog facility.priority",...}
verbosity={quiet,normal,verbose,debug}
done:
-executable menufiles should be executed and stdout used as menufile
-old format: identifier=cppesc($title) (xemacs problem).
-doc++ menuentry doesn't work ("+" in "package"). WHY???
question mark on collum one: probably will not do that very soon
two question marks: I don't know whether to put a question mark.
+: done
!: really must be solved before next release!
(should be no "!"'s in released versions!)
T: done, still to be tested.
todo:
-menu-method.cc
-Better error reporting (always line and place, etc).
-'function xterm(title, command)="xterm -T \"" $title "\" -e " $command'
-update-menus
should output "# 1 filename"
configurable: run user's ~/.menu-method/* files.
-adstring.h
-rewrite (read line-by-line, faster, better)
-remember filenames like "# 1 filename"
-include "filename".
-menu-exec Xterm
searches for title "Xterm", and executes the "command" ascosated with it.
options:
--needs
--section
(dus via een /etc/menu-methods/menu-exec script).
notes:
Some files in /usr/lib/menu/default have disappeared. If you very much
miss one of them, copy it from menu_0.11 and stick it in /etc/menu.
Alternatively, write a (very polite) note to the maintainer of
the corresponding package. Note however, that there are at the moment
no standards that require maintainers to include menuentries in their
packages.
Idea for /etc/menu-methods/update-menus.conf:
verbosity={"quiet","normal","verbose","debug"}
output={"stdout","stderr","syslog: facility.priority","shell: playwav some.wav"}
-----------------------
buttonbars:
-----------------------
Yeah, something like a tak "buttonbarpriority=0--99" added to every
menuentry, where buttonbarpriority=0 means that this entry is absolutely
useless in the buttonbar, while buttonbarpriority=99 means that this
menuentry really should be in the buttonbar on every debian computer
(I'm assuming neighter priority will be used in reality, if this ever
is implemented).
Then the file /etc/menu-methods/menu.h could have something like
buttonbarentries=8
in it, suggesting that menu should create buttonbar entries for the
8 highest priority buttonbar entries. (These numbers can then easily
be overruled in user files in ~/.menu-methods/* or whatever).
Thinking about this, this might actually be doable -- but I don't forsee
any spare time comming up in my life soon, so it will take some time
(note that the subject of buttonbars and menus has come up quite
frequently on debian-devel).
|
