# Will disable\_jump\_reply make a return?

**URL:** https://meta.discourse.org/t/will-disable-jump-reply-make-a-return/116558
**Category:** UX
**Created:** [May 1, 2019, 11:16am UTC](https://meta.discourse.org/t/will-disable-jump-reply-make-a-return/116558 "2019-05-01T11:16:38Z")
**Posts on this page:** 1
**Showing post:** 39

<div class="post-metadata">

### Author: ![Pod](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pod/32/119253_2.png) [@Pod](https://meta.discourse.org/u/Pod)
#### Post date: [May 3, 2019, 10:05am UTC](https://meta.discourse.org/t/will-disable-jump-reply-make-a-return/116558/39 "2019-05-03T10:05:47Z")

</div>

> [@codinghorror](#):
>
> Sort of like this.. but for the reply button:
> 
> ![image](https://global.discourse-cdn.com/meta/original/3X/2/f/2ff5029dd03d5aa568b045a21d2b1eb02de6ee08.png)

YOU WHAT? That’s a BUTTON?!

I used to just copy/delete/paste posts and ensure I pressed the correct “reply” button for the response I wanted. I had no idea I could switch on the fly!

> [@codinghorror](#):
>
> I am not opposed to a keyboard shortcut that jumps you to your topmost reading hole as well. But again… good freaking luck explaining that to people… there may indeed be reading holes but the best solution to holes is to _avoid creating them whenever possible._ 🕳

Speaking of holes: Is there a way to clear them? The back button went a bit crazy the other day and it ended up pointing at the top of QT3s Game Of Thrones mega-thread, even though I was “fully read” and possibly the last poster in that thread. It turns out there were quite a few posts near the top that weren’t marked as read, and they still are, because I’m not going to manually scroll down them all to satisfy Discourse. I’d never seen that before, though.

( I also find it ironic, as Discourse is usually hell bent on destroying my precious read position and getting me to the bottom of the thread)

> [@Stephen](#):
>
> To anyone who is hell-bent on not losing their topic position in a single reading it’s quite easy to just run a second tab or window. I’d rather “experts” be put though that inconvenience than give them the tools to perpetuate the above.

It’s quite easy, but completely impractical. I already have a dedicated tab open for the QT3 Star Trek watching thread because Discourse [mangled my read position](https://meta.discourse.org/t/have-search-take-me-to-my-read-position-or-the-first-post-in-the-topic/109628/38) with its search results. (ps I purposefully linked to the end there to mess with your read markers in that thread) Perhaps I should keep a physically notebook open by my desk and write down all of my read markers for all important threads, just on the (likely) chance that Discourse blows them away?

---

_[View the full topic](https://meta.discourse.org/t/will-disable-jump-reply-make-a-return/116558)._