Adding a man section about how to handle plugins.
This commit is contained in:
parent
96e3ae41dd
commit
3dd006f1c1
1 changed files with 13 additions and 2 deletions
15
surf.1
15
surf.1
|
@ -142,15 +142,26 @@ Toggle the enabling of plugins on that surf instance.
|
||||||
.B F11
|
.B F11
|
||||||
Toggle fullscreen mode.
|
Toggle fullscreen mode.
|
||||||
.SH ENVIRONMENT
|
.SH ENVIRONMENT
|
||||||
.TP
|
|
||||||
.B SURF_USERAGENT
|
.B SURF_USERAGENT
|
||||||
If this variable is set upon startup, surf will use it as the useragent string
|
If this variable is set upon startup, surf will use it as the useragent string
|
||||||
.TP
|
.TP
|
||||||
.B http_proxy
|
.B http_proxy
|
||||||
If this variable is set and not empty upon startup, surf will use it as the http proxy
|
If this variable is set and not empty upon startup, surf will use it as the http proxy
|
||||||
|
.SH PLUGINS
|
||||||
|
For using plugins in surf, first determine your running architecture. Then get
|
||||||
|
the appropriate plugin for that architecture and copy it to
|
||||||
|
.BR /usr/lib/browser-plugins
|
||||||
|
or
|
||||||
|
.BR /usr/lib64/browser-plugins.
|
||||||
|
Surf should load them automatically.
|
||||||
|
.BR
|
||||||
|
If you want to use a 32bit plugin on a 64bit system,
|
||||||
|
.BR nspluginwrapper(1)
|
||||||
|
will help you.
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
.BR dmenu(1),
|
.BR dmenu(1),
|
||||||
.BR xprop(1),
|
.BR xprop(1),
|
||||||
.BR tabbed(1)
|
.BR tabbed(1),
|
||||||
|
.BR nspluginwrapper(1)
|
||||||
.SH BUGS
|
.SH BUGS
|
||||||
Please report them!
|
Please report them!
|
||||||
|
|
Loading…
Reference in a new issue