vermaneerajin / editra Goto Github PK

What steps will reproduce the problem?
1. Open a document with highlighting turned on
2. turn highlighting off
3. generate a document (i.e Html) from the generators menu

There should be an unstyled webpage generated but the parser still finds
the style data being held in the text controls stylemgr so it applies the
styles.

What steps will reproduce the problem?
1. Open the command bar in search mode (ctrl+F)
2.
3.

What is the expected output? What do you see instead?
The checkboxes for "Match Case" and "Whole Word" are not properly centered
in the bar. They are very close to encroaching on the top border.

Please use labels and text to provide additional information.

What is the expected output? What do you see instead?
The extended file type autodetection fails to work on lines like the following.

#!C:\PythonXX\python.exe

What steps will reproduce the problem?
1. Try generating a LaTeX file from a file with Unicode characters in it
2.
3.

What is the expected output? What do you see instead?
The document should generate with out error. There is instead 'ascii out of
range' errors that arise during the parse that prevent it from finishing.

Please use labels and text to provide additional information.

What steps will reproduce the problem?
In Mac OS X:
1. Activate Format menu
2. Clic on Font

The pannel with the fonts etc. appears ant disappears at once so that it's 
impossible to work with 
them.

What steps will reproduce the problem?
1. Open the command bar in any mode
2.
3.

What is the expected output? What do you see instead?
The command bar close button does not visibly display the 'X'. This seems
to stem from the amount of padding that is drawn in side the button around
the bitmap. The button is only 14x14 px and the padding seems to consume
roughly 12x12px of that space. If the button is made to be a bigger size
the 'X' is visible but then the button is too large and doesn't look very
well in the bar as well as causing some alignment issues.

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. open a php file
2. hit ctrl+1 or ctrl+2

The selected lines are not commented or uncommented. This was a miss in the
last release, it was put off due to having to handle special cases (i.e are
the selected lines inside of a php region or are they in an pure html
section of code. This needs to be detected in order to choose the correct
commenting pattern.

What steps will reproduce the problem?
1. Open the goto line control
2. type some non digit characters
3.

What is the expected output? What do you see instead?
Any non numerical characters typed while the cursor is in the GotoLine
control should not be entered. They should be caught by the Validator that
only allows for integer input. Initial testing has shown that the validator
code does not get called on these two platforms.

This can be attributed to a current limitation in the SearchCtrl
implementation on these platforms. The GotoLine ctrl is a custom subclass
of wxSearchCtrl, this was done in order to get a nice rounded control on OS
X. The control however does not seem to emit the proper events for the
Validator to get called. I am not sure why though as the SearchCtrl on
these platforms is a generic control derived from TextCtrl which properly
emits all the text/key related events.

One fix could be to use a basic text control on these platforms instead of
the search control, but this would require adding a full set of os specific
code which I dont like doing if its not necessary. So for the meantime I
fixed this by double checking the data that is retrieved from the control
before using it.

Hopefully this issue will be addressed in a future bug fix release of
wxPython. Should check if a bug has been submitted over there about this or
not.

What steps will reproduce the problem?
1. Open Style Editor, click on New
2. Click on New again
3.

What is the expected output? What do you see instead?
The preview window turns reddish purple. The debugging msgs shows that the
style manager could not find the style sheet. 

The name of the file is being shown is the title version where it should be
in all lower case. Very quick to fix. However the fact that the preview
window gets screwed up from this failure shows some deeper problems in the
fallback code of the stylemgr that need further research.

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Open the preference dialog
2. Change the icons or icon size on the Misc page
3. Click Ok or Apply

What is the expected output? What do you see instead?
The Icons and/or their size should change, but the status of which ones are
enabled and disabled should not. Currently all tools are enabled after this
action.

Please use labels and text to provide additional information.

When opening a file the editor should check what type of line ending is
being used and warn if there is mixed endings and possibly offer to convert
them. If the endings are not mixed but of a different type than what the
editor currently has set the editor should warn and then set the line
endings to match if the user doesnt wish to convert.

What steps will reproduce the problem?
1. Open a document that has highlighting support
2. Go to Settings=>Lexers, and switch to plain text
3.

What is the expected output? What do you see instead?
The document should be cleared to default_style but the areas that were
previously highlighted are completely unstyled using the default scintilla
settings which does not match the rest of the document properly.

Please use labels and text to provide additional information.

Instead of popping dialogs for minor/common error conditions in opperation
it may be nicer/less annoying to simply highlight the status bar and
display the message there.

What steps will reproduce the problem?
1. run "python.exe setup.py install"
2.
3.

What is the expected output? What do you see instead?
Reported on editra forum.
There are some path problems and issues with files being copied properly to
the correct paths. Requires investigation.

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. open a file that has spaces in the path
2.
3.

What is the expected output? What do you see instead?
file should open but doesnt

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Open a fairly large file ~2000+ lines of text
2. Tools->Generator->LaTeX
3.

What is the expected output? What do you see instead?
The LaTeX code that Editra generates causes memory overflows in the latex
program when generating a dvi, causing the compile to fail.

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. install editra as a python package
2. try opening or starting a new file from commandline
3.

What is the expected output? What do you see instead?
The file should be opened in the editor, but only the default untitled page
is opened instead.

Please use labels and text to provide additional information.

Allow folders to be dropped on the editor and then prompt to open all the
files in the folder that can be opened in the editor. This could act as a
very simple project management for small projects or modules of a bigger
project.

What steps will reproduce the problem?
1. Open a file from the command line (Editra yourfile.txt)
2.
3.

What is the expected output? What do you see instead?
There should be an image displayed on the tab but there isnt one.

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Open the command bar in search mode
2. enter some text in the search control
3.

What is the expected output? What do you see instead?
The cancel button that appears in the search control when text is added, is
too large to properly fit inside the text box. This seems to be an issue
with the wxSearchCtrl implementation on GTK. It may be correctable by
adding some additional handling or providing a custom drawn button,
requires more investigation.

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. move the cursor to the first line
2. try to insert a line before current line (Ctrl+Shift+L)
3.

What is the expected output? What do you see instead?
A new line should be added to the beginning of the file, but instead it is
added to the next line.

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Open a text document
2. click to move the cursor to new location
3.

What is the expected output? What do you see instead?
The status bar should show the new line/column info but it doesnt update
from the previous one.

Please use labels and text to provide additional information.

It would be nice to have Editra distributable as an egg. Some path and
launch script items need to be examined to make this possible.

What steps will reproduce the problem?
1. Turn on DEBUG mode
2. open an html file
3.

What is the expected output? What do you see instead?
The debugging output shows a warning about an undefined lexer attribute
being set. STC_H_ASPAT, this is likely a typo in the html module.

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. open a document
2. Click on generate HTML
3.

What is the expected output? What do you see instead?
The html should be a representation of all characters in the document. The
last character of the source file is not carried over to the new html document.

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. open a file that doesn't have a file extension but does have a shebang line
2.
3.

What is the expected output? What do you see instead?
The tab image should show the mime type image for the type of file it is,
but instead shows a generic text file image.

Please use labels and text to provide additional information.

The editor should bail out or at least warn that it was unable to properly
encode all characters when opening a file. This sometimes happens with
unicode files and other files that have characters outside of the ascii range.

Without this warning the editor will open a page with the file but not all
text will be displayed or be able to be saved afterwards, leading to data loss.

1. Open a file with some text in it
2. open the command bar in search mode
3. start typing

What is the expected output? What do you see instead?
The live searching feature does not work, the search is only performed
after hitting enter.

This defect appears to be in the implementation of the SearchCtr on the MSW
platform. As this issue is not replicated on my OSX or Linux test systems.
It stems from the SearchCtrl not emitting EVT_CHAR or any other KEY events
when it is being typed in.

What steps will reproduce the problem?
1. open a file with some long lines in it
2. generate latex
3. compile the latex

What is the expected output? What do you see instead?
The resulting latex document often has lines that overflow the hbox do to
the word wrap not working/being implemented.

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Edit a document while syntax highlighting is turned on
2.
3.

Often times on OS X the performance of the text control is very slow. It is
especially noticeable when a lexer is being used. Often times when just
spacing over with the space bar or deleting text by holding the backspace
button the CPU usage spikes rather high and often the text adding/removal
gets very laggy. This is not visible on the GTK/MSW versions, leading my
current thinking to believe this is an issue in the OS X implementation of
Scintilla but to be sure there needs to be further investigation.


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Open a menu
2.
3.

What is the expected output? What do you see instead?
The accelerator labels (i.e Ctrl+C, ect..) should be all properly aligned
in the menu when displayed but many of them are not properly aligned with
each other.

Please use labels and text to provide additional information.

The editor should check if another program has modified the file that is on
disk while it is being edited in a buffer.

What steps will reproduce the problem?
1. Open a new file from the commandline
2. Save the file 
3.

What is the expected output? What do you see instead?
The new file should be saved to the working directory from which it was
opened with Editra from. But the path to the file is not properly set when
the file is opened so the directory that it is saved to defaults to the
root of the current drive.

Please use labels and text to provide additional information.

The tabs should display some sort of indication to show which files have
their dirty bit set so that it can be seen at a quick glance which files
have been saved since their last modification and which have not.