Updated my -current installation and looked through the changelog, but didn't see this fixed. The patch to the SlackBuild below should resolve the problem. Reposting for visibility, as I am guessing the first post was missed.

1 members found this post helpful.

I'm running current from today and I'm not having this problem.

This is a plea to add the original sc back to Slackware.

I noticed that sc was replaced by sc-im in 2018, as I was looking for the sc
source code. I was a bit sad to see the original and venerable sc had
disappeared. Sc-im may call itself `sc improved', but it is not comparable to
`vi improved', IMHO anyway.

About sc-im crashes:

I used sc-im for a year or so in 14.2 before switching back to the
original sc. The main reason I stopped using sc-im is that it
crashes/seqfaults so damned often. It is so bad that I made a
ctrl-x keybind to :write! files before doing any kind of complex
operation (i.e. more than just manually typing text or numbers in),
but it mostly crashed when I used that too(!)

When I say `often', I mean perhaps once in every 5 operations that
involve moving or copying data around, or copying cells containing
evaluations or functions. This makes it pretty unusable.

I did save some logs to report the issue on github, but never got
around to it, as I found that plain sc was rock solid, so I deleted
them. I didn't consider that sc-im was important or popular enough
to spend time on it, but I can probably recreate some and report it
if necessary.

Other reasons:

Other than stability, I guess it's mostly my opinions on why sc is
better than sc-im, but I'll list a few anyway.

I haven't looked at sc-im's source code, so I don't know exactly how
much of original sc was used, but it seems some features were removed
to make sc-im. There was no reply from the dev when I asked on
github about perhaps adding some kind of macro support, not realising
that he had probably removed them in the first place. sc also
supports vi-like abbreviations, although I haven't yet figured out
how to use them (which is why I wanted to look through the source in
the first place.)

The main reason for using sc-im is for the `undo' feature, but it
doesn't work on *all* operations - there is still no way to get back
to the original state a file was opened in other than reopening it
and discarding all edits. sc-im's visual mode is nice too, but sc
also supports visual selection with any kind of `range' operations.

I just tried doing a *very* quick and dirty comparison of @()
commands with the help and man pages for both applications:

egrep '^ @[a-z]+\(' /usr/share/sc-im/sc-im_help | wc -l
61

man sc | egrep -o '^ @[a-z]+\([^)]+\)' | wc -l
82

Other things like exiting sc by pressing `q' no longer work in sc-im,
but there *is* much better colour and keybind support, although it
unfortunately makes the files slightly incompatible with the original
sc. sc also comes with `psc', which is used to convert other file
types to sc format, and works great on CSV files, so sc-im's CSV and
TSV importer isn't really that special.

Well I hope that this makes a convincing argument in support of sc.

4 members found this post helpful.

Just two remarks:
1. the "original" sc isn't all that original and was abandoned once before, taken over by a new maintainer, but there hasn't been done anything by him (or anyone else) since about two years. There is even an issue for a new maintainer:github.com/n-t-roff/sc/issues/18
2. sc-im is not "improved" but "improvised"; according to its github page
Its last release was in 2017 too, although there are 119 commits to that version, the last being on Feb 10, 2020 (according to that same github). But that hasn't resulted into a new release (yet?).

1 members found this post helpful.

Interesting... I could swear I was still having the problem even if I gave man the full path the page, but now that seems to be working. That is specifically running works fine:

However, just invoking exits with code 16, which is: And double checking the man page shows that is still requesting the version file:
Running man and less on the extracted page in my home directory works. Under man no errors are reported, but when using less it reports the errors that my patch is supposed to fix:
Can anyone else verify if this is a problem, or lend some light on what is busted in my configuration? I haven't changed the configuration relating to the man pages as far as I know (e.g. no environment variables for man are set, mandb cron job is still running daily, etc.)

I can verify. Thanks for the report.

2 members found this post helpful.

I know the history of sc, but still it is rock solid and has never crashed on me once.

As for the `improved', the first time I came across it that's how it was named. Just a quick search on ddg found https://pkgsrc.se/math/sc-im

I realise that sc-im is likely more active than sc, but it's been unusable with all the random crashing. But I'm not asking that it be removed; I'm asking if sc can be reinstated.

2 members found this post helpful.

As it doesn't change anymore, you can just install it from the 14.2 tree. It effectively has become "pasture" now - no new versions anymore.

Continuing to use a package from an older release isn't the way we do things

If this request goes nowhere then I'll probably maintain it on SBo myself when 15.0 is released.

Actually, I rescind what I just said about keeping sc-im, because I care that Slackware's rock solid stability is affected. I'm sure that you would think it a problem too, if something you were using was continually crashing all the time

I don't know why you have such animosity towards the idea. AFIAK this is a thread for requests, not running arguments. I made a simple request and highlighted a problem for Pat and the team.

1 members found this post helpful.

Mesa 20.0.4 has been released to fix a regression.
https://www.mesa3d.org/

2 members found this post helpful.

I don't have any animosity towards the idea (nor to you).
Just wanted to point out that REadding an obsolete package isn't really the way forward in a testing pre-release like -current. Probably sc-im should be removed too, according to you it really doesn't seem an improvement.

I don't use sc at all, but have you reached out to the developers with crash reports? It may be possible that they aren't seeing it there and they need to have reports from users to try and fix it.

I will get some crash logs soon and let the guy know.

As XFCE 4.14 will be coming and GTK3 already has, I'd love to see webkitgtk3 added to Slackware 15.0. There are more and more packages based on it and it seems like the SBo version constantly needs to be recompiled in -current for whatever reason if deciding to use it. As qtwebkit was added for qt5, only seems fair.. and worthwhile to incorporate it. The compile time is also atrocious lol..

(and hi `dive`! long time )

1 members found this post helpful.

Thanks Pat , and Hey phantom_cyph

To be fair, a quick check shows there have been some fixes for segfaults in
sc-im's git log since the last release. These ones are since I last used it:

Release/tag dates:

1 members found this post helpful.