├── .gitignore
├── .travis.yml
├── CHANGELOG.md
├── COPYING
├── Doxyfile
├── Makefile
├── README.md
├── example.c
├── ringfs.c
├── ringfs.h
└── tests
├── flashsim.c
├── flashsim.h
├── fuzzer.py
├── pyflashsim.py
├── pyringfs.py
├── sharedlibrary.py
└── tests.c
/.gitignore:
--------------------------------------------------------------------------------
1 | *.o
2 | *.so
3 | *.pyc
4 | *.pyo
5 | *~
6 | *.bak
7 | *.diff
8 | .*.swp
9 | ringfs
10 | tests/tests
11 | example
12 | tags
13 | html/
14 | *.sim
15 |
--------------------------------------------------------------------------------
/.travis.yml:
--------------------------------------------------------------------------------
1 | language: c
2 | compiler:
3 | - gcc
4 | - clang
5 | before_install:
6 | - if [ "$CC" == "gcc" ]; then
7 | sudo add-apt-repository -y ppa:ubuntu-toolchain-r/test;
8 | sudo apt-get update -qq;
9 | fi
10 | install:
11 | - if [ "$CC" == "gcc" ]; then
12 | sudo apt-get install -qq gcc-4.8;
13 | export CC="gcc-4.8";
14 | fi
15 | - sudo apt-get install check
16 | script: make test
17 | notifications:
18 | email:
19 | on_success: change
20 | on_failure: change
21 | hipchat:
22 | format: html
23 | template:
24 | - "%{repository}#%{build_number}: %{commit}
on %{branch}
by %{author} has %{result}."
25 | rooms:
26 | secure: YCtUInhx74toFNey9E4V/5tbR1kGZqIBmn16l+Gmz5U+xba52pRPunegAqXZ1Ew8zA5+ppJb/BNugCiNtRWN/tZh/Er/hTV4zRwXJre3+gbHjzTS8QnALrl7fWPFKe5C1QMHdRHv6crBQ471YZLxUO4Imu5bvTW5BFOnJhVEuuI=
27 |
--------------------------------------------------------------------------------
/CHANGELOG.md:
--------------------------------------------------------------------------------
1 | # RingFS changelog
2 |
3 | ## 0.2.0, released 2014/05/07
4 |
5 | * BUGFIX: used_seen was not updated in ringfs_scan(), causing corruption.
6 | * Improved tests.
7 | * Basic Python bindings.
8 | * Basic fuzzing support.
9 |
10 | ## 0.1.0, released 2014/04/28
11 |
12 | First "full" release. Entire API is implemented but subject to change.
13 | Tests cover most common cases.
14 |
--------------------------------------------------------------------------------
/COPYING:
--------------------------------------------------------------------------------
1 | DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
2 | Version 2, December 2004
3 |
4 | Copyright (C) 2004 Sam Hocevar
5 |
6 | Everyone is permitted to copy and distribute verbatim or modified
7 | copies of this license document, and changing it is allowed as long
8 | as the name is changed.
9 |
10 | DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
11 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
12 |
13 | 0. You just DO WHAT THE FUCK YOU WANT TO.
14 |
--------------------------------------------------------------------------------
/Doxyfile:
--------------------------------------------------------------------------------
1 | # Copyright © 2014 Kosma Moczek
2 | # This program is free software. It comes without any warranty, to the extent
3 | # permitted by applicable law. You can redistribute it and/or modify it under
4 | # the terms of the Do What The Fuck You Want To Public License, Version 2, as
5 | # published by Sam Hocevar. See the COPYING file for more details.
6 |
7 | # Doxyfile 1.8.6
8 |
9 | # This file describes the settings to be used by the documentation system
10 | # doxygen (www.doxygen.org) for a project.
11 | #
12 | # All text after a double hash (##) is considered a comment and is placed in
13 | # front of the TAG it is preceding.
14 | #
15 | # All text after a single hash (#) is considered a comment and will be ignored.
16 | # The format is:
17 | # TAG = value [value, ...]
18 | # For lists, items can also be appended using:
19 | # TAG += value [value, ...]
20 | # Values that contain spaces should be placed between quotes (\" \").
21 |
22 | #---------------------------------------------------------------------------
23 | # Project related configuration options
24 | #---------------------------------------------------------------------------
25 |
26 | # This tag specifies the encoding used for all characters in the config file
27 | # that follow. The default is UTF-8 which is also the encoding used for all text
28 | # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
29 | # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
30 | # for the list of possible encodings.
31 | # The default value is: UTF-8.
32 |
33 | DOXYFILE_ENCODING = UTF-8
34 |
35 | # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
36 | # double-quotes, unless you are using Doxywizard) that should identify the
37 | # project for which the documentation is generated. This name is used in the
38 | # title of most generated pages and in a few other places.
39 | # The default value is: My Project.
40 |
41 | PROJECT_NAME = "ringfs"
42 |
43 | # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
44 | # could be handy for archiving the generated documentation or if some version
45 | # control system is used.
46 |
47 | PROJECT_NUMBER =
48 |
49 | # Using the PROJECT_BRIEF tag one can provide an optional one line description
50 | # for a project that appears at the top of each page and should give viewer a
51 | # quick idea about the purpose of the project. Keep the description short.
52 |
53 | PROJECT_BRIEF =
54 |
55 | # With the PROJECT_LOGO tag one can specify an logo or icon that is included in
56 | # the documentation. The maximum height of the logo should not exceed 55 pixels
57 | # and the maximum width should not exceed 200 pixels. Doxygen will copy the logo
58 | # to the output directory.
59 |
60 | PROJECT_LOGO =
61 |
62 | # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
63 | # into which the generated documentation will be written. If a relative path is
64 | # entered, it will be relative to the location where doxygen was started. If
65 | # left blank the current directory will be used.
66 |
67 | OUTPUT_DIRECTORY =
68 |
69 | # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub-
70 | # directories (in 2 levels) under the output directory of each output format and
71 | # will distribute the generated files over these directories. Enabling this
72 | # option can be useful when feeding doxygen a huge amount of source files, where
73 | # putting all generated files in the same directory would otherwise causes
74 | # performance problems for the file system.
75 | # The default value is: NO.
76 |
77 | CREATE_SUBDIRS = NO
78 |
79 | # The OUTPUT_LANGUAGE tag is used to specify the language in which all
80 | # documentation generated by doxygen is written. Doxygen will use this
81 | # information to generate all constant output in the proper language.
82 | # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
83 | # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
84 | # Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian,
85 | # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
86 | # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
87 | # Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian,
88 | # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
89 | # Ukrainian and Vietnamese.
90 | # The default value is: English.
91 |
92 | OUTPUT_LANGUAGE = English
93 |
94 | # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member
95 | # descriptions after the members that are listed in the file and class
96 | # documentation (similar to Javadoc). Set to NO to disable this.
97 | # The default value is: YES.
98 |
99 | BRIEF_MEMBER_DESC = YES
100 |
101 | # If the REPEAT_BRIEF tag is set to YES doxygen will prepend the brief
102 | # description of a member or function before the detailed description
103 | #
104 | # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
105 | # brief descriptions will be completely suppressed.
106 | # The default value is: YES.
107 |
108 | REPEAT_BRIEF = YES
109 |
110 | # This tag implements a quasi-intelligent brief description abbreviator that is
111 | # used to form the text in various listings. Each string in this list, if found
112 | # as the leading text of the brief description, will be stripped from the text
113 | # and the result, after processing the whole list, is used as the annotated
114 | # text. Otherwise, the brief description is used as-is. If left blank, the
115 | # following values are used ($name is automatically replaced with the name of
116 | # the entity):The $name class, The $name widget, The $name file, is, provides,
117 | # specifies, contains, represents, a, an and the.
118 |
119 | ABBREVIATE_BRIEF =
120 |
121 | # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
122 | # doxygen will generate a detailed section even if there is only a brief
123 | # description.
124 | # The default value is: NO.
125 |
126 | ALWAYS_DETAILED_SEC = NO
127 |
128 | # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
129 | # inherited members of a class in the documentation of that class as if those
130 | # members were ordinary class members. Constructors, destructors and assignment
131 | # operators of the base classes will not be shown.
132 | # The default value is: NO.
133 |
134 | INLINE_INHERITED_MEMB = NO
135 |
136 | # If the FULL_PATH_NAMES tag is set to YES doxygen will prepend the full path
137 | # before files name in the file list and in the header files. If set to NO the
138 | # shortest path that makes the file name unique will be used
139 | # The default value is: YES.
140 |
141 | FULL_PATH_NAMES = YES
142 |
143 | # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
144 | # Stripping is only done if one of the specified strings matches the left-hand
145 | # part of the path. The tag can be used to show relative paths in the file list.
146 | # If left blank the directory from which doxygen is run is used as the path to
147 | # strip.
148 | #
149 | # Note that you can specify absolute paths here, but also relative paths, which
150 | # will be relative from the directory where doxygen is started.
151 | # This tag requires that the tag FULL_PATH_NAMES is set to YES.
152 |
153 | STRIP_FROM_PATH =
154 |
155 | # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
156 | # path mentioned in the documentation of a class, which tells the reader which
157 | # header file to include in order to use a class. If left blank only the name of
158 | # the header file containing the class definition is used. Otherwise one should
159 | # specify the list of include paths that are normally passed to the compiler
160 | # using the -I flag.
161 |
162 | STRIP_FROM_INC_PATH =
163 |
164 | # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
165 | # less readable) file names. This can be useful is your file systems doesn't
166 | # support long names like on DOS, Mac, or CD-ROM.
167 | # The default value is: NO.
168 |
169 | SHORT_NAMES = NO
170 |
171 | # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
172 | # first line (until the first dot) of a Javadoc-style comment as the brief
173 | # description. If set to NO, the Javadoc-style will behave just like regular Qt-
174 | # style comments (thus requiring an explicit @brief command for a brief
175 | # description.)
176 | # The default value is: NO.
177 |
178 | JAVADOC_AUTOBRIEF = YES
179 |
180 | # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
181 | # line (until the first dot) of a Qt-style comment as the brief description. If
182 | # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
183 | # requiring an explicit \brief command for a brief description.)
184 | # The default value is: NO.
185 |
186 | QT_AUTOBRIEF = YES
187 |
188 | # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
189 | # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
190 | # a brief description. This used to be the default behavior. The new default is
191 | # to treat a multi-line C++ comment block as a detailed description. Set this
192 | # tag to YES if you prefer the old behavior instead.
193 | #
194 | # Note that setting this tag to YES also means that rational rose comments are
195 | # not recognized any more.
196 | # The default value is: NO.
197 |
198 | MULTILINE_CPP_IS_BRIEF = NO
199 |
200 | # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
201 | # documentation from any documented member that it re-implements.
202 | # The default value is: YES.
203 |
204 | INHERIT_DOCS = YES
205 |
206 | # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce a
207 | # new page for each member. If set to NO, the documentation of a member will be
208 | # part of the file/class/namespace that contains it.
209 | # The default value is: NO.
210 |
211 | SEPARATE_MEMBER_PAGES = NO
212 |
213 | # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
214 | # uses this value to replace tabs by spaces in code fragments.
215 | # Minimum value: 1, maximum value: 16, default value: 4.
216 |
217 | TAB_SIZE = 4
218 |
219 | # This tag can be used to specify a number of aliases that act as commands in
220 | # the documentation. An alias has the form:
221 | # name=value
222 | # For example adding
223 | # "sideeffect=@par Side Effects:\n"
224 | # will allow you to put the command \sideeffect (or @sideeffect) in the
225 | # documentation, which will result in a user-defined paragraph with heading
226 | # "Side Effects:". You can put \n's in the value part of an alias to insert
227 | # newlines.
228 |
229 | ALIASES =
230 |
231 | # This tag can be used to specify a number of word-keyword mappings (TCL only).
232 | # A mapping has the form "name=value". For example adding "class=itcl::class"
233 | # will allow you to use the command class in the itcl::class meaning.
234 |
235 | TCL_SUBST =
236 |
237 | # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
238 | # only. Doxygen will then generate output that is more tailored for C. For
239 | # instance, some of the names that are used will be different. The list of all
240 | # members will be omitted, etc.
241 | # The default value is: NO.
242 |
243 | OPTIMIZE_OUTPUT_FOR_C = YES
244 |
245 | # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or
246 | # Python sources only. Doxygen will then generate output that is more tailored
247 | # for that language. For instance, namespaces will be presented as packages,
248 | # qualified scopes will look different, etc.
249 | # The default value is: NO.
250 |
251 | OPTIMIZE_OUTPUT_JAVA = NO
252 |
253 | # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
254 | # sources. Doxygen will then generate output that is tailored for Fortran.
255 | # The default value is: NO.
256 |
257 | OPTIMIZE_FOR_FORTRAN = NO
258 |
259 | # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
260 | # sources. Doxygen will then generate output that is tailored for VHDL.
261 | # The default value is: NO.
262 |
263 | OPTIMIZE_OUTPUT_VHDL = NO
264 |
265 | # Doxygen selects the parser to use depending on the extension of the files it
266 | # parses. With this tag you can assign which parser to use for a given
267 | # extension. Doxygen has a built-in mapping, but you can override or extend it
268 | # using this tag. The format is ext=language, where ext is a file extension, and
269 | # language is one of the parsers supported by doxygen: IDL, Java, Javascript,
270 | # C#, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL. For instance to make
271 | # doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
272 | # (default is Fortran), use: inc=Fortran f=C.
273 | #
274 | # Note For files without extension you can use no_extension as a placeholder.
275 | #
276 | # Note that for custom extensions you also need to set FILE_PATTERNS otherwise
277 | # the files are not read by doxygen.
278 |
279 | EXTENSION_MAPPING =
280 |
281 | # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
282 | # according to the Markdown format, which allows for more readable
283 | # documentation. See http://daringfireball.net/projects/markdown/ for details.
284 | # The output of markdown processing is further processed by doxygen, so you can
285 | # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
286 | # case of backward compatibilities issues.
287 | # The default value is: YES.
288 |
289 | MARKDOWN_SUPPORT = YES
290 |
291 | # When enabled doxygen tries to link words that correspond to documented
292 | # classes, or namespaces to their corresponding documentation. Such a link can
293 | # be prevented in individual cases by by putting a % sign in front of the word
294 | # or globally by setting AUTOLINK_SUPPORT to NO.
295 | # The default value is: YES.
296 |
297 | AUTOLINK_SUPPORT = YES
298 |
299 | # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
300 | # to include (a tag file for) the STL sources as input, then you should set this
301 | # tag to YES in order to let doxygen match functions declarations and
302 | # definitions whose arguments contain STL classes (e.g. func(std::string);
303 | # versus func(std::string) {}). This also make the inheritance and collaboration
304 | # diagrams that involve STL classes more complete and accurate.
305 | # The default value is: NO.
306 |
307 | BUILTIN_STL_SUPPORT = NO
308 |
309 | # If you use Microsoft's C++/CLI language, you should set this option to YES to
310 | # enable parsing support.
311 | # The default value is: NO.
312 |
313 | CPP_CLI_SUPPORT = NO
314 |
315 | # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
316 | # http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen
317 | # will parse them like normal C++ but will assume all classes use public instead
318 | # of private inheritance when no explicit protection keyword is present.
319 | # The default value is: NO.
320 |
321 | SIP_SUPPORT = NO
322 |
323 | # For Microsoft's IDL there are propget and propput attributes to indicate
324 | # getter and setter methods for a property. Setting this option to YES will make
325 | # doxygen to replace the get and set methods by a property in the documentation.
326 | # This will only work if the methods are indeed getting or setting a simple
327 | # type. If this is not the case, or you want to show the methods anyway, you
328 | # should set this option to NO.
329 | # The default value is: YES.
330 |
331 | IDL_PROPERTY_SUPPORT = YES
332 |
333 | # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
334 | # tag is set to YES, then doxygen will reuse the documentation of the first
335 | # member in the group (if any) for the other members of the group. By default
336 | # all members of a group must be documented explicitly.
337 | # The default value is: NO.
338 |
339 | DISTRIBUTE_GROUP_DOC = NO
340 |
341 | # Set the SUBGROUPING tag to YES to allow class member groups of the same type
342 | # (for instance a group of public functions) to be put as a subgroup of that
343 | # type (e.g. under the Public Functions section). Set it to NO to prevent
344 | # subgrouping. Alternatively, this can be done per class using the
345 | # \nosubgrouping command.
346 | # The default value is: YES.
347 |
348 | SUBGROUPING = YES
349 |
350 | # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions
351 | # are shown inside the group in which they are included (e.g. using \ingroup)
352 | # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
353 | # and RTF).
354 | #
355 | # Note that this feature does not work in combination with
356 | # SEPARATE_MEMBER_PAGES.
357 | # The default value is: NO.
358 |
359 | INLINE_GROUPED_CLASSES = NO
360 |
361 | # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions
362 | # with only public data fields or simple typedef fields will be shown inline in
363 | # the documentation of the scope in which they are defined (i.e. file,
364 | # namespace, or group documentation), provided this scope is documented. If set
365 | # to NO, structs, classes, and unions are shown on a separate page (for HTML and
366 | # Man pages) or section (for LaTeX and RTF).
367 | # The default value is: NO.
368 |
369 | INLINE_SIMPLE_STRUCTS = YES
370 |
371 | # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
372 | # enum is documented as struct, union, or enum with the name of the typedef. So
373 | # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
374 | # with name TypeT. When disabled the typedef will appear as a member of a file,
375 | # namespace, or class. And the struct will be named TypeS. This can typically be
376 | # useful for C code in case the coding convention dictates that all compound
377 | # types are typedef'ed and only the typedef is referenced, never the tag name.
378 | # The default value is: NO.
379 |
380 | TYPEDEF_HIDES_STRUCT = NO
381 |
382 | # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
383 | # cache is used to resolve symbols given their name and scope. Since this can be
384 | # an expensive process and often the same symbol appears multiple times in the
385 | # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
386 | # doxygen will become slower. If the cache is too large, memory is wasted. The
387 | # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
388 | # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
389 | # symbols. At the end of a run doxygen will report the cache usage and suggest
390 | # the optimal cache size from a speed point of view.
391 | # Minimum value: 0, maximum value: 9, default value: 0.
392 |
393 | LOOKUP_CACHE_SIZE = 0
394 |
395 | #---------------------------------------------------------------------------
396 | # Build related configuration options
397 | #---------------------------------------------------------------------------
398 |
399 | # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
400 | # documentation are documented, even if no documentation was available. Private
401 | # class members and static file members will be hidden unless the
402 | # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
403 | # Note: This will also disable the warnings about undocumented members that are
404 | # normally produced when WARNINGS is set to YES.
405 | # The default value is: NO.
406 |
407 | EXTRACT_ALL = YES
408 |
409 | # If the EXTRACT_PRIVATE tag is set to YES all private members of a class will
410 | # be included in the documentation.
411 | # The default value is: NO.
412 |
413 | EXTRACT_PRIVATE = NO
414 |
415 | # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal
416 | # scope will be included in the documentation.
417 | # The default value is: NO.
418 |
419 | EXTRACT_PACKAGE = NO
420 |
421 | # If the EXTRACT_STATIC tag is set to YES all static members of a file will be
422 | # included in the documentation.
423 | # The default value is: NO.
424 |
425 | EXTRACT_STATIC = YES
426 |
427 | # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) defined
428 | # locally in source files will be included in the documentation. If set to NO
429 | # only classes defined in header files are included. Does not have any effect
430 | # for Java sources.
431 | # The default value is: YES.
432 |
433 | EXTRACT_LOCAL_CLASSES = YES
434 |
435 | # This flag is only useful for Objective-C code. When set to YES local methods,
436 | # which are defined in the implementation section but not in the interface are
437 | # included in the documentation. If set to NO only methods in the interface are
438 | # included.
439 | # The default value is: NO.
440 |
441 | EXTRACT_LOCAL_METHODS = NO
442 |
443 | # If this flag is set to YES, the members of anonymous namespaces will be
444 | # extracted and appear in the documentation as a namespace called
445 | # 'anonymous_namespace{file}', where file will be replaced with the base name of
446 | # the file that contains the anonymous namespace. By default anonymous namespace
447 | # are hidden.
448 | # The default value is: NO.
449 |
450 | EXTRACT_ANON_NSPACES = NO
451 |
452 | # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
453 | # undocumented members inside documented classes or files. If set to NO these
454 | # members will be included in the various overviews, but no documentation
455 | # section is generated. This option has no effect if EXTRACT_ALL is enabled.
456 | # The default value is: NO.
457 |
458 | HIDE_UNDOC_MEMBERS = NO
459 |
460 | # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
461 | # undocumented classes that are normally visible in the class hierarchy. If set
462 | # to NO these classes will be included in the various overviews. This option has
463 | # no effect if EXTRACT_ALL is enabled.
464 | # The default value is: NO.
465 |
466 | HIDE_UNDOC_CLASSES = NO
467 |
468 | # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
469 | # (class|struct|union) declarations. If set to NO these declarations will be
470 | # included in the documentation.
471 | # The default value is: NO.
472 |
473 | HIDE_FRIEND_COMPOUNDS = NO
474 |
475 | # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
476 | # documentation blocks found inside the body of a function. If set to NO these
477 | # blocks will be appended to the function's detailed documentation block.
478 | # The default value is: NO.
479 |
480 | HIDE_IN_BODY_DOCS = NO
481 |
482 | # The INTERNAL_DOCS tag determines if documentation that is typed after a
483 | # \internal command is included. If the tag is set to NO then the documentation
484 | # will be excluded. Set it to YES to include the internal documentation.
485 | # The default value is: NO.
486 |
487 | INTERNAL_DOCS = NO
488 |
489 | # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
490 | # names in lower-case letters. If set to YES upper-case letters are also
491 | # allowed. This is useful if you have classes or files whose names only differ
492 | # in case and if your file system supports case sensitive file names. Windows
493 | # and Mac users are advised to set this option to NO.
494 | # The default value is: system dependent.
495 |
496 | CASE_SENSE_NAMES = NO
497 |
498 | # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
499 | # their full class and namespace scopes in the documentation. If set to YES the
500 | # scope will be hidden.
501 | # The default value is: NO.
502 |
503 | HIDE_SCOPE_NAMES = NO
504 |
505 | # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
506 | # the files that are included by a file in the documentation of that file.
507 | # The default value is: YES.
508 |
509 | SHOW_INCLUDE_FILES = YES
510 |
511 | # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each
512 | # grouped member an include statement to the documentation, telling the reader
513 | # which file to include in order to use the member.
514 | # The default value is: NO.
515 |
516 | SHOW_GROUPED_MEMB_INC = NO
517 |
518 | # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
519 | # files with double quotes in the documentation rather than with sharp brackets.
520 | # The default value is: NO.
521 |
522 | FORCE_LOCAL_INCLUDES = NO
523 |
524 | # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
525 | # documentation for inline members.
526 | # The default value is: YES.
527 |
528 | INLINE_INFO = YES
529 |
530 | # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
531 | # (detailed) documentation of file and class members alphabetically by member
532 | # name. If set to NO the members will appear in declaration order.
533 | # The default value is: YES.
534 |
535 | SORT_MEMBER_DOCS = YES
536 |
537 | # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
538 | # descriptions of file, namespace and class members alphabetically by member
539 | # name. If set to NO the members will appear in declaration order. Note that
540 | # this will also influence the order of the classes in the class list.
541 | # The default value is: NO.
542 |
543 | SORT_BRIEF_DOCS = NO
544 |
545 | # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
546 | # (brief and detailed) documentation of class members so that constructors and
547 | # destructors are listed first. If set to NO the constructors will appear in the
548 | # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.
549 | # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief
550 | # member documentation.
551 | # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting
552 | # detailed member documentation.
553 | # The default value is: NO.
554 |
555 | SORT_MEMBERS_CTORS_1ST = NO
556 |
557 | # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
558 | # of group names into alphabetical order. If set to NO the group names will
559 | # appear in their defined order.
560 | # The default value is: NO.
561 |
562 | SORT_GROUP_NAMES = NO
563 |
564 | # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
565 | # fully-qualified names, including namespaces. If set to NO, the class list will
566 | # be sorted only by class name, not including the namespace part.
567 | # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
568 | # Note: This option applies only to the class list, not to the alphabetical
569 | # list.
570 | # The default value is: NO.
571 |
572 | SORT_BY_SCOPE_NAME = NO
573 |
574 | # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
575 | # type resolution of all parameters of a function it will reject a match between
576 | # the prototype and the implementation of a member function even if there is
577 | # only one candidate or it is obvious which candidate to choose by doing a
578 | # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still
579 | # accept a match between prototype and implementation in such cases.
580 | # The default value is: NO.
581 |
582 | STRICT_PROTO_MATCHING = NO
583 |
584 | # The GENERATE_TODOLIST tag can be used to enable ( YES) or disable ( NO) the
585 | # todo list. This list is created by putting \todo commands in the
586 | # documentation.
587 | # The default value is: YES.
588 |
589 | GENERATE_TODOLIST = YES
590 |
591 | # The GENERATE_TESTLIST tag can be used to enable ( YES) or disable ( NO) the
592 | # test list. This list is created by putting \test commands in the
593 | # documentation.
594 | # The default value is: YES.
595 |
596 | GENERATE_TESTLIST = YES
597 |
598 | # The GENERATE_BUGLIST tag can be used to enable ( YES) or disable ( NO) the bug
599 | # list. This list is created by putting \bug commands in the documentation.
600 | # The default value is: YES.
601 |
602 | GENERATE_BUGLIST = YES
603 |
604 | # The GENERATE_DEPRECATEDLIST tag can be used to enable ( YES) or disable ( NO)
605 | # the deprecated list. This list is created by putting \deprecated commands in
606 | # the documentation.
607 | # The default value is: YES.
608 |
609 | GENERATE_DEPRECATEDLIST= YES
610 |
611 | # The ENABLED_SECTIONS tag can be used to enable conditional documentation
612 | # sections, marked by \if ... \endif and \cond
613 | # ... \endcond blocks.
614 |
615 | ENABLED_SECTIONS =
616 |
617 | # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
618 | # initial value of a variable or macro / define can have for it to appear in the
619 | # documentation. If the initializer consists of more lines than specified here
620 | # it will be hidden. Use a value of 0 to hide initializers completely. The
621 | # appearance of the value of individual variables and macros / defines can be
622 | # controlled using \showinitializer or \hideinitializer command in the
623 | # documentation regardless of this setting.
624 | # Minimum value: 0, maximum value: 10000, default value: 30.
625 |
626 | MAX_INITIALIZER_LINES = 30
627 |
628 | # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
629 | # the bottom of the documentation of classes and structs. If set to YES the list
630 | # will mention the files that were used to generate the documentation.
631 | # The default value is: YES.
632 |
633 | SHOW_USED_FILES = YES
634 |
635 | # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This
636 | # will remove the Files entry from the Quick Index and from the Folder Tree View
637 | # (if specified).
638 | # The default value is: YES.
639 |
640 | SHOW_FILES = YES
641 |
642 | # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces
643 | # page. This will remove the Namespaces entry from the Quick Index and from the
644 | # Folder Tree View (if specified).
645 | # The default value is: YES.
646 |
647 | SHOW_NAMESPACES = YES
648 |
649 | # The FILE_VERSION_FILTER tag can be used to specify a program or script that
650 | # doxygen should invoke to get the current version for each file (typically from
651 | # the version control system). Doxygen will invoke the program by executing (via
652 | # popen()) the command command input-file, where command is the value of the
653 | # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
654 | # by doxygen. Whatever the program writes to standard output is used as the file
655 | # version. For an example see the documentation.
656 |
657 | FILE_VERSION_FILTER =
658 |
659 | # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
660 | # by doxygen. The layout file controls the global structure of the generated
661 | # output files in an output format independent way. To create the layout file
662 | # that represents doxygen's defaults, run doxygen with the -l option. You can
663 | # optionally specify a file name after the option, if omitted DoxygenLayout.xml
664 | # will be used as the name of the layout file.
665 | #
666 | # Note that if you run doxygen from a directory containing a file called
667 | # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
668 | # tag is left empty.
669 |
670 | LAYOUT_FILE =
671 |
672 | # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
673 | # the reference definitions. This must be a list of .bib files. The .bib
674 | # extension is automatically appended if omitted. This requires the bibtex tool
675 | # to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.
676 | # For LaTeX the style of the bibliography can be controlled using
677 | # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
678 | # search path. Do not use file names with spaces, bibtex cannot handle them. See
679 | # also \cite for info how to create references.
680 |
681 | CITE_BIB_FILES =
682 |
683 | #---------------------------------------------------------------------------
684 | # Configuration options related to warning and progress messages
685 | #---------------------------------------------------------------------------
686 |
687 | # The QUIET tag can be used to turn on/off the messages that are generated to
688 | # standard output by doxygen. If QUIET is set to YES this implies that the
689 | # messages are off.
690 | # The default value is: NO.
691 |
692 | QUIET = NO
693 |
694 | # The WARNINGS tag can be used to turn on/off the warning messages that are
695 | # generated to standard error ( stderr) by doxygen. If WARNINGS is set to YES
696 | # this implies that the warnings are on.
697 | #
698 | # Tip: Turn warnings on while writing the documentation.
699 | # The default value is: YES.
700 |
701 | WARNINGS = YES
702 |
703 | # If the WARN_IF_UNDOCUMENTED tag is set to YES, then doxygen will generate
704 | # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
705 | # will automatically be disabled.
706 | # The default value is: YES.
707 |
708 | WARN_IF_UNDOCUMENTED = YES
709 |
710 | # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
711 | # potential errors in the documentation, such as not documenting some parameters
712 | # in a documented function, or documenting parameters that don't exist or using
713 | # markup commands wrongly.
714 | # The default value is: YES.
715 |
716 | WARN_IF_DOC_ERROR = YES
717 |
718 | # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
719 | # are documented, but have no documentation for their parameters or return
720 | # value. If set to NO doxygen will only warn about wrong or incomplete parameter
721 | # documentation, but not about the absence of documentation.
722 | # The default value is: NO.
723 |
724 | WARN_NO_PARAMDOC = NO
725 |
726 | # The WARN_FORMAT tag determines the format of the warning messages that doxygen
727 | # can produce. The string should contain the $file, $line, and $text tags, which
728 | # will be replaced by the file and line number from which the warning originated
729 | # and the warning text. Optionally the format may contain $version, which will
730 | # be replaced by the version of the file (if it could be obtained via
731 | # FILE_VERSION_FILTER)
732 | # The default value is: $file:$line: $text.
733 |
734 | WARN_FORMAT = "$file:$line: $text"
735 |
736 | # The WARN_LOGFILE tag can be used to specify a file to which warning and error
737 | # messages should be written. If left blank the output is written to standard
738 | # error (stderr).
739 |
740 | WARN_LOGFILE =
741 |
742 | #---------------------------------------------------------------------------
743 | # Configuration options related to the input files
744 | #---------------------------------------------------------------------------
745 |
746 | # The INPUT tag is used to specify the files and/or directories that contain
747 | # documented source files. You may enter file names like myfile.cpp or
748 | # directories like /usr/src/myproject. Separate the files or directories with
749 | # spaces.
750 | # Note: If this tag is empty the current directory is searched.
751 |
752 | INPUT =
753 |
754 | # This tag can be used to specify the character encoding of the source files
755 | # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
756 | # libiconv (or the iconv built into libc) for the transcoding. See the libiconv
757 | # documentation (see: http://www.gnu.org/software/libiconv) for the list of
758 | # possible encodings.
759 | # The default value is: UTF-8.
760 |
761 | INPUT_ENCODING = UTF-8
762 |
763 | # If the value of the INPUT tag contains directories, you can use the
764 | # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
765 | # *.h) to filter out the source-files in the directories. If left blank the
766 | # following patterns are tested:*.c, *.cc, *.cxx, *.cpp, *.c++, *.java, *.ii,
767 | # *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp,
768 | # *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown,
769 | # *.md, *.mm, *.dox, *.py, *.f90, *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf,
770 | # *.qsf, *.as and *.js.
771 |
772 | FILE_PATTERNS =
773 |
774 | # The RECURSIVE tag can be used to specify whether or not subdirectories should
775 | # be searched for input files as well.
776 | # The default value is: NO.
777 |
778 | RECURSIVE = NO
779 |
780 | # The EXCLUDE tag can be used to specify files and/or directories that should be
781 | # excluded from the INPUT source files. This way you can easily exclude a
782 | # subdirectory from a directory tree whose root is specified with the INPUT tag.
783 | #
784 | # Note that relative paths are relative to the directory from which doxygen is
785 | # run.
786 |
787 | EXCLUDE =
788 |
789 | # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
790 | # directories that are symbolic links (a Unix file system feature) are excluded
791 | # from the input.
792 | # The default value is: NO.
793 |
794 | EXCLUDE_SYMLINKS = NO
795 |
796 | # If the value of the INPUT tag contains directories, you can use the
797 | # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
798 | # certain files from those directories.
799 | #
800 | # Note that the wildcards are matched against the file with absolute path, so to
801 | # exclude all test directories for example use the pattern */test/*
802 |
803 | EXCLUDE_PATTERNS =
804 |
805 | # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
806 | # (namespaces, classes, functions, etc.) that should be excluded from the
807 | # output. The symbol name can be a fully qualified name, a word, or if the
808 | # wildcard * is used, a substring. Examples: ANamespace, AClass,
809 | # AClass::ANamespace, ANamespace::*Test
810 | #
811 | # Note that the wildcards are matched against the file with absolute path, so to
812 | # exclude all test directories use the pattern */test/*
813 |
814 | EXCLUDE_SYMBOLS =
815 |
816 | # The EXAMPLE_PATH tag can be used to specify one or more files or directories
817 | # that contain example code fragments that are included (see the \include
818 | # command).
819 |
820 | EXAMPLE_PATH =
821 |
822 | # If the value of the EXAMPLE_PATH tag contains directories, you can use the
823 | # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
824 | # *.h) to filter out the source-files in the directories. If left blank all
825 | # files are included.
826 |
827 | EXAMPLE_PATTERNS =
828 |
829 | # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
830 | # searched for input files to be used with the \include or \dontinclude commands
831 | # irrespective of the value of the RECURSIVE tag.
832 | # The default value is: NO.
833 |
834 | EXAMPLE_RECURSIVE = NO
835 |
836 | # The IMAGE_PATH tag can be used to specify one or more files or directories
837 | # that contain images that are to be included in the documentation (see the
838 | # \image command).
839 |
840 | IMAGE_PATH =
841 |
842 | # The INPUT_FILTER tag can be used to specify a program that doxygen should
843 | # invoke to filter for each input file. Doxygen will invoke the filter program
844 | # by executing (via popen()) the command:
845 | #
846 | #
847 | #
848 | # where is the value of the INPUT_FILTER tag, and is the
849 | # name of an input file. Doxygen will then use the output that the filter
850 | # program writes to standard output. If FILTER_PATTERNS is specified, this tag
851 | # will be ignored.
852 | #
853 | # Note that the filter must not add or remove lines; it is applied before the
854 | # code is scanned, but not when the output code is generated. If lines are added
855 | # or removed, the anchors will not be placed correctly.
856 |
857 | INPUT_FILTER =
858 |
859 | # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
860 | # basis. Doxygen will compare the file name with each pattern and apply the
861 | # filter if there is a match. The filters are a list of the form: pattern=filter
862 | # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
863 | # filters are used. If the FILTER_PATTERNS tag is empty or if none of the
864 | # patterns match the file name, INPUT_FILTER is applied.
865 |
866 | FILTER_PATTERNS =
867 |
868 | # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
869 | # INPUT_FILTER ) will also be used to filter the input files that are used for
870 | # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
871 | # The default value is: NO.
872 |
873 | FILTER_SOURCE_FILES = NO
874 |
875 | # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
876 | # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
877 | # it is also possible to disable source filtering for a specific pattern using
878 | # *.ext= (so without naming a filter).
879 | # This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
880 |
881 | FILTER_SOURCE_PATTERNS =
882 |
883 | # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
884 | # is part of the input, its contents will be placed on the main page
885 | # (index.html). This can be useful if you have a project on for instance GitHub
886 | # and want to reuse the introduction page also for the doxygen output.
887 |
888 | USE_MDFILE_AS_MAINPAGE = README.md
889 |
890 | #---------------------------------------------------------------------------
891 | # Configuration options related to source browsing
892 | #---------------------------------------------------------------------------
893 |
894 | # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
895 | # generated. Documented entities will be cross-referenced with these sources.
896 | #
897 | # Note: To get rid of all source code in the generated output, make sure that
898 | # also VERBATIM_HEADERS is set to NO.
899 | # The default value is: NO.
900 |
901 | SOURCE_BROWSER = YES
902 |
903 | # Setting the INLINE_SOURCES tag to YES will include the body of functions,
904 | # classes and enums directly into the documentation.
905 | # The default value is: NO.
906 |
907 | INLINE_SOURCES = NO
908 |
909 | # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
910 | # special comment blocks from generated source code fragments. Normal C, C++ and
911 | # Fortran comments will always remain visible.
912 | # The default value is: YES.
913 |
914 | STRIP_CODE_COMMENTS = YES
915 |
916 | # If the REFERENCED_BY_RELATION tag is set to YES then for each documented
917 | # function all documented functions referencing it will be listed.
918 | # The default value is: NO.
919 |
920 | REFERENCED_BY_RELATION = NO
921 |
922 | # If the REFERENCES_RELATION tag is set to YES then for each documented function
923 | # all documented entities called/used by that function will be listed.
924 | # The default value is: NO.
925 |
926 | REFERENCES_RELATION = NO
927 |
928 | # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set
929 | # to YES, then the hyperlinks from functions in REFERENCES_RELATION and
930 | # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
931 | # link to the documentation.
932 | # The default value is: YES.
933 |
934 | REFERENCES_LINK_SOURCE = YES
935 |
936 | # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
937 | # source code will show a tooltip with additional information such as prototype,
938 | # brief description and links to the definition and documentation. Since this
939 | # will make the HTML file larger and loading of large files a bit slower, you
940 | # can opt to disable this feature.
941 | # The default value is: YES.
942 | # This tag requires that the tag SOURCE_BROWSER is set to YES.
943 |
944 | SOURCE_TOOLTIPS = YES
945 |
946 | # If the USE_HTAGS tag is set to YES then the references to source code will
947 | # point to the HTML generated by the htags(1) tool instead of doxygen built-in
948 | # source browser. The htags tool is part of GNU's global source tagging system
949 | # (see http://www.gnu.org/software/global/global.html). You will need version
950 | # 4.8.6 or higher.
951 | #
952 | # To use it do the following:
953 | # - Install the latest version of global
954 | # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
955 | # - Make sure the INPUT points to the root of the source tree
956 | # - Run doxygen as normal
957 | #
958 | # Doxygen will invoke htags (and that will in turn invoke gtags), so these
959 | # tools must be available from the command line (i.e. in the search path).
960 | #
961 | # The result: instead of the source browser generated by doxygen, the links to
962 | # source code will now point to the output of htags.
963 | # The default value is: NO.
964 | # This tag requires that the tag SOURCE_BROWSER is set to YES.
965 |
966 | USE_HTAGS = NO
967 |
968 | # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
969 | # verbatim copy of the header file for each class for which an include is
970 | # specified. Set to NO to disable this.
971 | # See also: Section \class.
972 | # The default value is: YES.
973 |
974 | VERBATIM_HEADERS = YES
975 |
976 | #---------------------------------------------------------------------------
977 | # Configuration options related to the alphabetical class index
978 | #---------------------------------------------------------------------------
979 |
980 | # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
981 | # compounds will be generated. Enable this if the project contains a lot of
982 | # classes, structs, unions or interfaces.
983 | # The default value is: YES.
984 |
985 | ALPHABETICAL_INDEX = YES
986 |
987 | # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
988 | # which the alphabetical index list will be split.
989 | # Minimum value: 1, maximum value: 20, default value: 5.
990 | # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
991 |
992 | COLS_IN_ALPHA_INDEX = 5
993 |
994 | # In case all classes in a project start with a common prefix, all classes will
995 | # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
996 | # can be used to specify a prefix (or a list of prefixes) that should be ignored
997 | # while generating the index headers.
998 | # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
999 |
1000 | IGNORE_PREFIX =
1001 |
1002 | #---------------------------------------------------------------------------
1003 | # Configuration options related to the HTML output
1004 | #---------------------------------------------------------------------------
1005 |
1006 | # If the GENERATE_HTML tag is set to YES doxygen will generate HTML output
1007 | # The default value is: YES.
1008 |
1009 | GENERATE_HTML = YES
1010 |
1011 | # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1012 | # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1013 | # it.
1014 | # The default directory is: html.
1015 | # This tag requires that the tag GENERATE_HTML is set to YES.
1016 |
1017 | HTML_OUTPUT = html
1018 |
1019 | # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
1020 | # generated HTML page (for example: .htm, .php, .asp).
1021 | # The default value is: .html.
1022 | # This tag requires that the tag GENERATE_HTML is set to YES.
1023 |
1024 | HTML_FILE_EXTENSION = .html
1025 |
1026 | # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1027 | # each generated HTML page. If the tag is left blank doxygen will generate a
1028 | # standard header.
1029 | #
1030 | # To get valid HTML the header file that includes any scripts and style sheets
1031 | # that doxygen needs, which is dependent on the configuration options used (e.g.
1032 | # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
1033 | # default header using
1034 | # doxygen -w html new_header.html new_footer.html new_stylesheet.css
1035 | # YourConfigFile
1036 | # and then modify the file new_header.html. See also section "Doxygen usage"
1037 | # for information on how to generate the default header that doxygen normally
1038 | # uses.
1039 | # Note: The header is subject to change so you typically have to regenerate the
1040 | # default header when upgrading to a newer version of doxygen. For a description
1041 | # of the possible markers and block names see the documentation.
1042 | # This tag requires that the tag GENERATE_HTML is set to YES.
1043 |
1044 | HTML_HEADER =
1045 |
1046 | # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1047 | # generated HTML page. If the tag is left blank doxygen will generate a standard
1048 | # footer. See HTML_HEADER for more information on how to generate a default
1049 | # footer and what special commands can be used inside the footer. See also
1050 | # section "Doxygen usage" for information on how to generate the default footer
1051 | # that doxygen normally uses.
1052 | # This tag requires that the tag GENERATE_HTML is set to YES.
1053 |
1054 | HTML_FOOTER =
1055 |
1056 | # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1057 | # sheet that is used by each HTML page. It can be used to fine-tune the look of
1058 | # the HTML output. If left blank doxygen will generate a default style sheet.
1059 | # See also section "Doxygen usage" for information on how to generate the style
1060 | # sheet that doxygen normally uses.
1061 | # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
1062 | # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1063 | # obsolete.
1064 | # This tag requires that the tag GENERATE_HTML is set to YES.
1065 |
1066 | HTML_STYLESHEET =
1067 |
1068 | # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional user-
1069 | # defined cascading style sheet that is included after the standard style sheets
1070 | # created by doxygen. Using this option one can overrule certain style aspects.
1071 | # This is preferred over using HTML_STYLESHEET since it does not replace the
1072 | # standard style sheet and is therefor more robust against future updates.
1073 | # Doxygen will copy the style sheet file to the output directory. For an example
1074 | # see the documentation.
1075 | # This tag requires that the tag GENERATE_HTML is set to YES.
1076 |
1077 | HTML_EXTRA_STYLESHEET =
1078 |
1079 | # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
1080 | # other source files which should be copied to the HTML output directory. Note
1081 | # that these files will be copied to the base HTML output directory. Use the
1082 | # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1083 | # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1084 | # files will be copied as-is; there are no commands or markers available.
1085 | # This tag requires that the tag GENERATE_HTML is set to YES.
1086 |
1087 | HTML_EXTRA_FILES =
1088 |
1089 | # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
1090 | # will adjust the colors in the stylesheet and background images according to
1091 | # this color. Hue is specified as an angle on a colorwheel, see
1092 | # http://en.wikipedia.org/wiki/Hue for more information. For instance the value
1093 | # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
1094 | # purple, and 360 is red again.
1095 | # Minimum value: 0, maximum value: 359, default value: 220.
1096 | # This tag requires that the tag GENERATE_HTML is set to YES.
1097 |
1098 | HTML_COLORSTYLE_HUE = 220
1099 |
1100 | # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
1101 | # in the HTML output. For a value of 0 the output will use grayscales only. A
1102 | # value of 255 will produce the most vivid colors.
1103 | # Minimum value: 0, maximum value: 255, default value: 100.
1104 | # This tag requires that the tag GENERATE_HTML is set to YES.
1105 |
1106 | HTML_COLORSTYLE_SAT = 100
1107 |
1108 | # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
1109 | # luminance component of the colors in the HTML output. Values below 100
1110 | # gradually make the output lighter, whereas values above 100 make the output
1111 | # darker. The value divided by 100 is the actual gamma applied, so 80 represents
1112 | # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
1113 | # change the gamma.
1114 | # Minimum value: 40, maximum value: 240, default value: 80.
1115 | # This tag requires that the tag GENERATE_HTML is set to YES.
1116 |
1117 | HTML_COLORSTYLE_GAMMA = 80
1118 |
1119 | # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
1120 | # page will contain the date and time when the page was generated. Setting this
1121 | # to NO can help when comparing the output of multiple runs.
1122 | # The default value is: YES.
1123 | # This tag requires that the tag GENERATE_HTML is set to YES.
1124 |
1125 | HTML_TIMESTAMP = YES
1126 |
1127 | # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
1128 | # documentation will contain sections that can be hidden and shown after the
1129 | # page has loaded.
1130 | # The default value is: NO.
1131 | # This tag requires that the tag GENERATE_HTML is set to YES.
1132 |
1133 | HTML_DYNAMIC_SECTIONS = NO
1134 |
1135 | # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
1136 | # shown in the various tree structured indices initially; the user can expand
1137 | # and collapse entries dynamically later on. Doxygen will expand the tree to
1138 | # such a level that at most the specified number of entries are visible (unless
1139 | # a fully collapsed tree already exceeds this amount). So setting the number of
1140 | # entries 1 will produce a full collapsed tree by default. 0 is a special value
1141 | # representing an infinite number of entries and will result in a full expanded
1142 | # tree by default.
1143 | # Minimum value: 0, maximum value: 9999, default value: 100.
1144 | # This tag requires that the tag GENERATE_HTML is set to YES.
1145 |
1146 | HTML_INDEX_NUM_ENTRIES = 100
1147 |
1148 | # If the GENERATE_DOCSET tag is set to YES, additional index files will be
1149 | # generated that can be used as input for Apple's Xcode 3 integrated development
1150 | # environment (see: http://developer.apple.com/tools/xcode/), introduced with
1151 | # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
1152 | # Makefile in the HTML output directory. Running make will produce the docset in
1153 | # that directory and running make install will install the docset in
1154 | # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
1155 | # startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
1156 | # for more information.
1157 | # The default value is: NO.
1158 | # This tag requires that the tag GENERATE_HTML is set to YES.
1159 |
1160 | GENERATE_DOCSET = NO
1161 |
1162 | # This tag determines the name of the docset feed. A documentation feed provides
1163 | # an umbrella under which multiple documentation sets from a single provider
1164 | # (such as a company or product suite) can be grouped.
1165 | # The default value is: Doxygen generated docs.
1166 | # This tag requires that the tag GENERATE_DOCSET is set to YES.
1167 |
1168 | DOCSET_FEEDNAME = "Doxygen generated docs"
1169 |
1170 | # This tag specifies a string that should uniquely identify the documentation
1171 | # set bundle. This should be a reverse domain-name style string, e.g.
1172 | # com.mycompany.MyDocSet. Doxygen will append .docset to the name.
1173 | # The default value is: org.doxygen.Project.
1174 | # This tag requires that the tag GENERATE_DOCSET is set to YES.
1175 |
1176 | DOCSET_BUNDLE_ID = org.doxygen.Project
1177 |
1178 | # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
1179 | # the documentation publisher. This should be a reverse domain-name style
1180 | # string, e.g. com.mycompany.MyDocSet.documentation.
1181 | # The default value is: org.doxygen.Publisher.
1182 | # This tag requires that the tag GENERATE_DOCSET is set to YES.
1183 |
1184 | DOCSET_PUBLISHER_ID = org.doxygen.Publisher
1185 |
1186 | # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1187 | # The default value is: Publisher.
1188 | # This tag requires that the tag GENERATE_DOCSET is set to YES.
1189 |
1190 | DOCSET_PUBLISHER_NAME = Publisher
1191 |
1192 | # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
1193 | # additional HTML index files: index.hhp, index.hhc, and index.hhk. The
1194 | # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1195 | # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1196 | # Windows.
1197 | #
1198 | # The HTML Help Workshop contains a compiler that can convert all HTML output
1199 | # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1200 | # files are now used as the Windows 98 help format, and will replace the old
1201 | # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1202 | # HTML files also contain an index, a table of contents, and you can search for
1203 | # words in the documentation. The HTML workshop also contains a viewer for
1204 | # compressed HTML files.
1205 | # The default value is: NO.
1206 | # This tag requires that the tag GENERATE_HTML is set to YES.
1207 |
1208 | GENERATE_HTMLHELP = NO
1209 |
1210 | # The CHM_FILE tag can be used to specify the file name of the resulting .chm
1211 | # file. You can add a path in front of the file if the result should not be
1212 | # written to the html output directory.
1213 | # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1214 |
1215 | CHM_FILE =
1216 |
1217 | # The HHC_LOCATION tag can be used to specify the location (absolute path
1218 | # including file name) of the HTML help compiler ( hhc.exe). If non-empty
1219 | # doxygen will try to run the HTML help compiler on the generated index.hhp.
1220 | # The file has to be specified with full path.
1221 | # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1222 |
1223 | HHC_LOCATION =
1224 |
1225 | # The GENERATE_CHI flag controls if a separate .chi index file is generated (
1226 | # YES) or that it should be included in the master .chm file ( NO).
1227 | # The default value is: NO.
1228 | # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1229 |
1230 | GENERATE_CHI = NO
1231 |
1232 | # The CHM_INDEX_ENCODING is used to encode HtmlHelp index ( hhk), content ( hhc)
1233 | # and project file content.
1234 | # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1235 |
1236 | CHM_INDEX_ENCODING =
1237 |
1238 | # The BINARY_TOC flag controls whether a binary table of contents is generated (
1239 | # YES) or a normal table of contents ( NO) in the .chm file.
1240 | # The default value is: NO.
1241 | # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1242 |
1243 | BINARY_TOC = NO
1244 |
1245 | # The TOC_EXPAND flag can be set to YES to add extra items for group members to
1246 | # the table of contents of the HTML help documentation and to the tree view.
1247 | # The default value is: NO.
1248 | # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1249 |
1250 | TOC_EXPAND = NO
1251 |
1252 | # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
1253 | # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
1254 | # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
1255 | # (.qch) of the generated HTML documentation.
1256 | # The default value is: NO.
1257 | # This tag requires that the tag GENERATE_HTML is set to YES.
1258 |
1259 | GENERATE_QHP = NO
1260 |
1261 | # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
1262 | # the file name of the resulting .qch file. The path specified is relative to
1263 | # the HTML output folder.
1264 | # This tag requires that the tag GENERATE_QHP is set to YES.
1265 |
1266 | QCH_FILE =
1267 |
1268 | # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
1269 | # Project output. For more information please see Qt Help Project / Namespace
1270 | # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
1271 | # The default value is: org.doxygen.Project.
1272 | # This tag requires that the tag GENERATE_QHP is set to YES.
1273 |
1274 | QHP_NAMESPACE = org.doxygen.Project
1275 |
1276 | # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
1277 | # Help Project output. For more information please see Qt Help Project / Virtual
1278 | # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
1279 | # folders).
1280 | # The default value is: doc.
1281 | # This tag requires that the tag GENERATE_QHP is set to YES.
1282 |
1283 | QHP_VIRTUAL_FOLDER = doc
1284 |
1285 | # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
1286 | # filter to add. For more information please see Qt Help Project / Custom
1287 | # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1288 | # filters).
1289 | # This tag requires that the tag GENERATE_QHP is set to YES.
1290 |
1291 | QHP_CUST_FILTER_NAME =
1292 |
1293 | # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
1294 | # custom filter to add. For more information please see Qt Help Project / Custom
1295 | # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1296 | # filters).
1297 | # This tag requires that the tag GENERATE_QHP is set to YES.
1298 |
1299 | QHP_CUST_FILTER_ATTRS =
1300 |
1301 | # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1302 | # project's filter section matches. Qt Help Project / Filter Attributes (see:
1303 | # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
1304 | # This tag requires that the tag GENERATE_QHP is set to YES.
1305 |
1306 | QHP_SECT_FILTER_ATTRS =
1307 |
1308 | # The QHG_LOCATION tag can be used to specify the location of Qt's
1309 | # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1310 | # generated .qhp file.
1311 | # This tag requires that the tag GENERATE_QHP is set to YES.
1312 |
1313 | QHG_LOCATION =
1314 |
1315 | # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
1316 | # generated, together with the HTML files, they form an Eclipse help plugin. To
1317 | # install this plugin and make it available under the help contents menu in
1318 | # Eclipse, the contents of the directory containing the HTML and XML files needs
1319 | # to be copied into the plugins directory of eclipse. The name of the directory
1320 | # within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
1321 | # After copying Eclipse needs to be restarted before the help appears.
1322 | # The default value is: NO.
1323 | # This tag requires that the tag GENERATE_HTML is set to YES.
1324 |
1325 | GENERATE_ECLIPSEHELP = NO
1326 |
1327 | # A unique identifier for the Eclipse help plugin. When installing the plugin
1328 | # the directory name containing the HTML and XML files should also have this
1329 | # name. Each documentation set should have its own identifier.
1330 | # The default value is: org.doxygen.Project.
1331 | # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.
1332 |
1333 | ECLIPSE_DOC_ID = org.doxygen.Project
1334 |
1335 | # If you want full control over the layout of the generated HTML pages it might
1336 | # be necessary to disable the index and replace it with your own. The
1337 | # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
1338 | # of each HTML page. A value of NO enables the index and the value YES disables
1339 | # it. Since the tabs in the index contain the same information as the navigation
1340 | # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.
1341 | # The default value is: NO.
1342 | # This tag requires that the tag GENERATE_HTML is set to YES.
1343 |
1344 | DISABLE_INDEX = NO
1345 |
1346 | # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1347 | # structure should be generated to display hierarchical information. If the tag
1348 | # value is set to YES, a side panel will be generated containing a tree-like
1349 | # index structure (just like the one that is generated for HTML Help). For this
1350 | # to work a browser that supports JavaScript, DHTML, CSS and frames is required
1351 | # (i.e. any modern browser). Windows users are probably better off using the
1352 | # HTML help feature. Via custom stylesheets (see HTML_EXTRA_STYLESHEET) one can
1353 | # further fine-tune the look of the index. As an example, the default style
1354 | # sheet generated by doxygen has an example that shows how to put an image at
1355 | # the root of the tree instead of the PROJECT_NAME. Since the tree basically has
1356 | # the same information as the tab index, you could consider setting
1357 | # DISABLE_INDEX to YES when enabling this option.
1358 | # The default value is: NO.
1359 | # This tag requires that the tag GENERATE_HTML is set to YES.
1360 |
1361 | GENERATE_TREEVIEW = NO
1362 |
1363 | # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
1364 | # doxygen will group on one line in the generated HTML documentation.
1365 | #
1366 | # Note that a value of 0 will completely suppress the enum values from appearing
1367 | # in the overview section.
1368 | # Minimum value: 0, maximum value: 20, default value: 4.
1369 | # This tag requires that the tag GENERATE_HTML is set to YES.
1370 |
1371 | ENUM_VALUES_PER_LINE = 4
1372 |
1373 | # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
1374 | # to set the initial width (in pixels) of the frame in which the tree is shown.
1375 | # Minimum value: 0, maximum value: 1500, default value: 250.
1376 | # This tag requires that the tag GENERATE_HTML is set to YES.
1377 |
1378 | TREEVIEW_WIDTH = 250
1379 |
1380 | # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open links to
1381 | # external symbols imported via tag files in a separate window.
1382 | # The default value is: NO.
1383 | # This tag requires that the tag GENERATE_HTML is set to YES.
1384 |
1385 | EXT_LINKS_IN_WINDOW = NO
1386 |
1387 | # Use this tag to change the font size of LaTeX formulas included as images in
1388 | # the HTML documentation. When you change the font size after a successful
1389 | # doxygen run you need to manually remove any form_*.png images from the HTML
1390 | # output directory to force them to be regenerated.
1391 | # Minimum value: 8, maximum value: 50, default value: 10.
1392 | # This tag requires that the tag GENERATE_HTML is set to YES.
1393 |
1394 | FORMULA_FONTSIZE = 10
1395 |
1396 | # Use the FORMULA_TRANPARENT tag to determine whether or not the images
1397 | # generated for formulas are transparent PNGs. Transparent PNGs are not
1398 | # supported properly for IE 6.0, but are supported on all modern browsers.
1399 | #
1400 | # Note that when changing this option you need to delete any form_*.png files in
1401 | # the HTML output directory before the changes have effect.
1402 | # The default value is: YES.
1403 | # This tag requires that the tag GENERATE_HTML is set to YES.
1404 |
1405 | FORMULA_TRANSPARENT = YES
1406 |
1407 | # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
1408 | # http://www.mathjax.org) which uses client side Javascript for the rendering
1409 | # instead of using prerendered bitmaps. Use this if you do not have LaTeX
1410 | # installed or if you want to formulas look prettier in the HTML output. When
1411 | # enabled you may also need to install MathJax separately and configure the path
1412 | # to it using the MATHJAX_RELPATH option.
1413 | # The default value is: NO.
1414 | # This tag requires that the tag GENERATE_HTML is set to YES.
1415 |
1416 | USE_MATHJAX = NO
1417 |
1418 | # When MathJax is enabled you can set the default output format to be used for
1419 | # the MathJax output. See the MathJax site (see:
1420 | # http://docs.mathjax.org/en/latest/output.html) for more details.
1421 | # Possible values are: HTML-CSS (which is slower, but has the best
1422 | # compatibility), NativeMML (i.e. MathML) and SVG.
1423 | # The default value is: HTML-CSS.
1424 | # This tag requires that the tag USE_MATHJAX is set to YES.
1425 |
1426 | MATHJAX_FORMAT = HTML-CSS
1427 |
1428 | # When MathJax is enabled you need to specify the location relative to the HTML
1429 | # output directory using the MATHJAX_RELPATH option. The destination directory
1430 | # should contain the MathJax.js script. For instance, if the mathjax directory
1431 | # is located at the same level as the HTML output directory, then
1432 | # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
1433 | # Content Delivery Network so you can quickly see the result without installing
1434 | # MathJax. However, it is strongly recommended to install a local copy of
1435 | # MathJax from http://www.mathjax.org before deployment.
1436 | # The default value is: http://cdn.mathjax.org/mathjax/latest.
1437 | # This tag requires that the tag USE_MATHJAX is set to YES.
1438 |
1439 | MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest
1440 |
1441 | # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
1442 | # extension names that should be enabled during MathJax rendering. For example
1443 | # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
1444 | # This tag requires that the tag USE_MATHJAX is set to YES.
1445 |
1446 | MATHJAX_EXTENSIONS =
1447 |
1448 | # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1449 | # of code that will be used on startup of the MathJax code. See the MathJax site
1450 | # (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an
1451 | # example see the documentation.
1452 | # This tag requires that the tag USE_MATHJAX is set to YES.
1453 |
1454 | MATHJAX_CODEFILE =
1455 |
1456 | # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1457 | # the HTML output. The underlying search engine uses javascript and DHTML and
1458 | # should work on any modern browser. Note that when using HTML help
1459 | # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
1460 | # there is already a search function so this one should typically be disabled.
1461 | # For large projects the javascript based search engine can be slow, then
1462 | # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
1463 | # search using the keyboard; to jump to the search box use + S
1464 | # (what the is depends on the OS and browser, but it is typically
1465 | # , /