Dolphin adds a txt extension to ini files

[finders]

Now every time I want to create a new.ini it creates a new.ini.txt
Creating new.sh works properly, it only happens with some extensions, not all.

[hcvv]

As usual, the only thing I seem to be doing on these forums is asking: Which version of opennSUSE? And that should awaken you, so that you volunteerly add that you use KDE (assumption from me, but not nessecarly true) and the if you use the standard version going with that openSUSE version or not. Thus we get at least an idea about the environment and the Dolphin version you are using.

And it never hurts to explain what you exactly do. Thus not sayjng you "create a file using Dolphin", but that you clicked on ... and then ........ I, e.g., have no idea how one creates files using Dolphin except using "copy" at a file drag from one place to another. And I also have no idea what some applications think that a file with the suffix .ini on it's name means.

[flymail]

On 2014-03-04, finders <finders@no-mx.forums.opensuse.org> wrote:
> Now every time I want to create a new.ini it creates a new.ini.txt
> Creating new.sh works properly, it only happens with some extensions,
> not all.

What happens in Dolphin if you press F4, type...

touch new.ini

.... and this press F4 again?

On 2014-03-04, hcvv <hcvv@no-mx.forums.opensuse.org> wrote:
> As usual, the only thing I seem to be doing on these forums is asking:
> Which version of opennSUSE? And that should awaken you, so that you
> volunteerly add that you use KDE (assumption from me, but not nessecarly
> true) and the if you use the standard version going with that openSUSE
> version or not. Thus we get at least an idea about the environment and
> the Dolphin version you are using.

Henk is absolutely right. I've openSUSE 13.1_x86_64 (KDE) and cannot reproduce this problem in Dolphin.

> And it never hurts to explain what you exactly do. Thus not sayjng you
> "create a file using Dolphin", but that you clicked on ... and then
> ........ I, e.g., have no idea how one creates files using Dolphin
> except using "copy" at a file drag from one place to another.

Within Dolphin, right click, select `Create New' > `Text File', but I'm guessing that's what the OP did.

> And I also
> have no idea what some applications think that a file with the suffix
> .ini on it's name means.

IIRC some Windows applications use `ini' extensions for configuration text files that initialise settings for some
applications (a bit like ~/.*rc) but I've never it used in Linux - although I guess there's no reason why it couldn't be
used.

[hcvv]

Within Dolphin, right click, select `Create New' > `Text File', but I'm guessing that's what the OP did.

I hate guessing what an OP did

[finders]

I hate guessing what an OP did

Dosbox programs use ini configuration files.
And yes, it happens on openSUSE 13.1 + KDE 4.12 (works properly on SLED 11)
Sorry about lack of info, I was in a hurry.

[tsu2]

To the OP:

Your Q has a logical answer.
Like practically any other File Manager, it wants to be able to automatically launch a "viewer" any time you click on that type of file.

When you created a new file, you almost certainly selected "text" which would mean that the File Manager needs to tag the file somehow so that it knows what type of "viewer" app to launch later on. The most common way to do this is to append a file extension which you have discovered.

To avoid appending a file extension, you shouldn't create the new file using a File Manager (or any Desktop GUI environment which typically will build on the File Manager's functionality).

Instead, you should create from a console.

Here are a few ways you can do this from a console.
"some text" is the contents of your text file to get started. Of course, you can always re-open and edit later even using a GUI text editor as long as you "Save" and don't "Save As."
"filename" is exactly what you want the file name to be, without any hidden suffixes.

Echo some text into a new file

echo "some text" > filename

Use the Vi console editing app pointing to a filename that doesn't already exist

vi filename

cat some text into a new file

cat >> filename << EOF
some text
some more text
EOF

HTH,
TSU

[finders]

Look, if I run "mcedit new.ini" and save the file in mcedit, it saves as new.ini, not new.ini.txt.
If I right click in dolphin 1.3, create new text file, and enter name "new.ini" it also saves new.ini without the txt extension.
In new dolphin from 4.12 it adds txt extension, which I don't need. Then I manually have to remove it, which is annoying.
Whatever, I give up on KDE 4.12 anyway, if I could downgrade to 4.4 I would do it right now.

[flymail]

On 2014-03-04, finders <finders@no-mx.forums.opensuse.org> wrote:
> Look, if I run "mcedit new.ini" and save the file in mcedit, it saves as
> new.ini, not new.ini.txt.

Look, if you follow the suggestions people offer you, people might be more inclined to help.

> If I right click in dolphin 1.3, create new text file, and enter name
> "new.ini" it also saves new.ini without the txt extension.

This is aimed at Henk: . But of course Henk is right: we shouldn't have to guess.

[finders]

On 2014-03-04, finders <finders@no-mx.forums.opensuse.org> wrote:
> Look, if I run "mcedit new.ini" and save the file in mcedit, it saves as
> new.ini, not new.ini.txt.

Look, if you follow the suggestions people offer you, people might be more inclined to help.

> If I right click in dolphin 1.3, create new text file, and enter name
> "new.ini" it also saves new.ini without the txt extension.

This is aimed at Henk: . But of course Henk is right: we shouldn't have to guess.

Quote the part where I was asking for help.
You just assume it's my fault the app is doing this and suggest I should get some help?
Last time I mention any bug on this forum, I'll just keep it shut from now on.

[robin_listas]

On 2014-03-04 11:28, flymail wrote:
> IIRC some Windows applications use `ini' extensions for configuration text files that initialise settings for some
> applications (a bit like ~/.*rc) but I've never it used in Linux - although I guess there's no reason why it couldn't be
> used.

I just did a "locate .ini" and found 726 instances. This is a full Linux
machine.

For instance: "/usr/share/texmf/tex/latex/latexconfig/latex.ini"

--
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)