the txt is not a text, it's a compress archive rather, that's not a bug
** Changed in: gedit (Ubuntu)
Importance: Undecided = Low
** Changed in: gedit (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is
Yes, it is .tar.gz archive with a .txt file, wich is NOT opening with gEdit,
but is opening normally wil another text redactors (Geany, Writer, etc.)
So the bug is not invalid
** Changed in: gedit (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are
I'm attaching this txt file without compression...
** Attachment added: wmsape-list.txt
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1067915/+attachment/3917617/+files/wmsape-list.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is
*** This bug is a duplicate of bug 575500 ***
https://bugs.launchpad.net/bugs/575500
sorry, I misunderstood the previous comment, that's a duplicate of bug
#575500 then
** This bug has been marked a duplicate of bug 575500
refuses to open files with incorrect encoding
--
You received
What you attached is not a .txt file, but rather a .tar.gz archive
containing a .txt file. After unpacking it Gedit opens it fine:
zcat wmsape-list.txt.tar.gz wmsape-list.txt.tar
tar xf wmsape-list.txt.tar
gedit wmsape-list.txt
--
You received this bug notification because you are a member of
It is still actual, any attention to this bug?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1067915
Title:
gedit can't open a txt file
Status in “gedit” package in Ubuntu:
It is fixed for me now
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1067915
Title:
gedit can't open a txt file
Status in “gedit” package in Ubuntu:
Confirmed
Bug description:
I
I’ve been facing a similar issue. For me the problem was that the
encoding of the file had changed since it was last opened with Gedit
(from WINDOWS-1252 to UTF-8). As I had manually set the encoding when
first opening the file, Gedit had saved this information and tried to
reuse it the next time
I am continuing to get this error on files that used to be able to be
opened by gEdit. Here's an error message that is logged relating to
this:
** (gedit:13182): WARNING **: Hit unhandled case 1 (Invalid byte
sequence in conversion input) in parse_error.
--
You received this bug notification
Bizarre workaround for this bug: cat the file from the command line and
then copy and paste it back into a new text file in gedit. I had to
copy-paste-save it in sections, because if I pasted the entire document
into gedit all at once, the invalid byte sequence error remained.
--
You received
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gedit (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1067915
Just upgraded to Quantal a week ago. Used gedit to edit a text file
this morning and it worked fine. Restarted my computer and then tried
to edit the same file again and got Unexpected error: Invalid byte
sequence in conversion input.
There shouldn't be any strange characters in the file.
--
12 matches
Mail list logo
