Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fs: Can't open files with only one letter in the extension, ex: file.c #30

Closed
zBl4ckUser opened this issue Feb 17, 2021 · 10 comments
Closed
Labels

Comments

@zBl4ckUser
Copy link
Contributor

After creating a new file and opening it with gramcode, this appears:
image

@frednora
Copy link
Member

Cool :)
Very nice this test. Probably you created a new file using the command interpreter gdeshell.
In this case the command will create an empy file.
But it is not a bug. It is a 'work in progress' ... the function to create new files is very very primitive ...
See the routines in: gramado/landos/kernel/0mem/sci/fs/
Thank you.

Another test:
If you open gramcode with no file, so you can type something and save the new file with a standard name for now ...
this way you can reopen this saved file in the next session. ;)

@frednora frednora changed the title Bug: File creation error gramcode: Trying to open a file Feb 22, 2021
@frednora frednora added the test testing label Feb 22, 2021
@frednora
Copy link
Member

We need to do more tests like this one.
We can create files using the gramcode and using some commands in the command interpreter gdeshell.
We can open these text files using the commnad 'cat'. This way: "$ cat file.txt &" ...
or we can open the file using the command: "$ gramcode file.txt"

@frednora
Copy link
Member

very good, thank you!

@zBl4ckUser
Copy link
Contributor Author

Hi! Yes, I created the file using the command 'newfile aa.c' in gdeshell, after that I opened the file with the gramcode. I thought it was a bug because of those characters that appeared on the screen.

@zBl4ckUser
Copy link
Contributor Author

Thanks for answering :)

@frednora
Copy link
Member

Hi! Yes, I created the file using the command 'newfile aa.c' in gdeshell, after that I opened the file with the gramcode. I thought it was a bug because of those characters that appeared on the screen.

Ohh i'm sorry ... In this special way, it is actually a bug. A bug in the routines for opening files.
It is because there is a problem when we try to open a file named with extension with only one letter. ex: 'file.c'
... it is working better with three letter, like this: 'file.cpp'. :)

@frednora frednora changed the title gramcode: Trying to open a file gramcode: Can't open files with only one letter in the extension, ex: file.c Feb 22, 2021
@frednora frednora added the bug label Feb 22, 2021
@frednora
Copy link
Member

frednora commented Sep 7, 2022

This is still a work to do in the file system support. That is why im using only .cpp .ini and .txt. hehehe

@frednora
Copy link
Member

frednora commented Sep 7, 2022

gramado-root-1
See: im still not using .c extention ... we still can't use only one single letter in the extention. In the picture you can see a file called test1.c ... sometimes im using this file to work in this issue. :)

@frednora frednora changed the title gramcode: Can't open files with only one letter in the extension, ex: file.c fs: Can't open files with only one letter in the extension, ex: file.c Sep 7, 2022
@FrancisBFTC
Copy link

Hello Fred! Does this extension bug still exist in the file system? I´m thinking of contributing it...

@frednora
Copy link
Member

ext-test
At this moment the system is able to open files when the filename has an extension with only one letter. And also some different combinations of number of letters. And also support some special 'symbols', just like + - $ etc ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants