this post was submitted on 26 Oct 2023

114 points (93.8% liked)

Linux

48008 readers

815 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

114

Undo the undo (lemmy.ca)

submitted 1 year ago by [email protected] to c/[email protected]

34 comments fedilink hide all child comments

Beginning Linux user: "Ctrl-Z is undo, right?"

Advanced Linux user: "Ctrl-Z dammit fg"

you are viewing a single comment's thread
view the rest of the comments

[–] Orbituary 19 points 1 year ago* (last edited 1 year ago) (2 children)

Omg. I've hated emacs for 30+ years and you just made it worse.

[–] Nibodhika 10 points 1 year ago (2 children)

It sounds confusing, but it's actually really easy to get used and hard to walk away from it. Essentially the undo is just another operation so it can be undone just like everything else, and that's a redo. Imagine the following situation, I wrote a text, but wasn't happy with some part, so I select that part and delete it, now I keep writing but I realised I need some part of what was there, so I undo all of the text that I wrote, select the text I want to copy, and accidentally cut it instead of copy it. In most editors that's it, you're fucked, you just lost your most recent changes, on Emacs undo does not destroy things, it only adds to the sequence. In other words, as a step by step:

Write text
Delete part of it
Write more text
Undo step 3 (most editors that means go back to step 2, so step 4 is in a dangerous space)
Undo step 2 (again, most editors would have actually gone to step 2)
You're now in something that looks like step 2, cut the text you wanted (on most editors because you were in step 2 and did changes you can't ever go back to step 4, because this is the new step 3 and there isn't still a step 4, so undo and redo will undo and redo the cut of that text)
Undo step 6 (you're now similar to how you started step 6 or 2, on most editors you are really on step 2).
Undo again (on most editors that would take you to step 1), this will take you to step 5, i.e. you redid the step 2, so the text disappeared and you're like you were at the beginning of step 3.
Undo again and you undo the undo of step 3, putting you back on original step 4

Like I said, confusing to understand, but it means that you can't ever shoot yourself in the foot by undoing things.

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago)

Emacs's undo-tree -- which I mentioned above that I use -- also provides non-destructive undo, same as emacs's base undo. So you can't lose data by undoing things. However, it also uses the undo and redo semantics to traverse one branch of the tree, so it works like most other apps as long as you aren't needing to recover data that would normally have been "lost" by performing an undo.

There are probably faster ways to do it, but since I rarely need to quickly grab stuff that an undo destroyed, I haven't looked into them.

Do non-undo operation.
Undo it.
Do non-undo operation. At this point, in software packages that lack non-destructive undo, you will have lost the data in #1.
Run undo-tree-visualize, on C-x u by default. A new window will come up displaying the undo history as a tree.
You can traverse around the tree. Move to the node immediately before the branch that you abandoned, and use C-b and C-f to switch between branches.

[–] Orbituary 2 points 1 year ago (2 children)

Yeah, no.

If 'esc-u' doesn't work, I :q!

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (1 children)

I will bet that vim has some form of non-destructive undo as well. Might take an add-on package, but generally-speaking, useful behavior in emacs and vim tend to get ported to each other.

googles

Yup.

https://learnvim.irian.to/basics/undo

In Vim, every time you press u and then make a different change, Vim stores the previous state's text by creating an "undo branch". In this example, after you typed "two", then pressed u, then typed "three", you created an leaf branch that stores the state containing the text "two". At that moment, the undo tree contained at least two leaf nodes: the main node containing the text "three" (most recent) and the undo branch node containing the text "two". If you had done another undo and typed the text "four", you would have at three nodes: a main node containing the text "four" and two nodes containing the texts "three" and "two".

To traverse each undo tree nodes, you can use g+ to go to a newer state and g- to go to an older state. The difference between u, Ctrl-R, g+, and g- is that both u and Ctrl-R traverse only the main nodes in undo tree while g+ and g- traverse all nodes in the undo tree.

Undo tree is not easy to visualize. I find vim-mundo plugin to be very useful to help visualize Vim's undo tree. Give it some time to play around with it.

It sounds like vim+vim-mundo and emacs+undo-tree operate kind of similarly, actually.

EDIT: In fact, this is definitely the case. According to emacswiki, emacs' undo-tree is based on vim's model.

[–] Orbituary 1 points 1 year ago

Nice.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

:q!

you mean ZQ

[–] Orbituary 2 points 1 year ago

Nope! But cool.

[–] [email protected] 1 points 1 year ago (1 children)

Bizarre that you've hated it for 30 years yet didn't know one of the earliest things users learn about it (that actually is fine to use). Perhaps you should examine why you hate something you're almost completely ignorant of.

Though most jokes and criticisms about Emacs betray complete ignorance of it, so you're hardly unusual.

[–] Orbituary 1 points 1 year ago (1 children)

I don't need all the overhead. Vi has always worked for me. It's ubiquitous. I'm fast with it. It suits my needs fully.

[–] [email protected] 2 points 1 year ago (1 children)

You must truly loathe vscode etc then if you hate emacs for overhead. I can't really see why you should hate something just because it uses a slightly less small amount of resources. I don't even know how you'd notice on any machine from the last 20 years.

[–] Orbituary 1 points 1 year ago* (last edited 1 year ago) (1 children)

This is my preference. Is that not OK?

[–] [email protected] 0 points 1 year ago

Seems pretty reasonable that if you want to tell the world you hate something, you might want the world to understand why you hate it, or else perhaps we might assume it's not a reasoned position. That's certainly the conclusion I'm coming to.