summaryrefslogtreecommitdiffstats
path: root/misc
Commit message (Collapse)AuthorAgeFilesLines
* Fix test_issue_1418 to pass on 1-core VMBernhard M. Wiedemann2019-09-201-1/+1
| | | | | the previous assert would fail because on a 1-core VM, the 3 outputs were produced sequentially from top to bottom
* Remove trailing whitespace from all filesJan Niklas Hasse2019-04-171-0/+41
|
* ninja_syntax.py: remove unused has_path argumentAlex Vallee2019-01-301-1/+1
| | | The usage of the parameter was removed a long time ago and was never cleaned up. The argument is not provided in the test.
* Add OSX build on travis (#1502)Takuto Ikuta2018-11-171-1/+5
| | | Also make test script works for OSX script command.
* Allow disabling of escape code stripping, fix #1475Jan Niklas Hasse2018-11-131-5/+16
| | | | | Don't strip colors when CLICOLOR_FORCE is set to a non-zero value. This environment variable is also used by CMake's Make back-end.
* Make output_test.py independent of the environmentJan Niklas Hasse2018-11-071-2/+8
|
* Add test for #1418 (edge output should match status)Jan Niklas Hasse2018-11-051-0/+21
|
* Add script to test Ninja's outputJan Niklas Hasse2018-11-051-0/+61
| | | | First test checks for #1214.
* Merge pull request #1472 from Hi-Angel/masterJan Niklas Hasse2018-11-021-1/+1
|\ | | | | Fix wrong description of script installation
| * Fix wrong description of script installationKonstantin Kharlamov2018-09-281-1/+1
| | | | | | The described way of installation makes zsh fail with `_arguments:comparguments:325: can only be called from completion function`. Per [zsh documentation](https://github.com/zsh-users/zsh-completions/blob/master/zsh-completions-howto.org#telling-zsh-which-function-to-use-for-completing-a-command) the correct way is to use `$fpath`.
* | Misc typo fixes by https://github.com/codespell-project/codespell/Mo Zhou2018-09-062-3/+3
|/
* update ninja.vim version after bff884d55Nico Weber2018-04-051-2/+2
|
* Merge pull request #1356 from RedBeard0531/vim_syntaxNico Weber2018-04-051-5/+9
|\ | | | | Improve vim syntax definition
| * Improve vim syntax definitionMathias Stearn2017-11-091-5/+9
| | | | | | | | | | Only highlights comments where the ninja lexer would treat them as such. Also correctly scopes the rule- and pool-specific variables highlighting.
* | Support pool for Writer.build() in ninja_syntax.pyKareem Khazem2018-02-201-1/+3
|/ | | | | ninja_syntax.py now supports a pool being specified for individual builds, as well as rules.
* Make zsh completion use explicitly specified ninja filesMathias Stearn2017-05-181-1/+6
|
* Fix syntax error in misc/write_fake_manifests.pyJames Robinson2016-10-251-2/+2
| | | | This is used by manifest_parser_perftest
* enhance write_fake_manifest.pyFrank Benkstein2016-06-231-18/+71
| | | | | | | | | | | | | | | Add an option to write_fake_manifest.py to generate sources expected by the manifest. Also slightly adapt command lines to the called commands. Together these changes mean that generated manifest can actually be executed successfully on Linux and OSX. Also add command line options to to change the number of targets being generated and the seed for the random number generator. Example usage: # create build directory in fake/build, sources in fake/src $ python misc/write_fake_manifest.py -s ../src fake/build # execute build in fake/build $ ninja -C fake/build
* Make misc/measure.py compatible with python3KiYugadgeter2016-05-041-5/+7
|
* Add support for implicit outputs in ninja_syntax.py.Nicolas Despres2016-02-062-1/+13
|
* Teach zsh to complete intermediary targets.Nicolas Despres2015-12-241-3/+2
| | | | | | | | Bash completion script uses "-t targets all" to list the target which is faster than "-t targets" and reports intermediary targets (see the manual entry for the 'targets' tool). See commit fc135c45.
* Merge pull request #1042 from avallee/masterEvan Martin2015-12-062-2/+9
|\ | | | | Fix wrapping file paths in Writer.comment
| * Disable long word wrapping entirely in comments.Alex Vallée2015-11-272-10/+3
| | | | | | | | | | | | As pointed out by nico, we should unconditionally disable breaking of long words in comments. It is unlikely long words that are in comments should be split (like pathnames).
| * Fix indent in pull request #1042.Alex Vallee2015-11-121-1/+1
| |
| * Fix wrapping file paths in Writer.commentAlex Vallée2015-10-232-2/+16
| | | | | | | | | | | | | | | | Long file names, especially with hyphens will get incorrectly wrapped by the comment method. Pass has_path=True to prevent this type of wrapping. This is mainly so that longer path names can show up in comments on their on line without breaking them up.
* | Merge pull request #1047 from pykello/masterNico Weber2015-11-121-3/+2
|\ \ | | | | | | Speed-up bash target auto-complete.
| * | Speed-up bash target auto-complete.Hadi Moshayedi2015-10-311-3/+2
| |/ | | | | | | | | | | | | | | These speed-ups include: * Let compgen do the command substitution. Similar to https://lists.gnu.org/archive/html/bug-bash/2012-03/msg00115.html * Use "cut" instead of "awk" for separating fields.
* | Merge pull request #1046 from zed0/masterNico Weber2015-11-121-2/+1
|\ \ | | | | | | Speed up zsh target completion
| * | Speed up zsh target completionBen Falconer2015-10-301-2/+1
| |/
* | Update link to point to ninja-build.orgNico Weber2015-11-111-1/+1
| |
* | Make links point to org pageNico Weber2015-11-112-4/+4
|/
* Add notes on using afl-fuzz to HACKING.Nico Weber2015-03-1917-0/+21
|
* zsh-completion: remove use of 'head' with negative offsetFraser Cormack2014-12-201-1/+1
| | | | | | | | | | Some systems - like OSX - don't come with a version of head that supports a negative value for the -n flag. Such systems get a message such as this when tab-completing ninja's -d flag: ninja -dhead: illegal line count -- -1 Using sed instead should be more universally supported.
* Remove unneeded save-excursion.Fanael Linithien2014-11-241-22/+21
| | | | syntax-propertize-function is allowed to move the point and mark.
* Use lexical-binding.Fanael Linithien2014-11-231-1/+1
| | | | | There's no reason not to use lexical-binding when supporting only Emacs 24+. Its semantics are just that much saner.
* Add a Emacs 24 requirement.Fanael Linithien2014-11-231-0/+2
| | | | Only Emacs >= 24 has prog-mode.
* Correctly recognize a comment if the previous line is a comment ending in $.Fanael Linithien2014-11-231-2/+9
|
* Avoid putting properties past the end of the buffer.Fanael Linithien2014-11-231-1/+4
|
* Don't use dotted list syntax unless necessary.Fanael Linithien2014-11-231-4/+4
|
* Remove unnecessary regexp group.Fanael Linithien2014-11-231-2/+2
|
* Correctly recognize comments.Fanael Linithien2014-11-231-0/+17
|
* Set up a proper syntax table for ninja-mode.Fanael Linithien2014-11-231-5/+8
| | | | | | | | Since quotes are not meant to be treated as string delimiters, the syntax table is the place to tell Emacs so. This also means syntactic fontification can be reenabled and the font-lock keyword entry for comments removed.
* Set comment-start buffer-locally, not globally.Fanael Linithien2014-11-231-1/+1
|
* Use quasi-quoting instead of list+cons.Fanael Linithien2014-11-231-15/+14
|
* Reindent ninja-mode.el using Emacs.Fanael Linithien2014-11-231-16/+16
| | | | Emacs knows best how to indent Emacs Lisp.
* Use double semicolon comments.Fanael Linithien2014-11-231-2/+2
|
* Don't leave lone closing parens.Fanael Linithien2014-11-231-4/+2
|
* no subshellElan Ruusamäe2014-11-231-1/+1
| | | don't need subshell to send stderr to /dev/null
* Merge pull request #772 from drbo/syntax_bugfixEvan Martin2014-11-231-0/+1
|\ | | | | Added highlighting in Emacs for ${...} variables
| * Removed tab and added . in variable name regexpDemetri Obenour2014-06-011-1/+1
| |