LegendFinder
New Member
how do i fix neofetche not working in linux mint terminal
my neofetch is not working how do i fix it
- Thread starter LegendFinder
- Start date
Don't know if this has anything to do with it.
Condobloke
Well-Known Member
G'day leendFinder, Welcome to Linux.org
WHich Linux Mint are you running?....version number...eg Linux Mint 21.3 ?.....etc /
neofetch still works in Linux Mint 22.1
Give us some more detail please
WHich Linux Mint are you running?....version number...eg Linux Mint 21.3 ?.....etc /
neofetch still works in Linux Mint 22.1
Give us some more detail please
Welcome to the Forum.
I think you may have spelt it incorrectly because it works as does fastfetch in Mint Cinnamon 22.1.
Try typing neofetch.
Ayup. A definite "typo"....
Despite Neofetch being discontinued, it should still keep working on any modern distro. Neofetch - like its replacement Fastfetch - is entirely script-based.....so no compiled binaries, and thus nothing to "go wrong" from one distro to another.
The same version that runs on a 64-bit Ubuntu or Fedora should also run on a 32-bit MX-Linux.....
Mike.
new_vintage
Member
The fastfetch in the openSUSE and Fedora repos is written in C and compiled.
That is where fastfetch's name comes from.
I don't know about elsewhere.
The
But, that suits many people just fine. It wasn't that long ago that the project was scuttled. If one had energy and motivation, they could fork the project to something new. It does mean a tedious and steady stream of updates will be required which is why the original author quit. There's no, "Someday this will be done!" No, it's more like, "Well, it's up to date as far as I know. It won't be long before it requires more work."
So, as things change so too will its utility. That's okay. There are alternatives and it was itself an alternative to prior software (like
neofetch application will continue to work properly with things it recognizes or gleans from system files. Eventually, it will stop knowing what CPUs you're using (for example) as those are newer than it has data for. It will eventually no longer be fit for purpose except on older hardware.But, that suits many people just fine. It wasn't that long ago that the project was scuttled. If one had energy and motivation, they could fork the project to something new. It does mean a tedious and steady stream of updates will be required which is why the original author quit. There's no, "Someday this will be done!" No, it's more like, "Well, it's up to date as far as I know. It won't be long before it requires more work."
So, as things change so too will its utility. That's okay. There are alternatives and it was itself an alternative to prior software (like
screenfetch).
Condobloke
Well-Known Member
@LegendFinder , have you solved this problem ?
There are a lot of answers here, but we have not heard back from you.
Your input is required. Talk to us, please.
There are a lot of answers here, but we have not heard back from you.
Your input is required. Talk to us, please.
Last edited:
Hi David, how did you get neofetch and screenfetch to look different? And what is the purpose behind that?
I'm thinking that you mean me. They're (both words) set to use the code tag, similar to
[code]text[/code] except I do it with markdown, which this forum partially supports In that case, you use the ` mark on either side of the word, saving you time and effort. You just put one before the text you wish to indicate is code and one after. You can also use the code tags.Many people only use the code tag like this:
sudo apt updateBut, you can also just put
sudo apt update inline and that's what I have done in the post above and in this post. You can use the BBCode 'code' tags, as indicated in the first paragraph, or you can just use tick marks.NOTE: The tick marks only work for single lines of code or inline code as demonstrated below.
`sudo apt update
sudo apt upgrade -y`
If you're interested in markdown, it's just a quick way to format text. Many sites support it. This site uses BBCode, but it also supports a subset of markdown, such as italics and bold. It only supports a limited few bits of markdown, which I think is unfortunate. Once you learn to format text with markdown, you'll see that it is a bit limited (or clunky in areas) but not bad for just the basics needed to post on a general forum.
It's what's used elsewhere, like the bevy of StackExchange sites, Reddit, etc...
Condobloke
Well-Known Member
sudo apt-get autoremove
Condobloke
Well-Known Member
Using the incorrect ' mark did not help
Thank you !
Thank you !
Yup. It's the tick, not the single quote.
Let's see if this breaks anything...
Code:
*italics*
**bold**
***bold italics***
> blockquote
`code`That's the markdown that I know works here. The full assortment is not supported. That may be because of BBCode already being an option, or maybe they interfere with other bits of formatting. I don't know why only part of them are supported. Then again, I've never looked to see if there's a given reason.
