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.
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.
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.
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.
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
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.
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.
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)
On 2014-03-04 17:06, tsu2 wrote:
> 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).
IMHO, you should not require to go to a CLI to create a new file like that.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Ah. That is a description on how to do this. I can now do this also. I have Dolphin 4.11.5. And when I create a file new.ini in the way described, it is called new.ini.
My conclusion, when a newer version of Dolphin (that is newer then the official openSUSE 13.1 one) does add that .txt suffix, then that is a bug IMHO. I am not sure if one should file this at the openSUSE Bugzulla or direct at KDE (maybe both?)
I must add that I never have done this before. And what is created is a bit strange. It is a two character file with the characters space and line-feed. I miss completely how this can be useful. But when anybody sees a use for it, then (s)he is correct that it should function correct. The problem here seems also that the OP thinks that what he uses everyday, is used by almost all other people and that his/her a precise description is not needed. Alas, this is not the case. Unix/Linux has many ways to do things and most people use only a small subset.
On 2014-03-04 18:06, finders wrote:
>
> 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.
I just tried with Dolphin 4.11.5 (default openSUSE 13.1), right clicked
on an empty directory, selected “create new”, then “Text file”. I
entered as name “pepe.ini” and got “pepe.ini.txt”.
But this is not a bug, it is intentional. I asked for a text file, and
got a text file, ie, “.txt”.
Me, I would prefer the logic to see that I did type an extension, and
that the software did not try to be so clever and add another extension
automatically. Windows does exactly the same and I hate it.
I’m not familiar with KDE. Maybe there is a template folder where you
can define the types of “new” files you can create, and there add a
“create ini file” entry. Dunno.
Or maybe the action to add the extension automatically can be configured
somewhere - as I said, I’m not that familiar with KDE.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2014-03-04 19:26, finders wrote:
> 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.
Please, don’t be mad at us 
We automatically assume you are asking for help, because the purpose of
this forum is to ask for help. Non help requests are typically moved by
moderators to other, more appropriate, subforums here.
If you are trying to report a bug, well, this is not the place. Bug
reports are made on Bugzilla:
openSUSE:Submitting bug
reports
(my guess is they will tell you to report this thing upstream, as it is
probably an “intentional feature”. Just a guess, though).
If your intention is to ask whether something is a bug or not, prior to
reporting it, then just say so on the first post, so that people don’t
get confused
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2014-03-04 21:48, Carlos E. R. wrote:
> On 2014-03-04 18:06, finders wrote:
> I just tried with Dolphin 4.11.5 (default openSUSE 13.1), right clicked
> on an empty directory, selected “create new”, then “Text file”. I
> entered as name “pepe.ini” and got “pepe.ini.txt”.
>
> But this is not a bug, it is intentional. I asked for a text file, and
> got a text file, ie, “.txt”.
And if I hit “F2” to rename the file, it automatically highlights the
name, only, skipping the .txt extension. It is mimicking the Windows
explorer behaviour.
At least it shows it, doesn’t hide extensions >:-)
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 03/04/2014 03:58 PM, Carlos E. R. pecked at the keyboard and wrote:
> On 2014-03-04 21:48, Carlos E. R. wrote:
>> On 2014-03-04 18:06, finders wrote:
>
>> I just tried with Dolphin 4.11.5 (default openSUSE 13.1), right clicked
>> on an empty directory, selected “create new”, then “Text file”. I
>> entered as name “pepe.ini” and got “pepe.ini.txt”.
>>
>> But this is not a bug, it is intentional. I asked for a text file, and
>> got a text file, ie, “.txt”.
> And if I hit “F2” to rename the file, it automatically highlights the
> name, only, skipping the .txt extension. It is mimicking the Windows
> explorer behaviour.
>
OH NO we’ve been infiltrated. Run for the hills.
Ken
On 2014-03-04 21:56, hcvv wrote:
> I must add that I never have done this before. And what is created is a
> bit strange. It is a two character file with the characters space and
> line-feed. I miss completely how this can be useful. But when anybody
> sees a use for it, then (s)he is correct that it should function
> correct.
I guess (because that is how Windows does it, and I looked it up a
decade ago), that there is a folder with a sample of each of those empty
new files.
For instance, you can select “create new spreadsheet document”. It does,
and you can double click on it and Libre Office opens it, automatically.
> cer@Telcontar:~/tmp/AAA.1> l
> total 16
> drwxr-xr-x 2 cer users 53 Mar 4 22:13 ./
> drwxr-xr-x 66 cer users 4096 Jan 22 00:46 ../
> -rw-r--r-- 1 cer users 6301 Mar 4 22:12 Spread Sheet Document
> -rw-r--r-- 1 cer users 2 Mar 4 21:36 pepe.ini.txt
> cer@Telcontar:~/tmp/AAA.1> file Spread\ Sheet\ Document
> Spread Sheet Document: OpenDocument Spreadsheet
> cer@Telcontar:~/tmp/AAA.1>
Somewhere there is a template for that new file, and it can be changed,
or new templates added. I guess.
This is a common usage pattern in Windows, many people use it. I used it
a lot when I used Windows. People expect to find those features in
Linux, too. You don’t use it, I almost do not use it, but many other
people do
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 03/04/2014 04:53 PM, Carlos E. R. pecked at the keyboard and wrote:
> On 2014-03-04 21:56, hcvv wrote:
>
>> I must add that I never have done this before. And what is created is a
>> bit strange. It is a two character file with the characters space and
>> line-feed. I miss completely how this can be useful. But when anybody
>> sees a use for it, then (s)he is correct that it should function
>> correct.
> I guess (because that is how Windows does it, and I looked it up a
> decade ago), that there is a folder with a sample of each of those empty
> new files.
>
> For instance, you can select “create new spreadsheet document”. It does,
> and you can double click on it and Libre Office opens it, automatically.
>
>
>> cer@Telcontar:~/tmp/AAA.1> l
>> total 16
>> drwxr-xr-x 2 cer users 53 Mar 4 22:13 ./
>> drwxr-xr-x 66 cer users 4096 Jan 22 00:46 ../
>> -rw-r--r-- 1 cer users 6301 Mar 4 22:12 Spread Sheet Document
>> -rw-r--r-- 1 cer users 2 Mar 4 21:36 pepe.ini.txt
>> cer@Telcontar:~/tmp/AAA.1> file Spread\ Sheet\ Document
>> Spread Sheet Document: OpenDocument Spreadsheet
>> cer@Telcontar:~/tmp/AAA.1>
>
>
> Somewhere there is a template for that new file, and it can be changed,
> or new templates added. I guess.
>
>
> This is a common usage pattern in Windows, many people use it. I used it
> a lot when I used Windows. People expect to find those features in
> Linux, too. You don’t use it, I almost do not use it, but many other
> people do
>
>
>
But in linux we never used an extension to specify the content of a
file. Perhaps retraining windows converts is a better plan of attack.
Ken
Personally, I prefer if it just uses the file extension I provide, but I do not have an issue with it. I find it is simple to just hit F2 right away, hit END, and delete it with the backspace key. Takes way longer to say than to do, and is no big deal to me.
Nope.
Most of us want more Windows users to convert to openSUSE Linux.
Thus, providing familiar methods to do things will make the switch more comfortable, less intimidating.
They come here, they start using it in familiar ways, then the retraining takes place by osmosis.
… and that way, fewer tend to go back.