mirror of https://github.com/rkd77/elinks.git synced 2024-06-19 00:05:36 +00:00
Commit Graph

8 Commits

Author SHA1 Message Date
Witold Filipczyk
7ea7cacade [.config] Read/write configuration from ~/.config/elinks . Refs #199
Note, configs and other files from ~/.elinks/ are not moved
to ~/.config/elinks/ automatically. You must do it yourself.

ELINKS_CONFDIR and HOME_ETC also are no longer supported.
2022-12-26 17:48:55 +01:00
Kalle Olavi Niemitalo
3caec64c51 doc: Ctrl-Alt- keystrokes can be bound too. 2007-02-11 20:55:58 +02:00
Jonas Fonseca
a892c84601 Make it possible to build all-docs when $(builddir) != $(srcdir) 2006-01-16 00:21:05 +01:00
Jonas Fonseca
01b9ba0983 Fix keymap-%.txt building; move FIXME about prefixes to elinkskeys.5.txt 2006-01-14 19:24:46 +01:00
Jonas Fonseca
1d35855d7d Minor fixes 2006-01-12 11:08:18 +01:00
Jonas Fonseca
0e57735284 Add description header to be used for the man hack 2006-01-12 10:30:25 +01:00
Jonas Fonseca
aa7d65fb79 Make elinks.conf(5) also be build from .txt files
This simplifies help2doc since it now just have to do one single thing with
output of either --config-help or --long-help. The new manpage is not as
fancy wrt. indentation and sub titles but it is more uniform and we get a
HTML version.

Generate options-{config,command}.txt with help2doc. Only conditionally
check for API header files, to speed up execusion.
2006-01-12 08:33:50 +01:00
Jonas Fonseca
ba6221c6f6 Redo the whole doc/ build thing
You can now use: make {all-docs,pdf,html,man,api,update-man}
     instead of: make {all-docs,pdf-docs,html-docs,man-docs}

Away is building into separate dirs. This makes make able to actually get
dependencies right, since there are now a collection of 'common' build
rules, some of which have even been moved to use the cmd infrastructure.

To update the man pages there is a new update-man rule. It builds the
manual pages and copies them to their proper place under man/ while doing
the final preformatting.

As good thing is that the (two) man pages are moved to .txt files and
include the generated content.

The API building thing is also refined. It builds into api/ and builds it's
list of files dynamically by searching throught the .h files in the src/
directory. Documented header files must contain a comment like this:

	/* API Doc :: <api-name> */

where <api-name> is the name used for the file under api/, for example
2006-01-11 11:02:43 +01:00