summaryrefslogtreecommitdiff
path: root/pygments/lexers/fortran.py
Commit message (Collapse)AuthorAgeFilesLines
* Update copyright year to 2023.Matthäus G. Chajdas2023-03-291-1/+1
|
* all: style fixesGeorg Brandl2022-10-271-2/+2
|
* Fix glitch found by regexlintJean Abou Samra2022-08-151-2/+2
|
* Fortran: fix catastrophic backtrackingJean Abou Samra2022-08-151-2/+2
| | | | \\\\|\\. is like \\. but causes catastrophic backtracking inside (...)* .
* Rework URL information in lexers.Matthäus G. Chajdas2022-03-201-0/+1
| | | | | | | | This commit adds a new url field to a lexer, which can be used to link to the language website, instead of relying on having the link in either languages.rst or the docstring of the lexer. Additionally, it changes the languages.rst file to auto-generate the list of lexers from the actual source code, using the provided URL.
* Happy new year.Georg Brandl2022-01-251-1/+1
|
* Add f90 as an alias for fortran (closes #2000.)Matthäus G. Chajdas2021-12-291-1/+1
|
* Improve whitespace handling in Fortran.Matthäus G. Chajdas2021-10-021-5/+5
|
* Fortran: Change whitespace to Text until Whitespace is used consistently.Matthäus G. Chajdas2021-10-021-2/+2
|
* Fix "do concurrent" and "go to" keywords in the Fortran lexer. (#1877)ecasglez2021-10-021-2/+6
| | | | | | | | | | | | | | | | | * Fix "do concurrent" and "go to" keywords in the Fortran lexer. * "Go to" statement was only highlighted if there was no space between "go" and "to". * "Concurrent" keyword in the "Do Concurrent" statement was never highlighted because of a typo. It has been fixed. In addition, it now highlights them only if "Concurrent" is right after the "Do" keyword. * I had to put the "do concurrent" changes before the already available list of keywords. Otherwise it won't highlight "Concurrent" because it finds first the "Do" keyword in the other list and stops searching for more keywords. * Fix a bug while parsing Fortran files with go to and do concurrent statements causing wrong highlighting. * For example, in the variable name "gotoErr", "goto" was highlighted but it shouldn't. * Update Fortran tests to the changes for the "go to statements" * Use Text.Whitespace to distinguish Fortran multiword keywords Co-authored-by: ecasglez <ecasglez@protonmail.com>
* Fotran lexer: detect keywords formed by two keywords without inter-word ↵ecasglez2021-02-121-0/+3
| | | | | | | spaces. (#1677) * Fix for issue #1188. * I took the list of keywords affected by this issue from the VIM fortran lexer. * All the affeced keywords are ending keywords, that is, "end" followed by another keyword without space.
* Run pyupgrade across codebase to modernize syntax and patterns (#1622)Jon Dufresne2021-01-171-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | pyupgrade is a tool to automatically upgrade syntax for newer versions of the Python language. The project has been Python 3 only since 35544e2fc6eed0ce4a27ec7285aac71ff0ddc473, allowing for several cleanups: - Remove unnecessary "-*- coding: utf-8 -*-" cookie. Python 3 reads all source files as utf-8 by default. - Replace IOError/EnvironmentError with OSError. Python 3 unified these exceptions. The old names are aliases only. - Use the Python 3 shorter super() syntax. - Remove "utf8" argument form encode/decode. In Python 3, this value is the default. - Remove "r" from open() calls. In Python 3, this value is the default. - Remove u prefix from Unicode strings. In Python 3, all strings are Unicode. - Replace io.open() with builtin open(). In Python 3, these functions are functionally equivalent. Co-authored-by: Matthäus G. Chajdas <Anteru@users.noreply.github.com>
* Added 'ERROR STOP' to fortran.py keywords. (#1665)ecasglez2021-01-101-2/+2
| | | Maybe close #931
* Bump copyright year.Matthäus G. Chajdas2021-01-031-1/+1
|
* feat: added 'ONLY' to fortran.py Keywords0xflotus2020-12-281-3/+3
| | | maybe close #1543
* Update copyright year (fixes #1514.)Matthäus G. Chajdas2020-08-221-1/+1
|
* fixed fortran literal regex patternTakanobu Amano2020-05-051-4/+4
|
* Fixup all headers and some more minor problems.2.4.2Georg Brandl2019-05-281-1/+1
|
* Safer Fortran E-notation without decimalMarshall Ward2018-01-061-1/+1
| | | | | Fortran e-notation values without decimal now require the presence of e (or d) and at least one exponent value.
* Fortran E-notation float without decimalMarshall Ward2018-01-061-0/+1
| | | | | Added a regex to parse Fortran floating points which identify floating point values with exponents but without decimals (e.g. 1e4 vs 1.e4 or 1.0e4)
* Copyright update.Georg Brandl2017-01-221-1/+1
|
* Add support for partials and path segments for Handlebars.Christian Hammond2016-11-041-0/+205
This introduces support for some missing features to the Handlebars lexer: Partials and path segments. Partials mostly appeared to work before, but the `>` in `{{> ... }}` would appear as a syntax error, as could other components of the partial. This change introduces support for: * Standard partials: `{{> partialName}}` * Partials with parameters: `{{> partialName varname="value"}}` * Ddynamic partials: `{{> (partialFunc)}}` * Ddynamic partials with lookups: `{{> (lookup ../path "partialName")}}` * Partial blocks: `{{> @partial-block}}` * Inline partials: `{{#*inline}}..{{/inline}}` It also introduces support for path segments, which can reference content in the current context or in a parent context. For instance, `this.name`, `this/name`, `./name`, `../name`, `this/name`, etc. These are all now tracked as variables.
View Lorry Controller Status