joined 1 month ago
[–] [email protected] 1 points 14 hours ago* (last edited 14 hours ago)

Instead of remembering what line number you were at, you can use marks (:help mark-motions) to immediately jump back to where you left off.

For example, type mx to mark the current position with x (or anything you want). Say now you are at the top of the file, just type 'x to go back to the line marked with x.

Programming Is Mostly Thinking (
[–] [email protected] 4 points 1 day ago* (last edited 1 day ago)

A godsend for saving time - the ab (abbreviation) command. This command lets you shorten a long sequence of characters (be it a text or a complex command) into another sequence of any length. It works in both insert mode and command mode. If you frequently edit text using a lengthy command, this feature will significantly save you time. For example: :ab ul s/\<./\u&/g to capitalize every word in a line. When you enter command mode (type :) and type ul, vim will automatically expand it to s/\<./\u&/g for you.

Additionally, the map command can save even more time, but IMO the ab command offers more control for handling various cases. In my example, you can use ul to only capitalize the lines that have a specific pattern using the global command g.

Another overlooked aspect is the .exrc file. Enabling it with set exrc in your config allows for different setups based on different situations. For instance, when writing notes, I prefer to have line breaks on to make the text look nicer on the screen. In contrast, when writing code, I don't require this option. I simply need to place set linebreak in the .exrc file in the note-writing directory to adjust accordingly.

Lets Help Adobe (
Lets Help Adobe (

Credit: JamesLee

submitted 1 week ago by [email protected] to c/linux
Opsec101 (
Opsec101 (
[–] [email protected] 20 points 2 weeks ago* (last edited 2 weeks ago) (4 children)

That's what I like about FOSS. You see very few distractions that try to grab your attention. This leads to a rather quiet digital life.

To take it a step further, you could enable the Do Not Disturb feature on your devices and only grant notification permissions to essential apps. This way, you can enjoy some peace of mind.

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

I haven't come across any information regarding the automatic aspect, and I don't have any personal experience with bubblejail either. However, bubblejail is mentioned on the arch wiki. It might be the closest match in this case, so you could give it a try.

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

You can use bubblewrap (its CLI name is bwrap) to make an arbitrary directory as $HOME for a specific program session. Basically, you can bind or set any environment variable you need for that particular program. I recommend checking out the arch wiki on this topic.

For example: bwrap --dev-bind / / --bind $HOME/your/dir/path $HOME <your_program>. This will let <your_program> have access to / and device permissions, with $HOME/your/dir/path serving as its $HOME.

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

My lazy ass decided to just go with the copied title generated by Lemmy when making the post. I edited the title, thanks for mentioning that!

[–] [email protected] 6 points 1 month ago* (last edited 1 month ago)


Edit: The new link of the post works but I think providing an archive link would be more sufficient.

[–] [email protected] 3 points 1 month ago (3 children)

This kind of self-fulfilling prophecy is what will drive down even more support for Linux. The thing we need to do right now is to let more people try out Linux so that corporations will see Linux as a potential target on the desktop and make products for Linux, not the opposite like what you are saying.

view more: next ›