SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Request to recompile mc with --enable-aspell option to enable spellchecking with its internal editor. It looks like it just requires aspell to be installed, so there shouldn't be any additional dependencies. It was noted on this thread.
I second the request and no there is no other deps.
Also noteworthy - on build I had unknown option errors --enable-extcharset --enable-netcode --with-ext2undel --with-vfs
So unless they are introduced in the patch (I just built direct from source with your configure options) , might want to verify and clean them up too Pat.
Also there is a keymap to linkit to ctl-p if you enable aspell, be nice to enable it too
Seconded, and also guidance on how we can add the additional stuff (docs | extra | fonts).
In case Pat doesn't update to texlive-2021, the -docs/-extra(-fonts doesn't exists anymore, was merged in -extra) packages on SBo will have to stay
at version 2020, too.
If you now need 2021 on -current, your best option might be to uninstall the stock texlive package and go the route with
the generic texlive installation, https://www.tug.org/texlive/quickinstall.html
In case Pat doesn't update to texlive-2021, the -docs/-extra(-fonts doesn't exists anymore, was merged in -extra) packages on SBo will have to stay
at version 2020, too.
If you now need 2021 on -current, your best option might be to uninstall the stock texlive package and go the route with
the generic texlive installation, https://www.tug.org/texlive/quickinstall.html
Thanks @franzen for the update.
@volkerdi do you have any plans to update TeXLive to 2021? Just asking so that I know whether to wait for it or just go with the generic texlive. Thanks!
After the last updates (I did
Fri Jul 2 21:05:49 UTC 2021
Thu Jul 1 18:15:40 UTC 2021
Wed Jun 30 18:28:50 UTC 2021
together) after Plasma came up I was asked, for the first time I think, to give the root password so Plasma could read the SMART results something something. Is this to be expected?
I hope it's okay I didn't open a new thread, even though this is not a request.
After the last updates (I did
Fri Jul 2 21:05:49 UTC 2021
Thu Jul 1 18:15:40 UTC 2021
Wed Jun 30 18:28:50 UTC 2021
together) after Plasma came up I was asked, for the first time I think, to give the root password so Plasma could read the SMART results something something. Is this to be expected?
I hope it's okay I didn't open a new thread, even though this is not a request.
I normally have two Plasmas started for two different (non-root) users.
The dialog you mention, I observe it popping up quite often.
It would be nice it didn't behave like that.
In reference to AlienBOB's most recent post: my life has been messy the last few weeks but if/when things get back to normal I will recompile my libseat/sway packages and update to 1.6.1 from 1.6(they are currently built with slackbuilds based on AlienBOB's slackbuild generator) and then rebase the slackbuilds to whatever template / standards slackbuilds.org furnishes and ask whoever is the god at slackbuilds.org if he would have me as provider/maintainer for libseat/wlroots/sway slackbuilds. I am retired and when my life is running as it should , I need a hobbies. However, I have no coding background ( I have taken only one computer class in my life, FORTRAN for engineers in 1983 when homework programs were submitted on cards and the output from the computer science department wide communal dot matrix printer was collected the next day, and I haven't used and don't remember a single FORTRAN command any time in the last 30 years). In my professional life I did mechanical maintenance and replacement contracts for industrial installations and controls and power supply were by my electrical colleagues. In conclusion, maybe it would be an error to accept me as maintainer, because I am at a self taught hack at this linux business and a hack of the weakest sort at that. I just want my personnel linux boxes to do what I want them to do, and I look into linux deeply enough to do that until I succeed or acknowledge failure, and then move on to something else (like my motorcycles).
Hey biker_rat, thats cool. Dont worry, maintaining something is not so difficult, and I am sure you will be able to do it. I can tell you that bash is not so complicated and from what you wrote you will get it quickly. After that is just simply call the build script to do its job. When things go wrong you have a lot of people around on internet to ask for help
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.