Requests for -current (14.2-->15.0)

NonNonBa · 12-23-2019, 04:22 AM

Quote:

Originally Posted by upnort

As I remember, [...]

I agree, but my main point is that you can already do everything you want regarding this (mount a tmpfs in /foo linked as /tmp, or echo tmpfs /tmp $YOUROPTIONS >>/etc/fstab). It's up to you, straightforward, and transparent for the distro. Maybe I miss something, bit I hardly see the benefit/goal of a standard toggle for this particular mount point.

upnort · 12-23-2019, 11:40 AM

Quote:

Also, yes, I know that /var/tmp is intended to be persistent. That's nice. I don't care.

Yup, your system, you do what you want.

That's the way all computers should be and something Slackware does for all of use nicely. The important point for me is somebody on the dev team agrees with the spirit of my request. Would be nice if there was a convenient global way to toggle this in Slackware.

mats_b_tegner · 12-24-2019, 04:08 AM

Nano 4.7
https://www.nano-editor.org/news.php
https://www.nano-editor.org/dist/v4/nano-4.7.tar.xz
https://www.nano-editor.org/dist/v4/nano-4.7.tar.xz.asc

GazL · 12-24-2019, 04:53 AM

Quote:

Originally Posted by NonNonBa

Do we really need a new rc.*?

It wouldn't be my preference. I already dislike the rc.loop file, whose existence I just can't understand the rationale for.

IMO putting /tmp on tmpfs is something that should be left to the system admin to choose to do: by editing fstab, or creating a symlink if that is their preference.

upnort · 12-24-2019, 11:33 AM

Quote:

IMO putting /tmp on tmpfs is something that should be left to the system admin to choose to do

Yes, I agree. I'm only proposing a common mechanism that can be toggled in Slackware.

shastah · 12-25-2019, 05:54 AM

Quote:

Originally Posted by upnort

All I am proposing is a convenient one-stop location for the configuration in Slackware because currently non exist.

The way I see it, that "one-stop location" does in fact exist, and is called /etc/fstab

Jeebizz · 12-25-2019, 11:05 AM

So, any chance of updating to XFCE 4.14?

swaggboi · 12-25-2019, 03:40 PM

Quote:

Originally Posted by Jeebizz

So, any chance of updating to XFCE 4.14?

this++

Jeebizz · 12-25-2019, 08:17 PM

Also QT5 and yea any status on Plasma?

SCerovec · 12-26-2019, 02:18 AM

Quote:

Originally Posted by Jeebizz

So, any chance of updating to XFCE 4.14?

I may add the opinions on 4.14 are split.

I, for one, have nothing against it - as I test ran it from a clean slate. Others seemed to have aggravations of several kinds.

YMMV

anon074 · 12-26-2019, 03:54 AM

There's a bug in Ruby's reline module. If the history size is set in ~/.inputrc, irb exits with "false can't be coerced into Integer". Reported as https://github.com/ruby/reline/issues/94. As a temporary fix I patched reline/config.rb.

Code:

--- /usr/lib64/ruby/2.7.0/reline/config.rb.orig 2019-12-25 10:50:58.000000000 +0100
+++ /usr/lib64/ruby/2.7.0/reline/config.rb      2019-12-26 10:39:35.301227689 +0100
@@ -186,2 +186,6 @@
     case name
+    when 'history-size'
+      if value.match?(/\A-?\d+\Z/)
+        @history_size = value.to_i
+      end
     when *VARIABLE_NAMES then

bassmadrigal · 12-26-2019, 10:08 AM

Quote:

Originally Posted by SCerovec

I may add the opinions on 4.14 are split.

I, for one, have nothing against it - as I test ran it from a clean slate. Others seemed to have aggravations of several kinds.

YMMV

Many of the complaints I read were related to the fact that it doesn't feel any different than 4.12, which was the goal of the xfce developers. They were just trying to migrate to gtk3 and weren't planning on implementing many changes visible to the user. The next version of xfce should see more noticeable changes by end-users. But there were also a few complaints due to issues with theming, but I believe those are more due to the gtk3 change and I don't believe it is something xfce can do much about.

But I'm not really an xfce user (except for when I break KDE), so I don't really have a horse in the race.

SCerovec · 12-27-2019, 02:30 AM

Quote:

Originally Posted by bassmadrigal

[snip]
But I'm not really an xfce user (except for when I break KDE), so I don't really have a horse in the race.

That is exactly how i become an XFCE user - KDE stayed broken for too long and i stopped checking if it works again...

bassmadrigal · 12-27-2019, 10:26 AM

Quote:

Originally Posted by SCerovec

That is exactly how i become an XFCE user - KDE stayed broken for too long and i stopped checking if it works again...

I don't think this will happen, because I'm quite annoyed with many things XFCE (why the crap does it default to mirrored on my monitors after they wake up? It boots up with them extended like I'd expect, but then resets to mirrored when they go into standby). It's decent enough that I can deal with it, but my first chance back to KDE, I'll take it.

And KDE tends to only break when I do drastic things on my system. Right now, it's because I've been trying to upgrade the video stack to support my newer video card without switching to -current.

montagdude · 12-27-2019, 11:38 AM

Quote:

Originally Posted by bassmadrigal

I don't think this will happen, because I'm quite annoyed with many things XFCE (why the crap does it default to mirrored on my monitors after they wake up? It boots up with them extended like I'd expect, but then resets to mirrored when they go into standby). It's decent enough that I can deal with it, but my first chance back to KDE, I'll take it.

And KDE tends to only break when I do drastic things on my system. Right now, it's because I've been trying to upgrade the video stack to support my newer video card without switching to -current.

Plasma 5 on -current is nice and stable right now.