# Fix Vim 'e' Behavior When Boundary Is Last Point on Line \(\#7424\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/3aa4e0c90b82db0a9cf542e56c2efae22500d8fc)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 3aa4e0c90b82db0a9cf542e56c2efae22500d8fc

Requested commit: 3aa4e0c90b82db0a9cf542e56c2efae22500d8fc

Commit: 3aa4e0c90b82db0a9cf542e56c2efae22500d8fc

Tree: 87b9916ae39cd0d5410ecf1d2b25e77a19692308

Author: Andrew Marek

Committer: GitHub

## Message

```
Fix Vim 'e' Behavior When Boundary Is Last Point on Line (#7424)

This was originally just to fix
https://github.com/zed-industries/zed/issues/4354, which I did by just
returning the previous offset in `find_boundary`.. but `find_boundary`
is used in the "insert mode" / normal editor too, so returning the
previous boundary breaks existing functionality in that case.

I was considering a new `find_boundary` function just for some of the
vim motions like this, but I thought that this is straightforward enough
and future Vim functions might need similar logic too.

Release Notes:

- Fixed https://github.com/zed-industries/zed/issues/4354
```

## Parents

- [90cd3b5e874907782756b7f12b30ae0f7e1697de](https://git.cafe/gitcafe/zed/commit/90cd3b5e874907782756b7f12b30ae0f7e1697de?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/3aa4e0c90b82db0a9cf542e56c2efae22500d8fc?format=markdown)