Skip to content

Commit 0f4f7ab

Browse files
authored
Merge pull request #73 from tarsiiformes/cosmetics
Minor whitespace and link cosmetics
2 parents 53d503a + 55e43a9 commit 0f4f7ab

File tree

1 file changed

+23
-19
lines changed

1 file changed

+23
-19
lines changed

README.md

+23-19
Original file line numberDiff line numberDiff line change
@@ -13,17 +13,17 @@ Bash completion for Emacs:
1313
- is configurable through programmable bash completion
1414
- works on remote shells, through TRAMP.
1515

16-
However, bash-completion.el only works with bash. If you run
17-
other shells or other interactive programs that support completion,
18-
bash-completion will not be able to help.
16+
However, bash-completion.el only works with bash. If you run
17+
other shells or other interactive programs that support completion,
18+
bash-completion will not be able to help.
1919

20-
A more powerful alternative to bash-completion.el is [MisTTY],
21-
as it works with all shells and most interactive programs that support
22-
completion. On the other hand, MisTTY cannot integrate with Emacs
23-
completion and is not able to provide completion in shell-command
24-
prompts nor in eshell mode.
20+
A more powerful alternative to bash-completion.el is [MisTTY],
21+
as it works with all shells and most interactive programs that support
22+
completion. On the other hand, MisTTY cannot integrate with Emacs
23+
completion and is not able to provide completion in shell-command
24+
prompts nor in eshell mode.
2525

26-
> [!NOTE]
26+
> [!NOTE]
2727
> While I'm still maintaining bash-completion.el, I've switched
2828
> to [MisTTY] for day-to-day operation, so that package is more
2929
> likely to receive updates. -- szermatt
@@ -115,25 +115,29 @@ the following:
115115

116116
* Does bash behave differently when run outside of Emacs? If not, check
117117
your shell configuration.
118-
* Call `M-x bash-completion-debug` and look at the `output-buffer`
119-
section. Does it match the expected set of completion? If yes,
120-
it might be a display problem. Are you using a completion engine
121-
other than the default, such as ivy or helm? Try turning it off to
122-
confirm, then [file a bug][new_issue]
123-
* If all else fails, [file a bug][new_issue]. Please include the output
118+
* Call `M-x bash-completion-debug` and look at the `output-buffer`
119+
section. Does it match the expected set of completion? If yes,
120+
it might be a display problem. Are you using a completion engine
121+
other than the default, such as ivy or helm? Try turning it off to
122+
confirm, then [file a bug][new_issue].
123+
* If all else fails, [file a bug][new_issue]. Please include the output
124124
of `M-x bash-completion-debug`, the command you're trying to use
125125
and the function or package providing completion for that command and
126-
where to download it.
126+
where to download it.
127127

128128
## CONTRIBUTING
129129

130-
To report bugs, features or even to ask questions, please open an [issue](https://github.com/szermatt/emacs-bash-completion/issues). To contribute code or documentation, please open a [pull request](https://github.com/szermatt/emacs-bash-completion/pulls).
130+
To report bugs, features or even to ask questions, please open an
131+
[issue][issues]. To contribute code or documentation, please open a
132+
[pull request][pull-requests].
131133

132-
See [CONTRIBUTING.md](CONTRIBUTING.md) for more details.
134+
See [CONTRIBUTING.md](CONTRIBUTING.md) for more details.
133135

134136
## COMPATIBILITY
135137

136138
bash-completion.el is known to work with Bash 4.2 and later and Bash
137-
5, on Emacs, starting with version 25.3, under Linux and OSX.
139+
5, on Emacs, starting with version 25.3, under Linux and OSX.
138140

139141
[new_issue]: https://github.com/szermatt/emacs-bash-completion/issues/new
142+
[issues]: https://github.com/szermatt/emacs-bash-completion/issues)
143+
[pull-requests]: (https://github.com/szermatt/emacs-bash-completion/pulls)

0 commit comments

Comments
 (0)