Porteus

On double clicking a txt file, "session chooser Kate" opens, when one wants a simple text editor to open.

assuming you're in KDE, right click on the text file, select Properties, then click on the tool button to the right of "Type: Plain Text Document". Then, highlight kate and select remove. That will take kate off of the list of applications (this will only survive reboot if you are saving changes).

Or, to continue using Kate, just select the box that says something like "always do this", and then "Open Current Session" or "Open New Session", and after that, text files will open directly to Kate (assuming you have your changes saved).

I'm sure there's a config file that could be saved to rootcopy or in a module, if you're running in Always Fresh mode. I just click "Open Current Session" every time, or right click, select "open with", and choose leafpad.

Thanks.

I think is necessary to make kwrite by default for txt files (32/64 bit)

kwite is already the default in 64-bit, as kate is no longer included (as of RC1 I think).

that presents yet another option for rnport: he could use rempkg to remove kate entirely from the kde module.

A newbie user get confused when he clicks a simple txt file to open it for viewing and gets a "Session chooser" dialog screen. It will put off many a beginner users if they feel even simple txt file management is either complex in this distro or there is some bug. I agree that kwrite should be default editor and it should promptly open the txt file. Kate is an advanced text editor; advanced users can make it their default editor.

I will make kwrite the default option. is this really a bug report? ... or a feature request?

Please read the FAQ for bug reports.

I agree it is a feature request. Please transfer this to correct area. But when I initially saw the message I did not know that Kate was an advanced text editor, so I thought this is some bug.

No problem. Will move it to newb questions. We need a section where people can ask for help. For future reference, a bug is not a bug unless it can be reproduce on multiple machines and is found to be the fault of Porteus.

The idea is to have a bugs section with very few threads ... it looks much better.

I strongly agree with you that users need an area to post their problems with porteus. Otherwise they will keep posting on other, more technical, parts of forum.