Commits
- Commit:
83272dfee9eb5292ce21de55ebdbb3876a37fcb1
- From:
- Omar Polo <op@omarpolo.com>
- Date:
don't yyerror if we can't open the file
the global var file could still be NULL and yyerror would crash.
- Commit:
abc8801d6064304c627cd75ed1f8c585d51346de
- From:
- Omar Polo <op@omarpolo.com>
- Date:
typo
- Commit:
c74c70304decdc06d050ea4ef3aac1914d3908e0
- From:
- Omar Polo <op@omarpolo.com>
- Date:
drop leading T from token names
- Commit:
9a818eebc193a0f891c3fb57034bf6ad367e8d25
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sort tokens
- Commit:
f3966209e5941ee3139425c5e375d373c1026923
- From:
- Anna “CyberTailor” <cyber@sysrq.in>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
contrib/vim: add Syntastic integration
Error and warning messages are prefixed with "error: " and "warning: "
correspondingly to ease integration with automated tooling.
`yywarn' function added. Off-by-one line numbers in warnings are fixed.
Two error messages are reworded to avoid repeating like
"error: error in server directive" or "error: syntax error".
- Commit:
391825e3604deef4c9dc3267dc2b6c89fc79958a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
move parse_portno to gmid.c
it's used only to parse the -p flag. While there add check_port_num
to check the range for the port.
- Commit:
e3b2a0f8de7210c4d403cf4c30d956c34d8c9353
- From:
- Omar Polo <op@omarpolo.com>
- Date:
missing newline in deprecation notice
- Commit:
1bd706dc4150dbcb42d48b98854e46a78ceda861
- From:
- Omar Polo <op@omarpolo.com>
- Date:
drop unsigned
it causes a cascade of warnings on some architectures. Also, for what
we're doing here, the signed/unsigned property isn't important.
- Commit:
67f494057aa3a0a32cc4d948cff2f27ef9de2340
- From:
- Omar Polo <op@omarpolo.com>
- Date:
@-macros, rollback changes to strings and optional semicolons
* expand $-macros as string, only the new @-macros get expanded as-is
* rollback changes to characters allowed in bare strings
* optional semicolons in optnl, useful for readable @-macros
- Commit:
c39be742cf8348232f6a527b19c42f764e80aae0
- From:
- Omar Polo <op@omarpolo.com>
- Date:
parsing: bring lots of goodies from OpenBSD' parse.y
This allows to solve the problem with the \n in the grammar (before
two following macro declaration were treated as invalid. This also
brings in a nice `include' keyword.
- Commit:
efacb859a7ebc65cff1b51cff04cdc2aea3135e1
- From:
- Omar Polo <op@omarpolo.com>
- Date:
change (again) the env/param separator: use '='
Given that env/param are new features of this release, no support for
the "old" syntax is needed.
- Commit:
762b9b991f373e5077d7e49396af62a34fa1c1ff
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add => in env/param and `port' between hostname and port for fastcgi
In the same spite of the last commit, add the missing separators
between strings to avoid the auto-concat pitfalls. `=>' is used to
separate between `env' and `param' arguments, while for `fastcgi' the
keyword `port' is required between the hostname/ip address and the
port (if provided).
Since `env', `param' and `fastcgi' are all new stuff, there's no need
to keep compatibility.
- Commit:
ff954a3e7641e83cca043ecc30789132478c7acd
- From:
- Omar Polo <op@omarpolo.com>
- Date:
typo...
- Commit:
d19951cf0373f6217bce2f97489bc46d6a8837ef
- From:
- Omar Polo <op@omarpolo.com>
- Date:
rename `mime MIME EXT' to `map MIME to-ext EXT'
With the newish automatic string concatenation, options like `mime'
that accepts two strings as parameter start to become ambiguous: which
strings gets concatenated? Instead of trying to document in the
manpage which argument(s) is subject to string concatenation, do the
concat always and introduce a separator. In the case of mime,
`to-ext' now acts as a separator to distinguish. While there, also
use a new keyword because it sounds better.
It's dead-easy to upgrade to the new configuration, possibly with some
sed magic, but for the moment the old `mime' form is preserved: (with
a warning!) Will be dropped in the next release.
- Commit:
d93c819182ba6decf8f7f1787c6ba416f76c315a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
use bsearch to match the keywords
not that it's a bottleneck, but it's fancier this way.