Hunspell Dictionary in Solus question

brent

Axios mate uses pluma and the answer is yes and no.

It does not underline mispellings but it makes me go to Pluma menu.

gkg agjg agjarjg

Now dig this. I am in ungoogled and I took a picture of that gibberish ^ above. Of course it's never underlined spell check is broken.

But the right-click thing shows English is selected and on....
If I click "ehanced" it shows me a warning that whole post will be sent to google so we can use their dictionary instead. Pass.

Axios

brent By default, Flatpak downloads app-specific locale data (including translation files, locale and format settings, and dictionaries) for each app matching your system locale.
So if it work when you installed flatpak should keep working I would think
Unless maybe a flatpak update killed it?
I think its issues with flatpaks (should say flatpak app)
Ya I never clicked on the enhanced option...
And you alraedy did this config languages --set "en" and it will install the whole set of English variants with the “en” language

Staudey

brent It does not underline mispellings

huh, that seems like a bug. Will have to take a look tomorrow.

brent

tomscharbach bingo. if we knew "app issue" or "flatpak issue", if we knew one of them for sure it could get easier. the now you see it, now you dont thing suggests...no idea.

edit: limitations of a sandboxed app? period?

tomscharbach

brent limitations of a sandboxed app? period?

Nope. If that were the case, your Chromium Flatpak would exhibit the same behavior. It is something with the unGoogled Chromium Flatpak.

I agree with @Axios ("By default, Flatpak downloads app-specific locale data (including translation files, locale and format settings, and dictionaries) for each app matching your system locale. So if it work when you installed flatpak should keep working ...")

I don't know what is causing this, but I'm reasonably sure that unGoogled Chromium is the place to look for a cause, not Flatpak. @Axios might be right about an unGoogled Chromium update breaking something. I can think of two ways to check this: (1) install a distro that runs unGoogled Chromium native and see what happens, or (2) install the unGoogled Chromium appimage and see what happens, in both cases over time so that unGoogled Chromium updates.

brent

Axios I read the app-specific locale stuff. in these chrome/chromium knockoffs my locale is the only thing on (virtual reality, camera, mic, etc all off).
I hope that worked for a while thing is not a figment...I'm feeling nuttty lately🙂...but pretty sure it's been a pattern. Let's say I am nuts, it wouldn't change anything. A browser that can't spellcheck 95% of its life is the same as one that can't spell 100% of its uptime..
This particular browser is maintained by Eloston, who has spearheaded this project as least a decade now. Others may fork it but this is the true source. All that means is this is updated on Flatpak almost weekly which is very good for an app.

These sandbox things are tough. remember that keepassxc nightmare?

brent

Axios And you alraedy did this config languages --set "en" and it will install the whole set of English variants with the “en” language

it's probably already installed when I run that command. it goes back to $ right away like it did nothing. should use the --verbose arg next time.

brent

tomscharbach Axios
thank you both for your brain power I really needed it. I am going to try to build the ungoogled source targz into solus eventually. that would be the only way it works I think.

that you would stay up and help me figure this out really says a lot. thank you guys

brent

tomscharbach . I can think of two ways to check this: (1) install a distro that runs unGoogled Chromium native and see what happens, or (2) install the unGoogled Chromium appimage and see what happens, in both cases over time so that unGoogled Chromium updates.

1) I am the world's crappiest package maker. I get snagged with the first command and I'm always too embarrased to come here for help. I don't know what I should have installed to make a package and I still find compiling from source intimidating. Consistent fail. At the starting gate there is something I'm not wrapping my head around. after cd nothing workds...A hurdle I would like to clear this year. I only have 4 new years resolutions and building a package is one of them.
2) more likely as a scientific control maybe. appimage would show either 'sandbox limitation' or something entirely different.

Axios

brent Yup and had some of my own since dont remb what they were tho
They have a flatpak repair command to dont think it would be of help tho
Yup I put all my routers in a box couldnt handle it today but did get truesnas to boot on server.

brent

Axios Yup I put all my routers in a box couldnt handle it today but did get truesnas to boot on server.

one of those days! your wired and wireless are refusing to act in concert. days of mystery for sure

brent

Staudey I thought this was the furtherst from a Solus thing...shows how little I know. Flatpak Chromium is fine. Flatpak ungoogled no underline, no right-click to fix spelling. Thanks for taking a look. I'll see if there is anything I can do on the Flatpak end (flatpak repair --help) etc

« Previous Page