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.
I just wish there was a fast, usable GUI like a combination of Windows 3 (program groups) and 9x/ME (start menu) without too many fancy things, like no forced animations, but with KDE conveniences like system-tray w/volume & w/clipboard, pinned/disappearing/reappearing panel ‘launchers’ (option to pin when you right-select a program on taskbar,) gradient background, and some system-tray 'widgets.'
GDB 8.3.1 + python 3.8.1 we have in -current has a problem cooperating with Emacs' GDB-mode.
The problem comes from the fact that Python linked with GDB prints a warning about wrong usage of "is not" construct,
and emacs' gdb-mode cannot parse it.
The file in question is /usr/share/gdb/python/gdb/command/prompt.py, lines 48 and 60.
GDB 8.3.1 + python 3.8.1 we have in -current has a problem cooperating with Emacs' GDB-mode.
The problem comes from the fact that Python linked with GDB prints a warning about wrong usage of "is not" construct,
and emacs' gdb-mode cannot parse it.
The file in question is /usr/share/gdb/python/gdb/command/prompt.py, lines 48 and 60.
Distribution: Slack 15.0 64 using Plasma 5.15 on Dell Inspiron 3847 8GB RAM with Dell 24inch monitor 1920x1080
Posts: 116
Rep:
Plasma 5 Desktop Icons
It is somewhat more involved to alter the icon spacing in the Plasma 5 Desktop.
With MS Windows the icon spacing vertically and horizontally are straightforward values to change.
If the Desktop Configuration could include such a facility that becomes a permanent part of the configuration until explicitly reset or altered it would be a very useful facility.
Some of us are very particular about the User Interface and look for high levels of control therein.
It is somewhat more involved to alter the icon spacing in the Plasma 5 Desktop.
With MS Windows the icon spacing vertically and horizontally are straightforward values to change.
If the Desktop Configuration could include such a facility that becomes a permanent part of the configuration until explicitly reset or altered it would be a very useful facility.
Some of us are very particular about the User Interface and look for high levels of control therein.
Well, first of all: Plasma5 is not part of Slackware-current.
Second, the question you have is about user preference. Slackware is a distro which is agnostic to user preference. What you should do is open an enhancement request at https://bugs.kde.org/ if you need more granularity in your control over desktop icon spacing.
nvi doinst.sh: 'ex' link fails because 'nex' is a link that
is created afterwords.
/var/lib/pkgtools/scripts/nvi-1.81.6-x86_64-1
Code:
# If there's no ex link, take over:
if [ ! -r usr/bin/ex ]; then
( cd usr/bin ; ln -sf nex ex )
fi
( cd usr/bin ; rm -rf nex )
( cd usr/bin ; ln -sf nvi nex )
You should be able to link 'ex' directly to 'nvi' (untested).
It shouldn't matter what order the symlinks are created in.
Yes, of course you are right. I saw your ChangeLog note, but I
didn't know vim would clobber ex, but not vi. I checked my
upgrade logs and the install order was:
elvis
nvi
vim
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
