thanks, that's OK. As long as it's not my fault I can live with the restriction. ;)

Except WordPerect, OpenOffice.org, LibreOffice, etc. should never be used for editing plain text configuration files, of course. If you've even copied a one line command from the Net where the -- was converted to an M-dash you know what I mean.

For editing config files purpose vi, Emacs and nano shine. With any other editor there might be an issue with how temp files are handled. I had a problem with pico in the distant past not letting me edit a large /etc/passwd file on a university server due to a full / partition.

DNA
AKA mrascii

wordgrinder is a nice console wordprocessor similar to the old DOS Wordstar (but simpler). I wish there was a way to get it to work in Slackware. Anybody has got lua + luafilesystem working on Slackware? Please share your knowledge!

WordGrinder looks promising, and on the one hand I'd also be interested in getting it working on Slackware. Howeer, it has many dependencies....

gargamel

It has only two dependencies: lua and the lua module "luafilesystem".

Unfortunately, the installer has some issues. I got lua working through SlackBuilds.org site, but luafilesystem does not work properly - i.e. it installs no .lua files in the lua directory. Also I tried installing luafilesystem through luarocks. luarocks compiles and installs perfectly on Slackware, but installing luafilesystem through luarocks also doesn't do the trick.

Strange issues. Wonder whether I should use the Debian packages and use alien to install the respective packages.

I've tried to prepare two slackbuilds (for fun :) ): install lua first

http://ponce.cc/slackware/testing/luafilesystem/
http://ponce.cc/slackware/testing/wordgrinder/

but I think wordgrinder has become unmaintained.

Thanks I will give it a try. :)

Wonderful, ponce! It works. I wish I was a better shell scripter. I like the way your SlackBuild made this so easy, compared to having doing it by hand. :)

You are right, I should have said "hard to resolve" dependencies, at least on Slackware and, at least, for me. However, ponce seems to have made it (again, like with Digikam and other programs...). Thanks to Ponce, then! :)

gargamel

deleted.

Or maybe it's just ready. ;)

gargamel

Back to OT, Xfce 4.10.

It runs fine here, but I wonder, if the following is a bug in Xfce or if it just happens here. The dialog for appearance settings offers me six (6) icon themes, but:

- two of them are incomplete: Nuvoladesign and Monochrome. I wonder, why they are still shipped with Xfce...
- there are two entries for Oxygen; I can't notice any difference between them...
- the beautiful theme and icons used for 'advertising' on the Xfce homepage is not there...

So if one wants Xfce to look neither GNOMEish nor KDEish, the only stock option is Tango. That was already the case with Xfce 4.6, and I have had some hope that it would be fixed. I'd be interested in a complete set of Nuvoladesign or Monochrome icons.

Now, my question is: Do you have the same, or did something go wrong here, during the upgrade to -current?
If it is an intrinsic Xfce problem, I'll research their bug tracker, and if noone else has done so, I'll file a bug report.

gargamel

Well, usually, I don't quote myself. ;)
But in this case there's progress: I found Faenza icons at SlackBuilds.org. What I am still missing is the Greybird theme. Actually I found the original source, but I don't know, how to make a Slackware package for it. Can anyone give a little advice on that, please?

Thanks a lot!

gargamel

I have a SlackBuild for greybird. I could post a link tomorrow if you want (it's getting late over here).

I'd really appreciate that!

gargamel