OS: Android
App: Mobile
As mentioned in the title there is no option to undo/redo in Android while editing a file (AFAIK). This along with aggressive auto-save make a annoying combo in case of accidentally deleting something in a note, especially big texts.
I am working on this
Ok! Thx for the response!
(AFAIK)
What do you mean by this?
(AFAIK)
What do you mean by this?
It means As Far As I Know (AFAIK)
Its an abbreviation :sweat_smile:
Thanks @amitsin6h 馃憤
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
@laurent22 is this still an issue?
@coderrsid Unfortunately yes....
Ohh.. i'll look what i can do.
@coderrsid I am already working on it, so could you please look on some other issue
Although @Rahulm2310 i'll suggest you to discuss the feature on the Discourse forum as it will increase the understanding of the feature for you and the community better.
the scope of this issue is not only Android, but also desktop (win/Linux).
tested version: 1.0.201
@teddyzhai I think we have undo/redo functionality on the desktop app.
@Rahulm2310 , I am on version 1.0.201 for Linux.

Under Edit tab, there is no undo or redo. Can you please point me to the right place? thanks.
Under Edit tab, there is no
undoorredo. Can you please point me to the right place? thanks.
Yeah we know that. But if the focus of cursor is in editor. Press Ctrl+Z for undo & Ctrl+Shift+Z for redo, it will work till the last note sync.
Although i have created an issue for listing in Edit Menu. I'll put a PR soon.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
@stale[bot] yes the issue is still at large