See the Christmas lights switch-on at Gateshead's Trinity Square Crowds packed into the town centre to enjoy some early Christmas cheer. Photographs by Tim McGuinness 22 Nov 2019, 12:07 by Barbara Hodgson Christmas Lights switch on at Trinity Square Gateshead. Credit: Tim McGuinness(Image: newcastle chronicle) Christmas Lights switch on at Trinity Square Gateshead Credit: Tim McGuinness(Image: newcastle chronicle) Christmas Lights switch on at Trinity Square Gateshead Credit: Tim McGuinness(Image: newcastle chronicle) Christmas Lights switch on at Trinity Square Gateshead Credit: Tim McGuinness(Image: newcastle chronicle) Christmas Lights switch on at Trinity Square Gateshead Credit: Tim McGuinness(Image: newcastle chronicle) Christmas Lights switch on at Trinity Square Gateshead Credit: Tim McGuinness(Image: newcastle chronicle) Christmas Lights switch on at Trinity Square Gateshead Credit: Tim McGuinness(Image: newcastle chronicle) Christmas Lights switch on at Trinity Square Gateshead Credit: Tim McGuinness(Image: newcastle chronicle) Christmas Lights switch on at Trinity Square Gateshead Credit: Tim McGuinness(Image: newcastle chronicle) Christmas Lights switch on at Trinity Square Gateshead Credit: Tim McGuinness(Image: newcastle chronicle) Christmas Lights switch on at Trinity Square Gateshead Credit: Tim McGuinness(Image: newcastle chronicle) Christmas Lights switch on at Trinity Square Gateshead Credit: Tim McGuinness(Image: newcastle chronicle) Christmas Lights switch on at Trinity Square Gateshead Credit: Tim McGuinness(Image: newcastle chronicle) Christmas Lights switch on at Trinity Square Gateshead Credit: Tim McGuinness(Image: newcastle chronicle) Eva Coates, Jessica Dowd and Jessica Black who played Princess Anna at different stages during a Frozen-inspired performance at the switch-on of Gateshead Christmas lights. Credit: Andrea Black(Image: Andrea Black)


virus USUV Usutu M., A., Nile West G., H., N., S., T., encephalitis J., P., substitutions human R., F., infection (–) Italy nucleotide protein Dis. Europe V., Virol. strains Germany assay birds Austria Nowotny acid amino strain C., Japanese species Bakonyi L., Weissenböck analysis including sequence viral Africa African B., Eurasian Figure Spain WNV important mosquitoes sequenced (–), D., E., Infect. USUV-specific flaviviruses genome reported showed using Bologna- CAR- Emerg. However, K., Microbiol. Z., cells common flavivirus sequences studies European JEV Table Vet. based genetic isolated polyprotein strains, surveillance wild Flavivirus NS, Nucleotide Sambri [./eid.] [./journal.pone.] associated avian blood cellular emergence fever infections mosquito precursor proteins related strains. virus, AGP Barkedji- Culex E.A., Gaibani Gen. Gould I., Italy, RT-PCR South Switzerland Turdus USUV-related Vector case completely detection developed different positions potential replication response role similar vaccine viruses A.A., BATUSUTU-BNI Bonilauri Borne CAR-, Cavrini Chvala Cx. Detection Eastern Europe, Europe. Hubálek Lussy M.A., Med. MeiseH- Murray O., Pierro Republic Rossini Senegal Trop. U., Valley Virus Zoonotic [./vbz..] antibodies bird blackbirds complete considered cross-reactivity diagnostic distinct diversity flaviviruses, genus identity infected neuroinvasive neutralizing observed owl pipiens real-time region samples serological shown structural tropism Africa, Albieri Am. Asian Bellini Boye C.S., Calzolari Comparison Czech Dengue Diallo Emergence Euro. H.W., Hungary Hyg. Jöst Kolodziejek M.P., NSA, NSB, Nikolay Phylogenetic Res. Rudolf Sall Savini Schmidt-Chanasit Surveill. USUV, UTRs VA, VI, W., WNV, YH, [./j.vetmic...] central cerebrospinal closely competence countries, cycle demonstrated detected domain envelope evidence fluid humans immune life listed man mice neavei neutralization open pathway phylogenetic plaque prevalence previously programs rash reduction reference relationship relative risk species, subsequent threat type various vector


Rating * * * * * 21 Rs/km Estimated ~903 Rs NearestCab 3.4 Km Reach in 10 Min
Rating * * * * * 21 Rs/km Estimated ~903 Rs NearestCab 3.4 Km Reach in 10 Min
Rating * * * * * 21 Rs/km Estimated ~903 Rs NearestCab 3.4 Km Reach in 10 Min
Rating * * * * * 21 Rs/km Estimated ~903 Rs NearestCab 3.4 Km Reach in 10 Min


On the same day that President Obama announces sanctions against Russia in retaliation for its interference in the 2016 election, national security adviser- designate Lt. Gen. Flynn places five phone calls to the Russian ambassador. These calls were apparently on unsecured lines, and monitored by U.S. intelligence agencies.
Source: Washington Post


This example shows how to load a static KML file and assign visual mappings that draw from data stored in the KML file. We also show how additional data outside the KML file can be linked in as well, in this case to color the countries.


--- layout: default nav: attributes > ic-prompt ---
ic-prompt
- The Prompt AttributeThe ic-prompt
attribute tells Intercooler to prompt the user for input before issuing an AJAX
request. The input is included in the ic-prompt-value
parameter of the request. If you wish
to change this, you can use the ic-prompt-name
attribute to override it.
If the user cancels the prompt, no request will be made.
The value of the ic-prompt
attribute should be a string prompting the user for input.
This attribute may be placed on parent elements, allowing you to specify behavior across multiple elements.
The ic-prompt
attribute has no effect on dependencies.
<button ic-post-to="/target_url" ic-prompt="What's your name?">Click Me!</button>


Performance Test
Basic responsive-grid demo
Simple Responsive Grid with No Gutter
Responsive column
Responsive column
Responsive column
Responsive column
Responsive column
Responsive column
Responsive Grid with Custom Gutter
Responsive column
Responsive column
Responsive column
Responsive column
Responsive column
Responsive column
Responsive Grid with Hidden Columns and Clear Floats
Responsive column (50% wide on large and extra-large screens)
Responsive column hidden on large screens
Responsive column print-only
Responsive column screen-only
Visible on an extra-small screen.
Visible on an small screen.
Visible on an medium screen.
Visible on an large screen.
Visible on an extra large screen.
Responsive Grid Relative to Parent Container
Parent Container
Visible in an extra-small parent (< 600px).
Visible in a small parent (> 600px and < 900px).
Visible on a medium screen (> 900px and < 1200px).
Visible on a large screen (> 1200px and < 1800px).
Visible on an extra-large screen (>= 1800px).
Responsive grid with Custom Breakpoints
Visible on an extra-small screen (< 1500px).
Visible on a small screen (> 1500px and < 2000px).
Visible on a medium screen (> 1500px and < 2000px).
Visible on a large screen (> 2000px and < 2500px).
Visible on an extra-large screen (>= 2500px).


By now you have seen many examples of the following kind:
A deck of cards consists of 26 red cards and 26 black cards. Three cards are drawn at random without replacement. What is the chance that they are all black?
You will be quick to answer $$ \frac{26}{52} \cdot \frac{25}{51} \cdot \frac{24}{50} $$
and you will be right. But where does that multiplication of three factors come from? The multiplication rule says only that if $A$ and $B$ are two events, then
$$ P(AB) = P(A)P(B \mid A) $$Can we just go ahead and extend it to three or more events, and if so, exactly how are we extending it?
The third factor in the product above is the conditional chance that the third card is red given that the first two cards were red. This suggests an extension of the multiplication rule, used by us without discussion and without proof in many calculations so far:
$$ P(A_1A_2 \ldots A_n) = P(A_1)P(A_2 \mid A_1) P(A_3 \mid A_1A_2)P(A_4 \mid A_1A_2A_3) \cdots P(A_n \mid A_1A_2 \ldots A_{n-1}) $$Let's prove this by induction. While it might seem a little pedantic, it's a good idea to develop skills that you can use to solidify the foundations of steps that are based on intuition.
We will start in the case $n=3$ to see what is going on. First notice that
$$ P(A_2A_3 \mid A_1) = \frac{P(A_1A_2A_3)}{P(A_1)} = \frac{P(A_1A_2)P(A_3 \mid A_1A_2)}{P(A_1)} = P(A_2 \mid A_1)P(A_3 \mid A_1A_2) $$This is just like the ordinary multiplication rule for the intersection of the two events $A_2$ and $A_3$, except that all the probabilities are also conditional given $A_1$.
And now
\begin{align*} P(A_1A_2A_3) &= P(A_1)P(A_2A_3 \mid A_1) ~~~ \text{(multiplication rule applied to }A_1 \text{ and } A_2A_3 \text{)} \\ &= P(A_1)P(A_2 \mid A_1)P(A_3 \mid A_1A_2) ~~~ \text{(we just proved this)} \end{align*}So our result is true for $n=3$.
To prove it for all positive integers, first assume the induction hypothesis that the result is true for $n$:
$$ P(A_1A_2 \ldots A_n) = P(A_1)P(A_2 \mid A_1) P(A_3 \mid A_1A_2) \cdots P(A_n \mid A_1A_2 \ldots A_{n-1}) $$And then show that it is true for $n+1$:
\begin{align*} & P(A_1A_2 \ldots A_nA_{n+1}) \\ &= P(A_1)P(A_2 \mid A_1) P(A_3 \mid A_1A_2) \cdots P(A_n \mid A_1A_2 \ldots A_{n-1}) P(A_{n+1} \mid A_1A_2 \ldots A_{n-1}A_n) \end{align*}The induction relies on treating $A_1A_2 \dots A_nA_{n+1}$ as the intersection of two events: $B_n = A_1A_2 \ldots A_n$ and $A_{n+1}$. Moves like this are use in many induction proofs of results about chances of intersections and unions.
Now
\begin{align*} P(A_1A_2 \ldots A_{n+1}) &= P(B_nA_{n+1}) \\ &= P(B_n)P(A_{n+1} \mid B_n) ~~~ \text{(multiplication rule)} \\ &= P(A_1A_2 \ldots A_n)P(A_{n+1} \mid A_1A_2 \ldots A_n) ~~~ \text{(definition of } B_n \text{)} \\ &= P(A_1)P(A_2 \mid A_1) P(A_3 \mid A_1A_2) \cdots P(A_n \mid A_1A_2 \ldots A_{n-1})P(A_{n+1} \mid A_1A_2 \ldots A_n) \end{align*}by the induction hypothesis. Done!
You shouldn't feel you have to have proved every single result that you use, specially when they arise naturally as properties of proportions. This section shows you that there are straightforward if laborious ways of establising such results mathematically.
However, what is "natural" and what is correct are not always the same. Here is an example.
We have defined the independence of two events to mean that the chance of one doesn't change if you are told that other has happened; $A$ and $B$ are independent means that
$$ P(B \mid A) = P(B) ~~~ \text{or equivalently,} ~~~ P(AB) = P(A)P(B) $$Now suppose you have three events $A, B$, and $C$, and suppose each pair of them is independent by the defintion above. That is, $A$ is independent of $B$, $A$ is independent of $C$, and $B$ is independent of $C$.
This is called pairwise independence, and you might be tempted to use it as a definition of independence of three events. But it doesn't quite work.
In a group of three people, let $B_{ij}$ be the event that Persons $i$ and $j$ have the same birthday, and let $B_{123}$ be the event that all three have the same birthday. Under the assumptions of randomness that we made for the classical Birthday Problem, we know that
$$ P(B_{12}) = \frac{1}{365} = P(B_{23}) = P(B_{13}) $$and $$ P(B_{12} B_{23}) = P(B_{123}) = \frac{1}{365} \cdot \frac{1}{365} = P(B_{12})P(B_{23}) $$
So $B_{12}$ and $B_{23}$ are independent. In the same way you can show that $B_{12}$ and $B_{13}$ are independent, as are $B_{23}$ and $B_{13}$. Thus the three events $B_{12}$, $B_{13}$, and $B_{23}$ are pairwise independent.
But $$ P(B_{13} \mid B_{12}B_{23}) = 1 \ne P(B_{13}) $$
Given that Persons 1 and 2 have the same birthday and that Persons 2 and 3 have the same birthday, there is no randomness left in whether Persons 1 and 3 have the same birthday – they just do. Information about the other two pairs affects the chance of $B_{13}$.
This goes against what independence should mean, and points out to us that when we have more than two events we have to be careful about the defining independence.
Events $A_1, A_2, \ldots A_n$ are mutually independent (or independent for short) if given that any subset of the events has occurred, the conditional chances of all other subsets remain unchanged.
That's quite a mouthful. In practical terms it means that it doesn't matter which of the events you know have happened; chances involving the remaining events are unchanged.
In terms of random variables, $X_1, X_2, \ldots , X_n$ are independent if given the values of any subset, chances of events determined by the remaining variables are unchanged.
In practice, this just formalizes statements such as "results of different tosses of a coin are independent" or "draws made at random with replacement are independent".
Try not to become inhibited by the formalism. Notice how the theory not only supports intuition but also develops it. You can expect your probabilistic intuition to be much sharper at the end of this course than it is now!


Survey Form
Let us know how we can improve Free Code Camp.
*
Name:
*
Email:
*
Age:
Which option best describes your current role?
Student
Full Time Learner
Full Time Job
Prefer not to say
Other
*
How likely is that you would recommend freeCodeCamp to a friend?
Definitely
Maybe
Not Sure
What do you like most in FCC:
Select an option
Challenges
Projects
Community
Open Source
Things that should be improved in the future (Check all that apply):
Font-end Projects
Back-end Projects
Data Visualization
Challenges
Open Source Community
Gitter Help Rooms
Videos
City Meetups
Wiki
Forum
Additional Courses
Any Comments or Suggestions?
Submit


| Version: | 0.0.0 |
|---|---|
| Manual group: | Universal-ctags |
| Manual section: | 1 |
The ctags and etags programs (hereinafter collectively referred to as ctags, except where distinguished) generate an index (or "tag") file for a variety of language objects found in source file(s). This tag file allows these items to be quickly and easily located by a text editor or other utilities (client tools). A tag signifies a language object for which an index entry is available (or, alternatively, the index entry created for that object).
Alternatively, ctags can generate a cross reference file which lists, in human readable form, information about the various language objects found in a set of source files.
Tag index files are supported by numerous editors, which allow the user to locate the object associated with a name appearing in a source file and jump to the file and line which defines the name. See the manual of your favorite editor about utilizing ctags command and the tag index files in the editor.
ctags is capable of generating different kinds of tags for each of many different languages. For a complete list of supported languages, the names by which they are recognized, and the kinds of tags which are generated for each, see the --list-languages and --list-kinds-full options.
This man page describes Universal-ctags, an implementation of ctags derived from Exuberant-ctags. The major incompatible changes between Universal-ctags and Exuberant-ctags are enumerated in ctags-incompatibilities(7).
One of the advantages of Exuberant-ctags is that it allows a user to define a new parser from the command line. Extending this capability is one of the major features of Universal-ctags. ctags-optlib(7) describes how the capability is extended.
Newly introduced experimental features are not explained here. If you are interested in such features and ctags internals, visit https://docs.ctags.io/en/latest/.
Despite the wealth of available options, defaults are set so that ctags is most commonly executed without any options (e.g. "ctags *", or "ctags -R"), which will create a tag file in the current directory for all recognized source files. The options described below are provided merely to allow custom tailoring to meet special needs.
Note that spaces separating the single-letter options from their parameters are optional.
Note also that the boolean parameters to the long form options (those beginning with "--" and that take a "[=yes|no]" parameter) may be omitted, in which case "=yes" is implied. (e.g. --sort is equivalent to --sort=yes). Note further that "=1", "=on", and "=true" are considered synonyms for "=yes", and that "=0", "=off", and "=false" are considered synonyms for "=no".
Some options are either ignored or useful only when used while running in etags mode (see -e option). Such options will be noted.
Most options may appear anywhere on the command line, affecting only those files which follow the option. A few options, however, must appear before the first file name and will be noted as such.
Options taking language names will accept those names in either upper or lower case. See the --list-languages option for a complete list of the built-in language names.
Some options take one-letter flags as parameters (e.g. --kinds-<LANG> option). Specifying just letters help a user create a complicated command line quickly. However, a command line including sequences of one-letter flags becomes difficult to understand.
Universal-ctags accepts long-name flags in addition to such one-letter flags. The long-name and one-letter flags can be mixed in an option parameter by surrounding each long-name by braces. Thus, for an example, the following three notations for --kinds-C option have the same meaning:
--kinds-C=+pLl --kinds-C=+{prototype}{label}{local} --kinds-C=+{prototype}L{local}
Note that braces may be meta characters in your shell. Put single quotes in such case.
--list-... options shows one-letter flags and associated long-name flags.
Universal-ctags introduces many --list-... options that provide the internal data of Universal-ctags. Both users and client tools may use the data. --with-list-header and --machinable options adjust the output of the most of --list-... options.
The default setting (--with-list-header=yes and --machinable=no) is for using interactively from a terminal. The header that explains the meaning of columns is simply added to the output, and each column is aligned in all lines. The header line starts with a hash ('#') character.
For scripting in a client tool, --with-list-header=no and --machinable=yes may be useful. The header is not added to the output, and each column is separated by tab characters.
Note the order of columns will change in the future release. However, labels in the header will not change. So by scanning the header, a client tool can find the index for the target column.
ctags has more options than listed here. Options starting with an underscore character, such as --_echo=msg, are not listed here. They are experimental or for debugging purpose.
Specifies a list of identifiers which are to be specially handled while parsing C and C++ source files. This option is specifically provided to handle special cases arising through the use of preprocessor macros. When the identifiers listed are simple identifiers, these identifiers will be ignored during parsing of the source files. If an identifier is suffixed with a '+' character, ctags will also ignore any parenthesis-enclosed argument list which may immediately follow the identifier in the source files. If two identifiers are separated with the '=' character, the first identifiers is replaced by the second identifiers for parsing purposes. The list of identifiers may be supplied directly on the command line or read in from a separate file. If the first character of identifier-list is '@', '.' or a pathname separator ('/' or '\'), or the first two characters specify a drive letter (e.g. "C:"), the parameter identifier-list will be interpreted as a filename from which to read a list of identifiers, one per input line. Otherwise, identifier-list is a list of identifiers (or identifier pairs) to be specially handled, each delimited by either a comma or by white space (in which case the list should be quoted to keep the entire list as one command line argument). Multiple -I options may be supplied. To clear the list of ignore identifiers, supply a single dash ("-") for identifier-list.
This feature is useful when preprocessor macros are used in such a way that they cause syntactic confusion due to their presence. Indeed, this is the best way of working around a number of problems caused by the presence of syntax-busting macros in source files (see "CAVEATS"). Some examples will illustrate this point.
int foo ARGDECL4(void *, ptr, long int, nbytes)
In the above example, the macro "ARGDECL4" would be mistakenly interpreted to be the name of the function instead of the correct name of "foo". Specifying "-I ARGDECL4" results in the correct behavior.
/* creates an RCS version string in module */ MODULE_VERSION("$Revision$")
In the above example the macro invocation looks too much like a function definition because it is not followed by a semicolon (indeed, it could even be followed by a global variable definition that would look much like a K&R style function parameter declaration). In fact, this seeming function definition could possibly even cause the rest of the file to be skipped over while trying to complete the definition. Specifying "-I MODULE_VERSION+" would avoid such a problem.
CLASS Example { // your content here };
The example above uses "CLASS" as a preprocessor macro which expands to something different for each platform. For instance CLASS may be defined as "class __declspec(dllexport)" on Win32 platforms and simply "class" on UNIX. Normally, the absence of the C++ keyword "class" would cause the source file to be incorrectly parsed. Correct behavior can be restored by specifying "-I CLASS=class".
Adds ('+') or removes ('-') an alias pattern to a language specified with <LANG>. ctags refers to the alias pattern in "Determining file language" stage.
The parameter aliasPattern is not a list. Use this option multiple times in a command line to add or remove multiple alias patterns.
To restore the default language aliases, specify "default" as the parameter aliasPattern. Using "all" for <LANG> has meaning in following two cases:
Add pattern to a list of excluded files and directories. This option may be specified as many times as desired. For each file name considered by ctags, each pattern specified using this option will be compared against both the complete path (e.g. some/path/base.ext) and the base name (e.g. base.ext) of the file, thus allowing patterns which match a given file name irrespective of its path, or match only a specific path. If appropriate support is available from the runtime library of your C compiler, then pattern may contain the usual shell wildcards (not regular expressions) common on Unix (be sure to quote the option parameter to protect the wildcards from being expanded by the shell before being passed to ctags; also be aware that wildcards can match the slash character, '/'). You can determine if shell wildcards are available on your platform by examining the output of the --list-features option, which will include "wildcards" in the compiled feature list; otherwise, pattern is matched against file names using a simple textual comparison.
If pattern begins with the character '@', then the rest of the string is interpreted as a file name from which to read exclusion patterns, one per line. If pattern is empty, the list of excluded patterns is cleared.
Note that at program startup, the default exclude list contains names of common hidden and system files, patterns for binary files, and directories for which it is generally not desirable to descend while processing the --recurse option. To see the list of built-in exclude patterns, use --list-excludes.
See also the description for --exclude-exception= option.
Add pattern to a list of included files and directories. The pattern affects the files and directories that are excluded by the pattern specified with --exclude= option.
For an example, you want @CTAGS_NAME_EXAMPLE@ to ignore all files under "foo" directory except "foo/main.c", use the following command line: "--exclude=foo/* --exclude-exception=foo/main.c". Don't forget shell quoting for '*'.
Determines the type of EX command used to locate tags in the source file. [Ignored in etags mode]
The valid values for type (either the entire word or the first letter is accepted) are:
Use only line numbers in the tag file for locating tags. This has four advantages:
However, this option has one significant drawback: changes to the source files can cause the line numbers recorded in the tag file to no longer correspond to the lines in the source file, causing jumps to some tags to miss the target definition by one or more lines. Basically, this option is best used when the source code to which it is applied is not subject to change. Selecting this option type causes the following options to be ignored: -BF.
Equivalent to --extras=[+|-]flags|*, which was introduced to make the option naming convention align to the other options like --kinds-<LANG>= and --fields=.
This option is kept for backward-compatibility with Exuberant-ctags.
Specifies whether to include extra tag entries for certain kinds of information. See also "Extras" subsection to know what are extras.
The parameter flags is a set of one-letter flags (and/or long-name flags), each representing one kind of extra tag entry to include in the tag file. If flags is preceded by either the '+' or '-' character, the effect of each flag is added to, or removed from, those currently enabled; otherwise the flags replace any current settings. All entries are included if '*' is given.
This --extras= option is for controlling extras common in all languages (or language-independent extras). Universal-ctags also supports language-specific extras. (See "Language-specific fields and extras" about the concept). Use --extras-<LANG>= option for controlling them.
The meaning of major extras is as follows (one-letter flag/long-name flag):
Include an extra class-qualified or namespace-qualified tag entry for each tag which is a member of a class or a namespace.
This may allow easier location of a specific tags when multiple occurrences of a tag name occur in the tag file. Note, however, that this could potentially more than double the size of the tag file.
The actual form of the qualified tag depends upon the language from which the tag was derived (using a form that is most natural for how qualified calls are specified in the language). For C++ and Perl, it is in the form "class::member"; for Eiffel and Java, it is in the form "class.member".
Note: Using backslash characters as separators forming qualified name in PHP. However, in tags output of Universal-ctags, a backslash character in a name is escaped with a backslash character. See tags(5) about the escaping.
Inquire the output of --list-extras option for the other minor extras.
Specifies whether to include extra tag entries for certain kinds of information for language <LANG>. Universal-ctags introduces language-specific extras. See "Language-specific fields and extras" about the concept. This option is for controlling them.
Specifies "all" as <LANG> to apply the parameter flags to all languages; all extras are enabled with specifying '*' as the parameter flags. If specifying nothing as the parameter flags (--extras-all=), all extras are disabled. These two combinations are useful for testing.
Check the output of the --list-extras=<LANG> option for the extras of specific language <LANG>.
Specifies which available extension fields are to be included in the tag entries (see "TAG FILE FORMAT" second, and "Fields" subsection , for more information).
The parameter flags is a set of one-letter flags (and/or long-name flags), each representing one type of extension field to include. Each letter or group of letters may be preceded by either '+' to add it to the default set, or '-' to exclude it. In the absence of any preceding '+' or '-' sign, only those fields explicitly listed in flags will be included in the output (i.e. overriding the default set). All fields are included if '*' is given. This option is ignored if the option --format=1 (legacy tag file format) has been specified.
This --fields= option is for controlling fields common in all languages (or language-independent fields). Universal-ctags also supports language-specific fields. (See "Language-specific fields and extras" about the concept). Use --fields-<LANG>= option for controlling them.
The meaning of major fields is as follows (one-letter flag/long-name flag):
Check the output of the --list-fields option for the other minor fields.
Specifies which language-specific fields are to be included in the entries of the tag file. Universal-ctags supports language-specific fields. (See "Language-specific fields and extras" about the concept). This option is for controlling them.
Specify "all" as <LANG> to apply the parameter flags to all fields; all fields are enabled with specifying '*' as the parameter flags. If specifying nothing as the parameter flags (--fields-all=), all fields are disabled. These two combinations are useful for testing.
Specifies a list of language-specific kinds of tags (or kinds) to include in the output file for a particular language, where <LANG> is case-insensitive and is one of the built-in language names (see the --list-languages option for a complete list). The parameter kinds is a group of one-letter flags (and/or long-name flags) designating kinds of tags (particular to the language) to either include or exclude from the output. The specific sets of flags recognized for each language, their meanings and defaults may be list using the --list-kinds-full option. Each letter or group of letters may be preceded by either '+' to add it to, or '-' to remove it from, the default set. In the absence of any preceding '+' or '-' sign, only those kinds explicitly listed in kinds will be included in the output (i.e. overriding the default for the specified language).
Specify '*' as the parameter to include all kinds implemented in <LANG> in the output. Furthermore if "all" is given as <LANG>, specification of the parameter kinds affects all languages defined in ctags. Giving "all" makes sense only when '*' or 'F' is given as the parameter kinds.
As an example for the C language, in order to add prototypes and external variable declarations to the default set of tag kinds, but exclude macros, use "--kinds-c=+px-d"; to include only tags for functions, use "--kinds-c=f".
Some kinds of C and C++ languages are synchronized; enabling (or disabling) a kind in one language enables the kind having the same one-letter and long-name in the other language. See also the description of MASTER column of --list-kinds-full.
Controls how file names are mapped to languages (see the --list-maps option). Each comma-separated map consists of the language name (either a built-in or user-defined language), a colon, and a list of file extensions and/or file name patterns. A file extension is specified by preceding the extension with a period (e.g. ".c"). A file name pattern is specified by enclosing the pattern in parentheses (e.g. "([Mm]akefile)").
If appropriate support is available from the runtime library of your C compiler, then the file name pattern may contain the usual shell wildcards common on Unix (be sure to quote the option parameter to protect the wildcards from being expanded by the shell before being passed to ctags). You can determine if shell wildcards are available on your platform by examining the output of the --list-features option, which will include "wildcards" in the compiled feature list; otherwise, the file name patterns are matched against file names using a simple textual comparison.
When mapping a file extension with --langmap option, it will first be unmapped from any other languages. (--map-<LANG> option provides more fine-grained control.)
If the first character in a map is a plus sign ('+'), then the extensions and file name patterns in that map will be appended to the current map for that language; otherwise, the map will replace the current map. For example, to specify that only files with extensions of .c and .x are to be treated as C language files, use "--langmap=c:.c.x"; to also add files with extensions of .j as Java language files, specify "--langmap=c:.c.x,java:+.j". To map makefiles (e.g. files named either "Makefile", "makefile", or having the extension ".mak") to a language called "make", specify "--langmap=make:([Mm]akefile).mak". To map files having no extension, specify a period not followed by a non-period character (e.g. ".", "..x", ".x.").
To clear the mapping for a particular language (thus inhibiting automatic generation of tags for that language), specify an empty extension list (e.g. "--langmap=fortran:"). To restore the default language mappings for a particular language, supply the keyword "default" for the mapping. To specify restore the default language mappings for all languages, specify "--langmap=default".
Note that file name patterns are tested before file extensions when inferring the language of a file. This order of Universal-ctags is different from Exuberant-ctags. See ctags-incompatibilities(7) for the background of this incompatible change.
Specifies the languages for which tag generation is enabled, with list containing a comma-separated list of language names (case-insensitive; either built-in or user-defined). If the first language of list is not preceded by either a '+' or '-', the current list (the current settings of enabled/disabled languages managed in ctags internally) will be cleared before adding or removing the languages in list. Until a '-' is encountered, each language in the list will be added to the current list. As either the '+' or '-' is encountered in the list, the languages following it are added or removed from the current list, respectively. Thus, it becomes simple to replace the current list with a new one, or to add or remove languages from the current list.
The actual list of files for which tags will be generated depends upon the language extension mapping in effect (see the --langmap option). Note that the most of all languages, including user-defined languages, are enabled unless explicitly disabled using this option. Language names included in list may be any built-in language or one previously defined with --langdef. The default is "all", which is also accepted as a valid argument. See the --list-languages option for a list of the all (built-in and user-defined) language names.
Note --languages= option works cumulative way; the option can be specified with different arguments multiple times in a command line.
Lists the extras recognized for either the specified language or all languages. See "Extras" subsection to know what are extras. all is used as default value if the option argument is omitted.
An extra can be enabled or disabled with --extras= for common extras in all languages, or --extras-<LANG>= for the specified language. These option takes one-letter flag or long-name flag as a parameter for specifying an extra.
The meaning of columns are as follows:
Lists the fields recognized for either the specified language or all languages. See "Fields" subsection to know what are fields. all is used as default value if the option argument is omitted.
A field can be enabled or disabled with --fields= for common fields in all languages, or --fields-<LANG>= for the specified language. These option takes one-letter flags and/or long-name flags as a parameter for specifying fields.
The meaning of columns are as follows:
Json type used in printing the value of field when "--output-format=json" is specified.
Following characters are used for representing types.
The representation of this field and the output format used in "--output-format=json" are still experimental.
Subset of --list-kinds-full. This option is kept for backward-compatibility with Exuberant-ctags.
This option prints only LETTER, DESCRIPTION, and ENABLED fields of --list-kinds-full output. However, the presentation of ENABLED column is different from that of --list-kinds-full option; "[off]" follows after description if the kind is disabled, and nothing follows if enabled. The most of all kinds are enabled by default.
The critical weakness of this option is that this option does not print the name of kind. Universal-ctags introduces --list-kinds-full because it considers that names are important.
This option does not work with --machinable nor --with-list-header.
Lists the tag kinds recognized for either the specified language or all languages, and then exits. See "Kinds" subsection to learn what kinds are. all is used as default value if the option argument is omitted.
Each kind of tag recorded in the tag file is represented by a one-letter flag, or a long-name flag. They are also used to filter the tags placed into the output through use of the --kinds-<LANG> option.
The meaning of columns are as follows:
The master parser controlling enablement of the kind. A kind belongs to a language (owner) in Universal-ctags; enabling and disabling a kind in a language has no effect on a kind in another language even if both kinds has the same one-letter flag and/or the same long-name flag. In other words, the namespace of kinds are separated by language.
However, Exuberant-ctags does not separate the kinds of C and C++. Enabling/disabling kindX in C language enables/disables a kind in C++ language having the same long-name flag with kindX. To emulate this behavior in Universal-ctags, a concept named "master parser" is introduced. Enabling/disabling some kinds are synchronized under the control of a master language.
$ ctags --kinds-C=+'{local}' --list-kinds-full \ | grep -E '^(#|C\+\+ .* local)' #LANGUAGE LETTER NAME ENABLED REFONLY NROLES MASTER DESCRIPTION C++ l local yes no 0 C local variables $ ctags --kinds-C=-'{local}' --list-kinds-full \ | grep -E '^(#|C\+\+ .* local)' #LANGUAGE LETTER NAME ENABLED REFONLY NROLES MASTER DESCRIPTION C++ l local no no 0 C local variables
You see "ENABLED" field of "local" kind of C++ language is changed Though "local" kind of C language is enabled/disabled. If you swap the languages, you see the same result.
Lists the names of the languages understood by ctags, and then exits. These language names are case insensitive and may be used in many other options like --language-force, --languages, --kinds-<LANG>, --regex-<LANG>, and so on.
Each language listed is disabled if followed by "[disabled]". To use the parser for such a language, specify the language as an argument of --languages=+ option.
This option does not work with --machinable nor --with-list-header.
Lists file name patterns and the file extensions which associate a file name with a language for either the specified language or all languages, and then exits. See the --langmap option, and "Determining file language", above. all is used as default value if the option argument is omitted.
To list the file extensions or file name patterns individually, use --list-map-extensions or --list-map-patterns option. See the --langmap option, and "Determining file language", above.
This option does not work with --machinable nor --with-list-header.
List the roles for either the specified language or all languages. all is used as default value if the option argument is omitted. If the parameter kinds is given after the parameter language or all with concatenating with '.', list only roles defined in the kinds. Both one-letter flags and long name flags surrounded by braces are acceptable as the parameter kinds.
The meaning of columns are as follows:
This option provides the way to control mapping(s) of file names to languages in a more fine-grained way than --langmap option.
In ctags, more than one language can map to a file name pattern or file extension (N:1 map). Alternatively, --langmap option handle only 1:1 map, only one language mapping to one file name pattern or file extension. A typical N:1 map is seen in C++ and ObjectiveC language; both languages have a map to ".h" as a file extension.
A file extension is specified by preceding the extension with a period (e.g. ".c"). A file name pattern is specified by enclosing the pattern in parentheses (e.g. "([Mm]akefile)"). A prefixed plus ('+') sign is for adding, and minus ('-') is for removing. No prefix means replacing the map of <LANG>.
Unlike --langmap, extension (or pattern) is not a list. --map-<LANG> takes one extension (or pattern). However, the option can be specified with different arguments multiple times in a command line.
Read additional options from file or directory.
ctags searches pathname in optlib path list first. If ctags cannot find a file or directory in the list, ctags reads a file or directory at the specified pathname.
If a file is specified, it should contain one option per line. If a directory is specified, files suffixed with ".ctags" under it are read in alphabetical order.
As a special case, if "--options=NONE" is specified as the first option on the command line, preloading is disabled; the option will disable the automatic reading of any configuration options from either a file or the environment (see "FILES").
Specifies the encoding of the tags file. Universal-ctags converts the encoding of input files from the encoding specified by --input-encoding=encoding to this encoding.
In addition encoding is specified at the top the tags file as the value for the TAG_FILE_ENCODING pseudo-tag. The default value of encoding is UTF-8.
Cutoff patterns of tag entries after N characters. Disable by setting to 0 (default is 96). Specifying 0 as N results no truncation.
An input source file with long lines and multiple tag matches per line can generate an excessively large tags file with an unconstrained pattern length. For example, running ctags on a minified JavaScript source file often exhibits this behaviour.
The truncation avoids cutting in the middle of a UTF-8 code point spanning multiple bytes to prevent writing invalid byte sequences from valid input files. This handling allows for an extra 3 bytes above the configured limit in the worse case of a 4 byte code point starting right before the limit. Please also note that this handling is fairly naive and fast, and although it is resistant against any input, it requires a valid input to work properly; it is not guaranteed to work as the user expects when dealing with partially invalid UTF-8 input. This also partially affect non-UTF-8 input, if the byte sequence at the truncation length looks like a multibyte UTF-8 sequence. This should however be rare, and in the worse case will lead to including up to an extra 3 bytes above the limit.
Put "UCTAGS" as prefix for the name of fields newly introduced in Universal-ctags.
Some fields are newly introduced in Universal-ctags and more will be introduced in the future. Other tags generators may also introduce their specific fields.
In such a situation, there is a concern about conflicting field names; mixing tags files generated by multiple tags generators including Universal-ctags is difficult. This option provides a workaround for such station.
$ ctags --fields='{line}{end}' -o - hello.c main hello.c /^main(int argc, char **argv)$/;" f line:3 end:6 $ ctags --put-field-prefix --fields='{line}{end}' -o - /tmp/hello.c main /tmp/hello.c /^main(int argc, char **argv)$/;" f line:3 UCTAGSend:6
In the above exapmle, the prefix is put to "end" field which is newly introduced in Universal-ctags.
Prints statistics about the source files read and the tag file written during the current invocation of ctags. This option is off by default. This option must appear before the first file name.
The extra value prints parser specific statistics for parsers gathering such information.
As ctags considers each source file name in turn, it tries to determine the language of the file by applying tests described in "Determining file language".
If a language was identified, the file is opened and then the appropriate language parser is called to operate on the currently open file. The parser parses through the file and adds an entry to the tag file for each language object it is written to handle. See "TAG FILE FORMAT", below, for details on these entries.
This implementation of ctags imposes no formatting requirements on C code as do legacy implementations. Older implementations of ctags tended to rely upon certain formatting assumptions in order to help it resolve coding dilemmas caused by preprocessor conditionals.
In general, ctags tries to be smart about conditional preprocessor directives. If a preprocessor conditional is encountered within a statement which defines a tag, ctags follows only the first branch of that conditional (except in the special case of "#if 0", in which case it follows only the last branch). The reason for this is that failing to pursue only one branch can result in ambiguous syntax, as in the following example:
#ifdef TWO_ALTERNATIVES struct { #else union { #endif short a; long b; }
Both branches cannot be followed, or braces become unbalanced and ctags would be unable to make sense of the syntax.
If the application of this heuristic fails to properly parse a file, generally due to complicated and inconsistent pairing within the conditionals, ctags will retry the file using a different heuristic which does not selectively follow conditional preprocessor branches, but instead falls back to relying upon a closing brace ("}") in column 1 as indicating the end of a block once any brace imbalance results from following a #if conditional branch.
ctags will also try to specially handle arguments lists enclosed in double sets of parentheses in order to accept the following conditional construct:
extern void foo __ARGS((int one, char two));
Any name immediately preceding the "((" will be automatically ignored and the previous name will be used.
C++ operator definitions are specially handled. In order for consistency with all types of operators (overloaded and conversion), the operator name in the tag file will always be preceded by the string "operator " (i.e. even if the actual operator definition was written as "operator<<").
After creating or appending to the tag file, it is sorted by the tag name, removing identical tag lines.
Unless the --language-force option is specified, the language of each source file is automatically selected based upon a mapping of file names to languages. The mappings in effect for each language may be displayed using the --list-maps option and may be changed using the --langmap or --map-<LANG> options.
If the name of a file is not mapped to a language, ctags tries to heuristically guess the language for the file by inspecting its content. See "Determining file language".
All files that have no file name mapping and no guessed parser are ignored. This permits running ctags on all files in either a single directory (e.g. "ctags *"), or on all files in an entire source directory tree (e.g. "ctags -R"), since only those files whose names are mapped to languages will be scanned.
The same extensions are mapped to multiple parsers. For example, ".h" are mapped to C++, C and ObjectiveC. These mappings can cause issues. ctags tries to select the proper parser for the source file by applying heuristics to its content, however it is not perfect. In case of issues one can use --language-force=language, --langmap=map[,map[...]], or the --map-<LANG>=-pattern|extension options. (Some of the heuristics are applied whether --guess-language-eagerly is given or not.)
If ctags cannot select a parser from the mapping of file names, various heuristic tests are conducted to determine the language:
The first line of the file is checked to see if the file is a "#!" script for a recognized language. ctags looks for a parser having the same name.
If ctags finds no such parser, ctags looks for the name in alias lists. For example, consider if the first line is "#!/bin/sh". Though ctags has a "shell" parser, it doesn't have a "sh" parser. However, "sh" is listed as an alias for "shell", therefore ctags selects the "shell" parser for the file.
An exception is "env". If "env" is specified, ctags reads more lines to find real interpreter specification.
To display the list of aliases, use --list-aliases option. To add/remove an item to/from the list, use the --alias-<LANG>=[+|-]aliasPattern option.
The Emacs editor has multiple editing modes specialized for programming languages. Emacs can recognize a marker called modeline in a file and utilize the marker for the mode selection. This heuristic test does the same as what Emacs does.
ctags treats MODE as a name of interpreter and applies the same rule of "interpreter" testing if the first line has one of the following patterns:
-*- mode: MODE -*-
or
-*- MODE -*-
Emacs editor recognizes another marker at the end of file as a mode specifier. This heuristic test does the same as what Emacs does.
ctags treats MODE as a name of an interpreter and applies the same rule of "interpreter" heuristic testing, if the lines at the tail of the file have the following pattern:
Local Variables: ... mode: MODE ... End:
3000 characters are sought from the end of file to find the pattern.
Like the modeline of the Emacs editor, Vim editor has the same concept. ctags treats TYPE as a name of interpreter and applies the same rule of "interpreter" heuristic testing if the last 5 lines of the file have one of the following patterns:
filetype=TYPE
or
ft=TYPE
Looking into the file contents is a more expensive operation than file name matching. So ctags runs the testings in limited conditions. "interpreter" testing is enabled only when a file is an executable or the --guess-language-eagerly (-G in short) option is given. The other heuristic tests are enabled only when -G option is given.
The --print-language option can be used just to print the results of parser selections for given files instead of generating a tags file.
Examples:
$ ctags --print-language config.h.in input.m input.unknown config.h.in: C++ input.m: MatLab input.unknown: NONE
NONE means that ctags does not select any parser for the file.
A tag is an index for a language object. The concept of a tag and related items in Exuberant-ctags are refined and extended in Universal-ctags.
A tag is categorized into definition tags or reference tags. In general, Exuberant-ctags only tags definitions of language objects: places where newly named language objects are introduced. Universal-ctags, on the other hand, can also tag references of language objects: places where named language objects are used. However, support for generating reference tags is new and limited to specific areas of specific languages in the current version.
A tag can record various information, called fields. The essential fields are: name of language objects, input, pattern, and line. input: is the name of source file where name: is defined or referenced. pattern: can be used to search the name in input:. line is the line number where name: is defined or referenced in input:.
ctags offers extension fields. See also the descriptions of --list-fields option and --fields option.
kind: is a field which represents the kind of language object specified by a tag. Kinds used and defined are very different between parsers. For example, C language defines "macro", "function", "variable", "typedef", etc. See also the descriptions of --list-kinds-full option and --kinds-<LANG> option.
Generally, ctags tags only language objects appearing in source files, as is. In other words, a value for a name: field should be found on the source file associated with the name:. An "extra" type tag (extra) is for tagging a language object with a processed name, or for tagging something not associated with a language object. A typical extra tag is "qualified", which tags a language object with a class-qualified or scope-qualified name.
The following example demonstrates the "qualified" extra tag.
package Bar; import Baz; class Foo { // ... }
For the above source file, ctags tags "Bar" and "Foo" by default. If the "qualified" extra is enabled from the command line (--extras=+q), then "Bar.Foo" is also tagged even though the string "Bar.Foo" is not in the source code.
See also the descriptions of --list-extras option and --extras option in "OPTIONS".
Role is a newly introduced concept in Universal-ctags. Role is a concept associated with reference tags, and is not implemented widely yet.
As described previously in "Kinds", the "kind" field represents the type of language object specified with a tag, such as a function vs. a variable. Specific kinds are defined for reference tags, such as the C++ kind "header" for header file, or Java kind "package" for package statements. For such reference kinds, a "roles" field can be added to distinguish the role of the reference kind. In other words, the "kind" field identifies the "what" of the language object, whereas the "roles" field identifies the "how" of a referenced language object. Roles are only used with specific kinds.
For example, for the source file used for demonstrating in the "Extras" subsection, "Baz" is tagged as a reference tag with kind "package" and with role "imported". Another example is for a C++ "header" kind tag, generated by "#include" statements: the roles:system or roles:local fields will be added depending on whether the include file name begins with "<" or not.
See also the descriptions of --list-roles option.
Exuberant-ctags has the concept of "fields" and "extras". They are common between parsers of different languages. Universal-ctags extends this concept by providing language-specific fields and extras.
When not running in etags mode, each entry in the tag file consists of a separate line, each looking like this in the most general case:
tag_name<TAB>file_name<TAB>ex_cmd;"<TAB>extension_fields
The fields and separators of these lines are specified as follows:
- tag name
- single tab character
- name of the file in which the object associated with the tag is located
- single tab character
- EX command used to locate the tag within the file; generally a search pattern (either /pattern/ or ?pattern?) or line number (see --excmd). Tag file format 2 (see --format) extends this EX command under certain circumstances to include a set of extension fields (described below) embedded in an EX comment immediately appended to the EX command, which leaves it backward-compatible with original vi(1) implementations.
A few special tags are written into the tag file for internal purposes. These tags are composed in such a way that they always sort to the top of the file. Therefore, the first two characters of these tags are used a magic number to detect a tag file for purposes of determining whether a valid tag file is being overwritten rather than a source file.
Note that the name of each source file will be recorded in the tag file exactly as it appears on the command line. Therefore, if the path you specified on the command line was relative to the current directory, then it will be recorded in that same manner in the tag file. See, however, the --tag-relative option for how this behavior can be modified.
Extension fields are tab-separated key-value pairs appended to the end of the EX command as a comment, as described above. These key value pairs appear in the general form "key:value". Their presence in the lines of the tag file are controlled by the --fields option. The possible keys and the meaning of their values are as follows:
In addition, information on the scope of the tag definition may be available, with the key portion equal to some language-dependent construct name and its value the name declared for that construct in the program. This scope entry indicates the scope in which the tag was found. For example, a tag generated for a C structure member would have a scope looking like "struct:myStruct".
Vi will, by default, expect a tag file by the name "tags" in the current directory. Once the tag file is built, the following commands exercise the tag indexing feature:
Emacs will, by default, expect a tag file by the name "TAGS" in the current directory. Once the tag file is built, the following commands exercise the tag indexing feature:
For more commands, see the Tags topic in the Emacs info document.
NEdit version 5.1 and later can handle the new extended tag file format (see --format). To make NEdit use the tag file, select "File->Load Tags File". To jump to the definition for a tag, highlight the word, then press Ctrl-D. NEdit 5.1 can read multiple tag files from different directories. Setting the X resource nedit.tagFile to the name of a tag file instructs NEdit to automatically load that tag file at startup time.
Because ctags is neither a preprocessor nor a compiler, use of preprocessor macros can fool ctags into either missing tags or improperly generating inappropriate tags. Although ctags has been designed to handle certain common cases, this is the single biggest cause of reported problems. In particular, the use of preprocessor constructs which alter the textual syntax of C can fool ctags. You can work around many such problems by using the -I option.
Note that since ctags generates patterns for locating tags (see the --excmd option), it is entirely possible that the wrong line may be found by your editor if there exists another source line which is identical to the line containing the tag. The following example demonstrates this condition:
int variable; /* ... */ void foo(variable) int variable; { /* ... */ }
Depending upon which editor you use and where in the code you happen to be, it is possible that the search pattern may locate the local parameter declaration in foo() before it finds the actual global variable definition, since the lines (and therefore their search patterns are identical). This can be avoided by use of the --excmd=n option.
ctags has more options than ls(1).
When parsing a C++ member function definition (e.g. "className::function"), ctags cannot determine whether the scope specifier is a class name or a namespace specifier and always lists it as a class name in the scope portion of the extension fields. Also, if a C++ function is defined outside of the class declaration (the usual case), the access specification (i.e. public, protected, or private) and implementation information (e.g. virtual, pure virtual) contained in the function declaration are not known when the tag is generated for the function definition. It will, however be available for prototypes (e.g. "--kinds-c++=+p").
No qualified tags are generated for language objects inherited into a class.
$XDG_CONFIG_HOME/ctags/*.ctags, or $HOME/.config/ctags/*.ctags if $XDG_CONFIG_HOME is not defeind (on other than MSWindows)
$HOME/.ctags.d/*.ctags
$HOMEDRIVE$HOMEPATH/ctags.d/*.ctags (on MSWindows only)
.ctags.d/*.ctags
ctags.d/*.ctags
If any of these configuration files exist, each will be expected to contain a set of default options which are read in the order listed when ctags starts, but before the CTAGS environment variable is read or any command line options are read. This makes it possible to set up personal or project-level defaults. It is possible to compile ctags to read an additional configuration file before any of those shown above, which will be indicated if the output produced by the --version option lists the "custom-conf" feature. Options appearing in the CTAGS environment variable or on the command line will override options specified in these files. Only options will be read from these files. Note that the option files are read in line-oriented mode in which spaces are significant (since shell quoting is not possible) but spaces at the beginning of a line are ignored. Each line of the file is read as one command line parameter (as if it were quoted with single quotes). Therefore, use new lines to indicate separate command-line arguments. A line starting with '#' is treated as a comment.
*.ctags files in a directory are loaded in alphabetical order.
See ctags-optlib(7) for defining (or extending) a parser in a configuration file.
See tags(5) for the format of tag files.
See ctags-incompatibilities(7) about known incompatible changes with Exuberant-ctags.
See ctags-client-tools(7) if you are interested in writing a tool for processing tags files.
The official Universal-ctags web site at:
Also ex(1), vi(1), elvis, or, better yet, vim, the official editor of ctags. For more information on vim, see the VIM Pages web site at:
Universal-ctags project https://ctags.io/
Darren Hiebert<EMAIL_ADDRESS>http://DarrenHiebert.com/
"Think ye at all times of rendering some service to every member of the human race."
"All effort and exertion put forth by man from the fullness of his heart is worship, if it is prompted by the highest motives and the will to do service to humanity."
-- From the Baha'i Writings
This version of ctags (Universal-ctags) derived from the repository, known as fishman-ctags, started by Reza Jelveh.
Some parsers are taken from tagmanager of Geany (https://www.geany.org/) project.
The fishman-ctags was derived from Exuberant-ctags.
Exuberant-ctags was originally derived from and inspired by the ctags program by Steve Kirkendall<EMAIL_ADDRESS>that comes with the Elvis vi clone (though virtually none of the original code remains).
Credit is also due Bram Moolenaar<EMAIL_ADDRESS>the author of vim, who has devoted so much of his time and energy both to developing the editor as a service to others, and to helping the orphans of Uganda.
The section entitled "HOW TO USE WITH GNU EMACS" was shamelessly stolen from the info page for GNU etags.


---
title: Home
---
Introduction to Smos
Smos is a purely functional semantic tree-based editor to replace Emacs' Org Mode for Getting Things Done.
In short:
-
What todoist would have been if it had been written by the people who wrote vim
-
Emacs' Org Mode but without the emacs around it


Add some effect to your photos with this simple website. This website is build from our first experience in web development.s


com.foo.ClassInComFoo.readonlyProperty
readonlyProperty:Number
This is docs for readonlyProperty of class in com.foo package
public function get readonlyProperty():Number


For security, this request was received from a laptop device using MacOS. If you did not request a password reset, please ignore this email or
contact support if you have questions
Thanks,
The EmailOctopus Team
Address Line 1,
Address Line 2,
Zip Code
You're receiving this email because you've requested a password reset. You can access your account here.


A non-empty zero-indexed array A consisting of N integers is given.
The leader of this array is the value that occurs in more than half of the elements of A.
An equi leader is an index S such that 0 ≤ S < N − 1 and two sequences A[0], A[1], ..., A[S] and A[S + 1], A[S + 2], ..., A[N − 1] have leaders of the same value.
For example, given array A such that:
A[0] = 4 A[1] = 3 A[2] = 4 A[3] = 4 A[4] = 4 A[5] = 2we can find two equi leaders:
- 0, because sequences: (4) and (3, 4, 4, 4, 2) have the same leader, whose value is 4.
- 2, because sequences: (4, 3, 4) and (4, 4, 2) have the same leader, whose value is 4.
The goal is to count the number of equi leaders.
Write a function:
def solution(A)
that, given a non-empty zero-indexed array A consisting of N integers, returns the number of equi leaders.
For example, given:
A[0] = 4 A[1] = 3 A[2] = 4 A[3] = 4 A[4] = 4 A[5] = 2the function should return 2, as explained above.
Assume that:
- N is an integer within the range [1..100,000];
- each element of array A is an integer within the range [−1,000,000,000..1,000,000,000].
Complexity:
- expected worst-case time complexity is O(N);
- expected worst-case space complexity is O(N), beyond input storage (not counting the storage required for input arguments).


{% autoescape off %}
Hi {{ name }},
Unfortunately, your verification request has been denied by the Alumni Programming Committee. If you believe this is a mistake, please resubmit another request and make sure all of your submitted information is accurate.
If you have any further concerns or questions, please contact conference.executive@uvsamidwest.org


Soldering Basics
Soldering is a process in wich two items are joined together by using a filler metal to hold the joint.
Soldering is a process in wich two items are joined together by using a filler metal to hold the joint.
The soldering project consisted in soldering a little prepared kit following the instructions. I decided to make the spinning wheel of LED's. Here are some images of my soldering and the project.


To view explanation, please click here.
To go back to main page, please click here.
| $\omega_0$ | ||
| $\gamma$ | ||
| $\max x$ | ||
| $F_0$ | ||
| $\omega_d$ | 7 | |
| $\Delta$ |
The graph aboves shows the solution x(t) to the following second-order differential equation:
$\frac{d^2x}{dt^2} = -\omega_0 x - \gamma \frac{dx}{dt} + F_0 \cos\omega_d t$
You can adjust the parameters with the sliders above to observe the behavior of the solution when the parameters are changed. The initial conditions are:
$x(0) = 0$ and $\frac{dx}{dt}(0) = 0$
The estimated numerical solution is obtained using Euler method.
Note: checkbox does not work with Edge


Wildcard pathnames can be used with directory but not with open, and return true from wild-pathname-p. When examining wildcard components of a wildcard pathname, conforming programs must be prepared to encounter any of the following additional values in any component or any element of a list that is the directory component:


Want to be more confident with your communications?
LearnLily Will Help!
Speech Analysis Live Report
Posture Feedback:
Voice Feedback:
Fly Solo Feedback:
Total Speech Duration:
How to Use LearnLily's Speech Analyser?
Click on the big 'Start Recording' button in the center.
Take a couple of deep breaths and be patient while our ML software loads.
If this is your first time using our platform, you will have to allow your browser camera and microphone permissions (don't fret, we don't store any of your data).
Once the model has successfully loaded, you will see the camera canvas in the middle.
Get comfortable and start speaking. While you do, you will get to see live feedback of your speech.
Once you're done, press the 'Stop Recording' button.
You'll see an overview of your overall speech and also the duration that you spoke for.
If you want to see a graphical representation of your speech and also download a .pdf version of your report, hit the 'Download Speech Report' button!
Last but not the least, Moira Rose is here to inspire you! :)


| DOSE: |
125 mg |
oral |
Pharms - Topiramate |
(pill / tablet) |
I was having headaches, & was given Topamax to try. I was taking Lortabs, & then Firoicet, both of those were great for killing pain, & also have nice recreational value. My Dr. isn't very liberal in prescribing meds. I told him the Fioricet worked, so he changed my scrip to topamax. I looked up a little info about topamax, & one of the side effects read may cause 'exaggerated feeling of well-being'. Sweet!
I was given 25 MG tabs. Take 1 in the AM, 1 in PM. So after a couple times of taking 25-50 MG, with no 'happiness', I decided to try 125 MG. This produced a noticible high, similar to an opioid, or Ultram. The effects were rather quick, 15-20 min. & lasted 4-5 hours. The one weird side effect was that my sense of taste was altered. I drank a Coke, & it tasted flat, & just strange. The taste alteration lasted for 3-4 days, & resumed to normal.
I don't know if Topamax is 'habit forming', but there is a bit of recreational value with this drug. I'm not sure why my Doc decided to change my scrip from Fioricet to Topamax, but either way, there is the additional pleasant floaty feeling associated with the drug.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


People
At Johns Hopkins, Krevans went on to become an instructor, an assistant professor, a professor of medicine, the assistant dean of student affairs, and, from 1968-1971, the dean for academic affairs. He was also an active research investigator and clinician, serving as the director of the Johns Hopkins Blood Bank (1953-1962) and as Physician-in-Chief for Baltimore City Hospitals (1963-1969).
Dr. Krevans came to UCSF in 1971 as Dean of the School of Medicine, a position he held until 1982. During his ten years as the Dean, he remained active in clinical practice by taking an annual rotation in hematology at Moffitt Hospital and the Cancer Research Institute, where he was also the Acting Director. Krevans devoted his sabbatical year, 1977-1978, to patient care, alternating as Acting Chief of Medicine at San Francisco General Hospital, working in a private group practice in Berkeley, and as a practicing internist in Bangor, Maine.
On July 1, 1982, Julius R. Krevans was appointed the fifth Chancellor of UCSF. During his time as Chancellor, he created the UCSF Health and Safety Policy Board in reaction to concerns within the UCSF hospital regarding policy, HIV, and the workplace. Under his leadership, UCSF attracted many women and minority students to careers in health sciences, and strengthened programs to reach out to the local community. Dr. Krevans retired from the Chancellor position in 1993. On his day of retirement, San Francisco Mayor Jordan designated May 19 as Julius R. Krevans Day.
Krevans has served on several boards and committees, including the board of the National Academy of Science Institute of Medicine, and the American Board of Internal Medicine. He served as a director of the Clinical Scholar Program, and of the James Picker, and Bank of America-Giannini Foundations. He was a member of the Association of American Physicians, the San Francisco Planning and Urban Renewal Association, and the San Francisco Zoological Society. He was also the Chairman of the American Board of Internal Medicine's Committee on the Humanistic Qualities in the Internist. From 1980-1981, he served as the Chairman of the Association of American Medical Colleges, helping develop public policy for the organization.
Dr. Krevans has received many awards and recognition for his work and achievements. In 1978, he was named Alumnus of the Year by his alma mater, the New York University School of Medicine. He received the American College of Cardiology Convocation Medal (1984), the Abraham Flexner Award (1984), an Honorary Degree of Doctor of Humane Letters from Rush University (1984), and the UCSF Medal in 1993. He was elected to Phi Beta Kappa and Alpha Omega Alpha, and made a Commander in the Order of Merit in the Republic of Italy on February 26, 1985 and a Master in the American College of Physicians.