# VS2019 Mercury Behavior

**URL:** https://talk.remobjects.com/t/vs2019-mercury-behavior/24282
**Category:** Mercury
**Tags:** visual-studio
**Created:** [February 28, 2021, 5:07pm UTC](https://talk.remobjects.com/t/vs2019-mercury-behavior/24282 "2021-02-28T17:07:11Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![avonelle](https://talk.remobjects.com/user_avatar/talk.remobjects.com/avonelle/32/13001_2.png) [@avonelle](https://talk.remobjects.com/u/avonelle)
#### Post date: [February 28, 2021, 5:07pm UTC](https://talk.remobjects.com/t/vs2019-mercury-behavior/24282/1 "2021-02-28T17:07:11Z")

</div>

Visual Studio 2019 16.8.4, Elements 10.0.0.2607

At least two behaviors I’ve noticed in Visual Studio 2019 with Mercury that (to me anyway) seem not quite right:

1. Often when I add a line of code, it ignores formatting rules to automatically indent.
2. If I type something like “Public Function Foo” and press Enter, it does not add the “End Function”, I have to type that manually.
3. If I type “Public FUnction Foo” and press Enter, it doesn’t automatically reformat that to “Public Function Foo”.

Here’s a screencast for the first two items, in case I wasn’t clear:

–Avonelle

---

<div class="post-metadata">

### Author: ![RemObjectsSoftware](https://talk.remobjects.com/user_avatar/talk.remobjects.com/remobjectssoftware/32/15947_2.png) [@RemObjectsSoftware](https://talk.remobjects.com/u/RemObjectsSoftware)
#### Post date: [March 1, 2021, 12:26pm UTC](https://talk.remobjects.com/t/vs2019-mercury-behavior/24282/2 "2021-03-01T12:26:24Z")

</div>

Thanks, logged as [bugs://85659](https://www.remobjects.com/portal/bugs/?id=85659) — Mercury: VS Capitalize keywords on typing

---

<div class="post-metadata">

### Author: ![RemObjectsSoftware](https://talk.remobjects.com/user_avatar/talk.remobjects.com/remobjectssoftware/32/15947_2.png) [@RemObjectsSoftware](https://talk.remobjects.com/u/RemObjectsSoftware)
#### Post date: [March 1, 2021, 12:27pm UTC](https://talk.remobjects.com/t/vs2019-mercury-behavior/24282/3 "2021-03-01T12:27:45Z")

</div>

Thanks, logged as [bugs://85660](https://www.remobjects.com/portal/bugs/?id=85660) — Mercury: VS: Smart-end

---

<div class="post-metadata">

### Author: ![RemObjectsSoftware](https://talk.remobjects.com/user_avatar/talk.remobjects.com/remobjectssoftware/32/15947_2.png) [@RemObjectsSoftware](https://talk.remobjects.com/u/RemObjectsSoftware)
#### Post date: [March 1, 2021, 12:31pm UTC](https://talk.remobjects.com/t/vs2019-mercury-behavior/24282/4 "2021-03-01T12:31:20Z")

</div>

Thanks, logged as [bugs://85661](https://www.remobjects.com/portal/bugs/?id=85661) — Mercury: VS: bad cursor offset (0) after pressing enter, sometimes

---

<div class="post-metadata">

### Author: ![RemObjectsSoftware](https://talk.remobjects.com/user_avatar/talk.remobjects.com/remobjectssoftware/32/15947_2.png) [@RemObjectsSoftware](https://talk.remobjects.com/u/RemObjectsSoftware)
#### Post date: [March 3, 2021, 8:58am UTC](https://talk.remobjects.com/t/vs2019-mercury-behavior/24282/5 "2021-03-03T08:58:21Z")

</div>

[bugs://85661](https://www.remobjects.com/portal/bugs/?id=85661) got closed with status fixed.

---

<div class="post-metadata">

### Author: ![RemObjectsSoftware](https://talk.remobjects.com/user_avatar/talk.remobjects.com/remobjectssoftware/32/15947_2.png) [@RemObjectsSoftware](https://talk.remobjects.com/u/RemObjectsSoftware)
#### Post date: [March 12, 2021, 12:22pm UTC](https://talk.remobjects.com/t/vs2019-mercury-behavior/24282/6 "2021-03-12T12:22:40Z")

</div>

[bugs://85659](https://www.remobjects.com/portal/bugs/?id=85659) got closed with status fixed.

---

<div class="post-metadata">

### Author: ![RemObjectsSoftware](https://talk.remobjects.com/user_avatar/talk.remobjects.com/remobjectssoftware/32/15947_2.png) [@RemObjectsSoftware](https://talk.remobjects.com/u/RemObjectsSoftware)
#### Post date: [April 26, 2021, 1:00pm UTC](https://talk.remobjects.com/t/vs2019-mercury-behavior/24282/7 "2021-04-26T13:00:52Z")

</div>

[bugs://85660](https://www.remobjects.com/portal/bugs/?id=85660) got closed with status fixed.
