Fabian Homborg cb16d9e741 fish_indent: Allow escaped newlines only for certain things
Things like

```fish
\
echo foo
```

or

```fish
echo foo; \
echo bar
```

are a formatting blunder and should be handled.

This makes it so the escaped newline is removed, and the
semicolon/token_type_end handling will then put the statements on
different lines.

One case this doesn't handle brilliantly is an escaped newline after a
pipe:

```fish
echo foo | \
cat
```

is turned into

```fish
echo foo | cat
```

which here works great, but in long pipelines can cause issues.

Pipes at the end of the line cause fish to continue parsing on the
next line, so this can just be written as

```fish
echo foo |
cat
```

for now.
2020-03-15 21:01:00 +01:00
..
2020-03-09 19:46:43 +01:00
2019-09-14 12:46:57 -07:00
2019-04-11 21:59:23 -07:00
2018-04-01 13:48:21 -07:00
2018-12-11 18:23:37 +01:00
2014-09-21 21:03:44 -07:00
2014-09-21 21:03:44 -07:00
2019-06-28 11:16:27 -07:00
2014-12-23 15:46:47 -08:00
2019-05-24 17:00:56 -07:00
2017-07-25 12:44:26 -07:00
2019-04-07 09:20:32 -07:00
2019-04-07 09:20:32 -07:00
2019-04-07 09:20:32 -07:00
2019-02-24 21:46:52 -08:00
2019-02-24 21:46:52 -08:00
2019-02-24 21:46:52 -08:00
2014-07-13 19:11:29 -07:00
2019-01-01 14:52:26 +01:00
2017-03-28 16:28:24 -07:00
2017-03-28 16:28:24 -07:00
2017-03-28 16:28:24 -07:00
2018-12-31 19:36:08 -06:00
2017-11-16 10:48:21 -08:00
2017-11-16 10:48:21 -08:00