| /dports/lang/racket/racket-8.3/src/expander/read/ |
| H A D | indentation.rkt | 5 (provide make-indentation
6 track-indentation!
7 indentation-possible-cause
10 (struct indentation
23 (indentation closer
50 (set-indentation-suspicious-closer! indt (indentation-closer indt))
53 (define (indentation-possible-cause config)
56 [(indentation-suspicious-line indt)
57 (format "\n possible cause: indentation suggests a missing ~a before line ~a"
96 ;; Possibly add a cause based on indentation:
[all …]
|
| H A D | sequence.rkt | 11 "indentation.rkt"
26 (define indentation (make-indentation closer in seq-config))
28 [indentations (cons indentation
41 (indentation-possible-cause config)))
59 (track-indentation! config dot-line dot-col)
88 (track-indentation! config dot2-line dot2-col)
|
| /dports/lang/racket-minimal/racket-8.3/src/expander/read/ |
| H A D | indentation.rkt | 5 (provide make-indentation
6 track-indentation!
7 indentation-possible-cause
10 (struct indentation
23 (indentation closer
50 (set-indentation-suspicious-closer! indt (indentation-closer indt))
53 (define (indentation-possible-cause config)
56 [(indentation-suspicious-line indt)
57 (format "\n possible cause: indentation suggests a missing ~a before line ~a"
96 ;; Possibly add a cause based on indentation:
[all …]
|
| H A D | sequence.rkt | 11 "indentation.rkt"
26 (define indentation (make-indentation closer in seq-config))
28 [indentations (cons indentation
41 (indentation-possible-cause config)))
59 (track-indentation! config dot-line dot-col)
88 (track-indentation! config dot2-line dot2-col)
|
| /dports/finance/hs-hledger-ui/hledger-ui-1.19/_cabal_deps/word-wrap-0.4.1/ |
| H A D | CHANGELOG.md | 7 indentation longer than the indentation width when
10 * When breakLongWords is enabled, this change reduces the indentation
12 the wrap limit, so they will have reduced indentation and word
16 indentation of the indented lines and leaves whole words, unbroken,
17 on them, resulting in lines that are longer than the indentation
58 it possible to cause words to get broken up over multiple lines if
68 * Wrap settings now include a setting to control how indentation is
|
| /dports/devel/hs-git-brunch/git-brunch-1.5.1.0/_cabal_deps/word-wrap-0.4.1/ |
| H A D | CHANGELOG.md | 7 indentation longer than the indentation width when
10 * When breakLongWords is enabled, this change reduces the indentation
12 the wrap limit, so they will have reduced indentation and word
16 indentation of the indented lines and leaves whole words, unbroken,
17 on them, resulting in lines that are longer than the indentation
58 it possible to cause words to get broken up over multiple lines if
68 * Wrap settings now include a setting to control how indentation is
|
| /dports/net-im/matterhorn/matterhorn-50200.13.0/_cabal_deps/word-wrap-0.4.1/ |
| H A D | CHANGELOG.md | 7 indentation longer than the indentation width when
10 * When breakLongWords is enabled, this change reduces the indentation
12 the wrap limit, so they will have reduced indentation and word
16 indentation of the indented lines and leaves whole words, unbroken,
17 on them, resulting in lines that are longer than the indentation
58 it possible to cause words to get broken up over multiple lines if
68 * Wrap settings now include a setting to control how indentation is
|
| /dports/misc/hs-hascard/hascard-0.3.0.1/_cabal_deps/word-wrap-0.4.1/ |
| H A D | CHANGELOG.md | 7 indentation longer than the indentation width when
10 * When breakLongWords is enabled, this change reduces the indentation
12 the wrap limit, so they will have reduced indentation and word
16 indentation of the indented lines and leaves whole words, unbroken,
17 on them, resulting in lines that are longer than the indentation
58 it possible to cause words to get broken up over multiple lines if
68 * Wrap settings now include a setting to control how indentation is
|
| /dports/cad/openscad/openscad-41f58fe57c03457a3a8b4dc541ef5654ec3e8c78/doc/ |
| H A D | hacking.md | 7 * Use 2 spaces for indentation
17 Alternatively, it's possible to beautify the entire codebase by running `scripts/beautify.sh --all`.
20 * You're bringing an old branch to life and want to minimize conflict cause by the large coding sty…
|
| /dports/cad/openscad-devel/openscad-63a7c77740030c63d646eb0684ba6947eecb0db7/doc/ |
| H A D | hacking.md | 7 * Use 2 spaces for indentation
17 Alternatively, it's possible to beautify the entire codebase by running `scripts/beautify.sh --all`.
20 * You're bringing an old branch to life and want to minimize conflict cause by the large coding sty…
|
| /dports/astro/py-astropy/astropy-5.0/docs/development/ |
| H A D | codeguide_emacs.rst | 20 The setup below is on purpose minimal. In principle, it is possible
28 This setting will cause indentation to use spaces rather than tabs for all
29 files. For python files, indentation of 4 spaces will be used if the tab key
|
| /dports/deskutils/flameshot/flameshot-0.10.2/cmake/ |
| H A D | CompilerWarnings.cmake | 10 /w14242 # 'identifier': conversion from 'type1' to 'type1', possible loss of data
11 …/w14254 # 'operator': conversion from 'type1:field_bits' to 'type2:field_bits', possible loss of d…
27 …/w14826 # Conversion from 'type1' to 'type_2' is sign-extended. This may cause unexpected runtime …
59 -Wmisleading-indentation # warn if indentation implies blocks where blocks do not exist
|
| /dports/devel/hs-haskell-language-server/haskell-language-server-1.4.0/_cabal_deps/brittany-0.13.1.1/doc/implementation/ |
| H A D | theory.md | 22 prefer the indentation of our expressions(, statements etc.) line up with
26 in their newline/indentation usage:
82 possible layouts;
110 at just the first, but the first n possible layouts, but against an exponential
127 of possible layouts, and top-to-bottom for making the actual decisions.. well,
136 For example we might return two possible spacings for the following (same)
157 child-nodes in the syntax-tree, we generate a limited number of possible
164 of the possible layouts for the current node. It passes the current
268 layout. However, this not possible always:
310 are good reasons against using such whitespace: It can cause larger diffs
[all …]
|
| H A D | exactprinting.md | 44 other stuff (even switching order of comments is possible). Use the steps
50 only with the wrong indentation, the cause most likely is a
53 thing that provides the "layouting rule" indentation, i.e. the body of a
56 - There is one other cause for off-by-one errors in comment position:
327 keywords). This covers both newlines and indentation, and for indentation
328 includes the case where indentation is mandatory ("layouting rule").
336 -- DP (2, 2) two newlines, two spaces indentation
338 -- DB (1, 0) one newline, zero indentation relative to the do-indentation
353 ### Caveat One: Indentation relative to layouting rule indentation level
361 construct (`abc`) has an indentation relative to the enclosing indentation
[all …]
|
| /dports/devel/stlink/stlink-1.7.0/ |
| H A D | CONTRIBUTING.md | 4 …ut! We want to make contributing to this project as easy and transparent as possible, whether it's:
21 * Use [fixed width integer types](http://en.cppreference.com/w/c/types/integer) wherever possible a…
26 * Use 4 spaces for indentation rather than tabs (the latter results in inconsistent appearance on d…
28 …possible, as they are interpreted differently on particular platforms and systems. Otherwise these…
29 * Use state-of-the-art UTF-8 encoding whereever possible.
|
| /dports/devel/pear-PhpDocumentor/PhpDocumentor-1.4.4/tutorials/Converters/PDFdefault/ |
| H A D | PDFParser.cls | 21 …e Cezpdf library and do anything that it can do. This is what makes it possible to use Smarty tem…
32 <listitem><para>left - indentation from the left margin</para></listitem>
33 <listitem><para>right - indentation from the right margin</para></listitem>
34 <listitem><para>aleft - absolute indentation from the left side of the page</para></listitem>
35 … <listitem><para>aright - absolute indentation from the right side of the page</para></listitem>
52 …ectory as a fontface-php.afm and fontface.afm file, otherwise Cezpdf will cause all kinds of PHP w…
|
| /dports/databases/py-pglast/pglast-1.2/ |
| H A D | CHANGES.rst | 34 I'm sorry for any inconvenience this may cause.
150 - Fix indentation of boolean expressions in SELECT's targets (`issue #3`__)
180 - Nicer indentation for JOINs, making OUTER JOINs stand out
208 - New ``compact_lists_margin`` option to produce a more compact representation when possible
|
| /dports/databases/py-pglast/pglast-1.2/docs/ |
| H A D | changes.rst | 34 I'm sorry for any inconvenience this may cause.
150 - Fix indentation of boolean expressions in SELECT's targets (`issue #3`__)
180 - Nicer indentation for JOINs, making OUTER JOINs stand out
208 - New ``compact_lists_margin`` option to produce a more compact representation when possible
|
| /dports/lang/racket/racket-8.3/share/pkgs/preprocessor/scribblings/ |
| H A D | mzpp.scrbl | 39 (thunk (push-indentation ""))
40 (define bar "BAR") (thunk (pop-indentation))
45 (thunk (push-indentation " "))
46 bar newline* bar (thunk (pop-indentation))
72 embedded Racket code added the appropriate spaces for indentation.
74 It is possible to temporarily switch from Racket to text-mode and back
160 possible to change them. This is done by a line with a special
169 possible to change the markers from the Racket side (see below), but this
195 accept zero arguments will cause an error) and the result is sent back to
257 @defproc[(push-indentation [str string?]) void?]
[all …]
|
| /dports/devel/p5-Perl-Tidy/Perl-Tidy-20211029/ |
| H A D | CHANGES.md | 1244 possible if a logfile stream is specified. This is to prevent
1286 possible values are now:
1877 if possible.
2536 -Whenever possible, if a logical expression is broken with leading
2770 -The -w parameter now notes possible errors of the form:
2856 was possible until Wolfgang Weisselberg pointed it out:
2899 . " possible values ("
2904 . " possible values ("
3527 following file would cause it to disappear:
3875 -chk flag and perltidy will scan for this possible error.
[all …]
|
| /dports/multimedia/transcode/transcode-1.1.7/ |
| H A D | STYLE | 9 * The basic indentation unit is four columns.
11 * Tab characters (ASCII 0x09) must not be used for indentation or alignment
13 where possible. Tabs should not be assumed to have any particular width.
17 code). Comments on their own lines should start at the same indentation
22 same line as the last line of comment text, unless doing so would cause
59 * expressions (such as "ptr != NULL") where possible. If there are no
237 * Case labels for a switch should be indented half of a normal indentation
287 function has more than four levels of indentation then it should probably
376 code. Labels for goto should be outdented half of an indentation unit
443 For unrecoverable errors which cause the operation to abort.
[all …]
|
| /dports/graphics/py-gdal/gdal-3.3.3/doc/source/development/rfc/ |
| H A D | rfc69_cplusplus_formatting.rst | 71 file, however to make it as easy as possible, we will use the default
80 symptoms, no cause: developers not following the code formatting
104 modification. It is possible to fine-tune the configuration, but this
123 editors about the basic style settings like indentation, whitespaces and
202 warnings <https://developers.redhat.com/blog/2016/02/26/gcc-6-wmisleading-indentation-vs-goto-fail/…
207 … src/geom/Polygon.cpp:154:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
|
| /dports/graphics/p5-Geo-GDAL/gdal-3.3.3/doc/source/development/rfc/ |
| H A D | rfc69_cplusplus_formatting.rst | 71 file, however to make it as easy as possible, we will use the default
80 symptoms, no cause: developers not following the code formatting
104 modification. It is possible to fine-tune the configuration, but this
123 editors about the basic style settings like indentation, whitespaces and
202 warnings <https://developers.redhat.com/blog/2016/02/26/gcc-6-wmisleading-indentation-vs-goto-fail/…
207 … src/geom/Polygon.cpp:154:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
|
| /dports/graphics/gdal/gdal-3.3.3/doc/source/development/rfc/ |
| H A D | rfc69_cplusplus_formatting.rst | 71 file, however to make it as easy as possible, we will use the default
80 symptoms, no cause: developers not following the code formatting
104 modification. It is possible to fine-tune the configuration, but this
123 editors about the basic style settings like indentation, whitespaces and
202 warnings <https://developers.redhat.com/blog/2016/02/26/gcc-6-wmisleading-indentation-vs-goto-fail/…
207 … src/geom/Polygon.cpp:154:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
|
| /dports/math/blis/blis-0.8.1/docs/ |
| H A D | CodingConventions.md | 7 * [Indentation](CodingConventions.md#indentation)
28 Please either use braces to denote the indentation limits of scope, or to enclose multiple statemen…
55 …possible, **please use tabs to denote changing levels of scope!** If you can't use tabs or doing s…
67 … the characters that should be spaces with `.` (with tabs used for the first level of indentation):
98 line containing words, unless the comment marker would cause you to
|