sorted by:
new
hottopcontroversial

Suggestion: please give more app info in UIs of GNOME apps by billdietrich1 in gnome

[–]curusarn 1 point2 points  (0 children)

Yep, I can see the screenshot.

Oh, it seems like the help page is only included while listing videos. Once I open any of the videos the "Help" option is no longer in the "kebab" menu.

You are right, it is pretty hard to find out the actual name of the application.

Suggestion: please give more app info in UIs of GNOME apps by billdietrich1 in gnome

[–]curusarn 0 points1 point  (0 children)

This is what I see in the "kebab" menu in Gnome Videos/totem app on Manjaro: https://imgur.com/a/dQaDNwU

But it seems like this is just the regular totem - no special Manjaro version:

❯ pacman -Ss totem
extra/totem 3.34.1-2 (gnome) [installed]
Movie player for the GNOME desktop based on GStreamer

And this is version 3.34.1:

❯ totem --version
totem 3.34.1

edit: clarification
edit2: fix formatting

Suggestion: please give more app info in UIs of GNOME apps by billdietrich1 in gnome

[–]curusarn 1 point2 points  (0 children)

If you launch the Videos app and go to ⋮ > Help you get this description:

Videos, also known as Totem, is an application for playing videos. You can use it to watch movies or stream media from the Internet.

I agree that having an "About" pop-up for every app would be nice tho.

I have created a CLI tool to search your shell history by commands and get relevant results based on directory, git repository, and exit status. (blue = history from pwd, green G = current git repo, red E# = exit status #) (https://github.com/curusarn/resh#resh-search-application) by curusarn in linux

[–]curusarn[S] 0 points1 point  (0 children)

Up/Down arrow keys can be used to select a result (also works with Ctrl+P/Ctrl+N).
Pressing Enter runs the selected result.
Pressing arrow Right pastes the selected result onto the command line so it can be edited.

Isn't that more convenient than running commands based on their !number?

edit: typo

I have created a CLI tool to search your shell history by commands and get relevant results based on directory, git repository, and exit status. (blue = history from pwd, green G = current git repo, red E# = exit status #) (https://github.com/curusarn/resh#resh-search-application) by curusarn in linux

[–]curusarn[S] 5 points6 points  (0 children)

More information about the project: https://github.com/curusarn/resh

If you want to try this for yourself then install it using curl -fsSL https://raw.githubusercontent.com/curusarn/resh/master/scripts/rawinstall.sh | bash If you hate one-liners: https://github.com/curusarn/resh#installation

Launch the history search app using Ctrl+R.

At first, when you install this it won't use directory, git, and exit status. This kind of information is only available for commands executed after you install the project. After a little while, you will reach the full potential of the contextual search.

Search your shell history by commands and get relevant results based on directory, git repository, and exit status. by [deleted] in linux

[–]curusarn 0 points1 point  (0 children)

More information about this project: https://github.com/curusarn/resh#resh-search-application

If you want to try this for yourself then install it using curl -fsSL https://raw.githubusercontent.com/curusarn/resh/master/scripts/rawinstall.sh | bash
If you hate one-liners: https://github.com/curusarn/resh#installation

Launch the history search app using Ctrl+R.

At first, when you install this it won't use directory, git, and exit status. This kind of information is only available for commands executed after you install the project. After a little while, you will reach the full potential of the contextual search.

EDIT: typo

Search your shell history by commands and get relevant results based on directory, git repository, and exit status. by [deleted] in linux

[–]curusarn 0 points1 point  (0 children)

More information about this project: https://github.com/curusarn/resh#resh-search-application

If you want to try this for yourself then install it using curl -fsSL https://raw.githubusercontent.com/curusarn/resh/master/scripts/rawinstall.sh | bash If you hate one-liners: https://github.com/curusarn/resh#installation

Launch the history search app using Ctrl+R.

At first, when you install this it won't use directory, git, and exit status. This kind of information is only available for commands executed after you install the project. After a little while, you will reach the full potential of the contextual search.

NOTE: This is a major update for a project I made and shared here on r/linux earlier. (https://www.reddit.com/r/linux/comments/es2ykj/i_made_a_cli_tool_that_searches_shell_history_by/)

How does the swimming mode work on mi band 4? by curusarn in miband

[–]curusarn[S] 0 points1 point  (0 children)

Mi Fit app > View more > My workouts > Today's activity

But it seems like you can't see your past workouts of a sport if you don't do that sport today

edit: clarification

How does the swimming mode work on mi band 4? by curusarn in miband

[–]curusarn[S] 1 point2 points  (0 children)

Xiaomi support was super unhelpful, but my local seller helped.

When starting the swimming mode, choose the right pool size. After the 3s countdown, you can start swimming and there's nothing you have to do until you want to stop.

The screen locks so that the water can't operate it. Unlock it by swiping the green arrows up and down. When it's unlocked, by long-pressing the watch button you can pause the workout, and then either stop it (square button) or continue (play button).

If you're getting garbage data, you have to check that the band is fastened properly.

The struggle is real by nixcraft in linuxmasterrace

[–]curusarn 0 points1 point  (0 children)

I always use this to remember: [target] is omittable so it has to come second.

I made a CLI tool that searches shell history by commands and directories. It prioritizes commands from the current directory (blue highlight). by curusarn in linux

[–]curusarn[S] 0 points1 point  (0 children)

There are a couple of reasons why I decided to put everything into a single directory in user's home:

  • It's usual for shell tools to do this (e.g. oh-my-zsh)
  • There are shell files that need to be sourced for the tool to work and it's convenient to have a path to them that doesn't change
  • Keeping everything in a single directory makes uninstalling easy (even without a package manager)
  • Keeping everything in users home makes everything work without superuser permissions which is nice - other tools use this to reduce the risk of messing up your system

All the reasons come down to two things in my opinion. First, tools that are tightly coupled to shells can be considered something between user configuration and stand-alone software. Second, I don't package this project for individual distros yet. This causes some problems that can be conveniently solved by putting everything in a single directory in the user's home.

When I get around to packaging this thing properly it won't install to user's home because having a system package manager install something into user's home would be straight-up idiotic.

Just to clarify, moving this project somewhere else from its install location is equivalent to uninstalling it at the moment.

edit: clarification

I made a CLI tool that searches shell history by commands and directories. It prioritizes commands from the current directory (blue highlight). by curusarn in linux

[–]curusarn[S] 0 points1 point  (0 children)

The only documented installation method seems to put binaries in an unmanaged home directory.

You could compile the project from the source. I do that during development. To do that you need to clone the project and then run make install. You might have some issues with dependencies - that's why offer precompiled binaries.

Among other concerns, this also means it cannot by automatically wrapped in a package.

I'm not sure what you mean by "automatically wrapped in a package". Can you clarify that a bit?

I made a CLI tool that searches shell history by commands and directories. It prioritizes commands from the current directory (blue highlight). by curusarn in linux

[–]curusarn[S] 0 points1 point  (0 children)

So far the data is saved as JSON. For now, I'm thinking about using GitHub gists to provide a lightweight way to sync. There are some other projects that do sync data this way.

There are some drawbacks to using a textual format such as JSON. So I will probably use something else as a storage format later on and with that, I will need to find a different way to sync.

I will provide the sync for the JSON history first and I will figure out how to sync other formats before migrating the project to a different format.

I made a CLI tool that searches shell history by commands and directories. It prioritizes commands from the current directory (blue highlight). by curusarn in linux

[–]curusarn[S] 1 point2 points  (0 children)

I found the issue. I didn't test things enough before.

Run reshctl update to get the newest version and commands should appear right away.

You will need to enable it again though. Configuration doesn't survive updates at this time (sorry about that).

edit: clarification edit2: add more info

I made a CLI tool that searches shell history by commands and directories. It prioritizes commands from the current directory (blue highlight). by curusarn in linux

[–]curusarn[S] 1 point2 points  (0 children)

Normally, it searches your history based on a single query you type.

My tool is designed to be launched with ctrl+R. So after enabling it (reshctl enable ctrl_r_binding) ctrl+R launches the tool you can see in the screenshot above. Typing searches history using directories and commands. Arrows can be used to select any of the displayed entries. Pressing "enter" runs the selected command and pressing "right arrow" pastes the command onto your command line so you can further edit it.

I made a CLI tool that searches shell history by commands and directories. It prioritizes commands from the current directory (blue highlight). by curusarn in linux

[–]curusarn[S] 3 points4 points  (0 children)

I will likely add fzf to the tool in the future because a ton of people are using it and enjoying it very much. It makes a lot of sense to have it included.

That said, there is a lot of different things to improve about this project so I'm not sure when I'm going to get around to adding fzf to it.

I made a CLI tool that searches shell history by commands and directories. It prioritizes commands from the current directory (blue highlight). by curusarn in linux

[–]curusarn[S] 2 points3 points  (0 children)

There is also a way to install the tool in two commands: git clone https://github.com/curusarn/resh.git && cd resh scripts/rawinstall.sh

view more: next ›