Is there a good, user friendly editor that would take the place of kate? Definitely not Emacs or Vi if I can get away from it! I do use nano for a very little bit of editing configuration files, so maybe that's sufficient - kate was more like a notepad to me.

For MX 17, we switched to Featherpad as the default text editor because it had a tiny added footprint, has a lot of features which can be switched off or on in the settings so it can look like a dead simple notepad-like editor or you can use it for complex code editing, and the developer is very responsive to requests or to bugs. It's recently been added to upstream Debian, but even that 0.7 version is falling behind with some of the newer features like auto-save and date-time hotkey entry being added since then. The Debian packager has been behind many of the latest added feature requests.

Well, I always thought I was kinda normal, but sane? No one has ever accused me of being sane ;>).I went into every directory that contained firefox-esr and removed the firefox-esr files .... obviously I made the wrong, wrong choice! - but now I know what is the correct command to use!THX!

I purged firefox-esr, tried the bash script, and got this message "Failed to execute default Browser input/output Error"After doing a lot of research on the web, I find that it's somehow connected with Google Chrome and Chromium - neither of which I have installed or ever used. I then tried the MX firefox, as suggested by Steven Pusser, but every time it opened up, I got an MX pic and ad, instead of firefox-branded page. Then I had to change it to wherever I wanted to go. I have now d/l'ed Midori as a backup browser, but I'm still working on installing the 'real' Firefox, but it will have to be from a download/extract/run. Every time I purged the MX firefox and ran the bash script again, when I would click on the icon on the bottom of the desktop, I got the MX Firefox page - AFTER I'd purged it! I never did get the 'real' one from the bash script ....

jppattison wrote: I then tried the MX firefox, as suggested by Steven Pusser, but every time it opened up, I got an MX pic and ad, instead of firefox-branded page. Then I had to change it to wherever I wanted to go. I have now d/l'ed Midori as a backup browser, but I'm still working on installing the 'real' Firefox, but it will have to be from a download/extract/run.

MX Firefox is the real Firefox, probably with home page set to MX. You just need to go into preferences and set your home page to whatever you want.

“ computer users can be divided into 2 categories:Those who have lost data...and those who have not lost data YET ”Remember toBACKUP!

jppattison wrote: I then tried the MX firefox, as suggested by Steven Pusser, but every time it opened up, I got an MX pic and ad, instead of firefox-branded page. Then I had to change it to wherever I wanted to go. I have now d/l'ed Midori as a backup browser, but I'm still working on installing the 'real' Firefox, but it will have to be from a download/extract/run.

MX Firefox is the real Firefox, probably with home page set to MX. You just need to go into preferences and set your home page to whatever you want.

Yes, we add a custom distribution.ini file that goes to MX Linux, like many distros do for theirs (Ubuntu). That also gets added to your profile in the .mozilla folder in your home folder, which is why you can't get rid of it by simply deleting the package, but it's simple enough to change the home page.

Sorry folks, I had edited that last post 2 or 3 times, so I guess that what I thought was a preview, ended up a couple of posts. late night!The upshot of it is that I am using the MX Firefox. but as someone said, I just set my own home page. I'm leaving it at that for now. Even tho I'm retired, I have other responsibilities, so at this time I want to thank all who helped, gave advice, etc. for my problems with this setup. I only had to re-install four times! A couple of times was because of a couple of bonehead mistakes I made along the way,(and I had a lot of fun practice and learned a lot along the way as well), but it's going to be what I've got now, no more messing around - and hopefully the last time I have to re-install. THANKS ALL!!jppattison

stevepusser wrote:For MX 17, we switched to Featherpad as the default text editor because it had a tiny added footprint, has a lot of features which can be switched off or on in the settings so it can look like a dead simple notepad-like editor or you can use it for complex code editing, and the developer is very responsive to requests or to bugs. It's recently been added to upstream Debian, but even that 0.7 version is falling behind with some of the newer features like auto-save and date-time hotkey entry being added since then. The Debian packager has been behind many of the latest added feature requests.

oh, that looks very interesting! i'm looking for a geany replacement on my arch desktop...the 0.7 release is from Jan 17 - that can't be too old?or are you saying all these new features cropped up in the last 4 weeks?

(i'm talking abotu archlinux here. i can always build from the latest git master, but i'd prefer a release)

stevepusser wrote:For MX 17, we switched to Featherpad as the default text editor because it had a tiny added footprint, has a lot of features which can be switched off or on in the settings so it can look like a dead simple notepad-like editor or you can use it for complex code editing, and the developer is very responsive to requests or to bugs. It's recently been added to upstream Debian, but even that 0.7 version is falling behind with some of the newer features like auto-save and date-time hotkey entry being added since then. The Debian packager has been behind many of the latest added feature requests.

oh, that looks very interesting! i'm looking for a geany replacement on my arch desktop...the 0.7 release is from Jan 17 - that can't be too old?or are you saying all these new features cropped up in the last 4 weeks?

(i'm talking abotu archlinux here. i can always build from the latest git master, but i'd prefer a release)

Yes, the developer has been quite active. Take a look at the closed issues on the github. He decided to bump the next release version to 0.8 due to all the additions. The tilde "~" I add to the version means it's a pre-release version. Many of the new feature requests have come from the Debian package maintainer, and the date-time entry request was relayed by me from a MX user. The cursor position in the line option on the status bar is mine. It's getting really handy for editing Debian packaging files such as the rules and control files, too. I built a new version from git yesterday for MX 17 main to use the new features.

I also managed to package the current Qupzilla 2.2.5 AppImage into a deb for MX, since that's not practical to build from source on Stretch, let alone Jessie. That makes it easy to add to our package installer. I learned I had do some extra tricks, at least for this AppImage. It installs into /opt/qupzilla...I don't think qupzilla has auto-update.