| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
I'm still unsure, but couldn't stand the virtual event trickery so tried a
different sin (adding undo_block_start/stop methods to the Text instance in
EditorWindow.py). Like it or not, it's efficient and works <wink>. Better
idea?
Give the attached a whirl. Even if you hate the implementation, I think
you'll like the results. Think I caught all the "block edit" cmds,
including Format Paragraph, plus subtler ones involving smart indents and
backspacing.
|
|
|
|
|
|
|
| |
[W]hile trying to dope out how redirection works, stumbled into two
possible glitches. In the first, it doesn't appear to make sense to try to
rename a command that's already been destroyed; in the second, the name
"previous" doesn't really bring to mind "ignore the previous value" <wink>.
|
| |
|
| |
|
|
|
|
| |
once for foo + module.so, once for foomodule + .so).
|
|
|
|
| |
Bump version number 1.0
|
|
|
|
| |
(thanks Fred!)
|
|
|
|
| |
on every invocation, instead of just the first.
|
|
|
|
| |
invocation, instead of just the first.
|
|
|
|
|
| |
PyncheWidget.__init__(): Add the extrapath argument which can be used
to pass in additional directories to search for Viewers.
|
|
|
|
| |
lookup protocol.
|
|
|
|
|
| |
set_colordb(): Call Viewers' colordb_changed() method if they have
them. Notifies them of changes to the color name database.
|
| |
|
|
|
|
|
| |
text widget attribute), the color the attribute currently has is set
in the main widget.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
to the 'load palette' entry. Just don't put the quit button on
there.
|
|
|
|
| |
(with some controversy surrounding AliceBlue :-)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
You can switch database by just loading the new one; the list window
and nearest colors adapt to the new database.
Some reorganizing of code. Also, the name of the database file is
stored in the ~/.pynche pickle. If it can't be loaded, fallbacks are
used.
|
|
|
|
| |
file URLs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ho ho ho -- that's trickier than it sounded! The colorizer is working with
"line.col" strings instead of Text marks, and the absolute coordinates of
the point of interest can change across the self.update call (voice of
baffled experience, when two quick backspaces no longer fooled it, but a
backspace followed by a quick ENTER did <wink>).
Anyway, the attached appears to do the trick. CPU usage goes way up when
typing quickly into a long triple-quoted string, but the latency is fine for
me (a relatively fast typist on a relatively slow machine). Most of the
changes here are left over from reducing the # of vrbl names to help me
reason about the logic better; I hope the code is a *little* easier to
|
| |
|
| |
|
|
|
|
| |
menu, command line and color preferences.
|
| |
|
| |
|
|
|
|
| |
from ScriptBinding.py where they are no longer needed.
|
|
|
|
|
|
|
|
|
|
|
| |
there are two new commands:
Import module (F5) imports or reloads the module and also adds its
name to the __main__ namespace. This gets executed in the PyShell
window under control of its debug settings.
Run script (Control-F5) is similar but executes the contents of the
file directly in the __main__ namespace.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
idle.py -e file ... -- to edit files
idle.py script arg ... -- to run a script
idle.py -c cmd arg ... -- to run a command
Other options, see also the usage message (also new!) for more details:
-d -- enable debugger
-s -- run $IDLESTARTUP or $PYTHONSTARTUP
-t title -- set Python Shell window's title
sys.argv is set accordingly, unless -e is used.
sys.path is absolutized, and all relevant paths are inserted into it.
Other changes:
- the environment in which commands are executed is now the __main__ module
- explicitly save sys.stdout etc., don't restore from sys.__stdout__
- new interpreter methods execsource(), execfile(), stuffsource()
- a few small nits
|
|
|
|
| |
Run/Import, __main__.
|
|
|
|
|
|
|
|
| |
dramatically (up to 15 times he claims). Works by reading more than
one line at a time, up to 100-line chunks (starting with one line and
then doubling up to the limit). On a typical machine (e.g. Tim's
P5-166) this doesn't reduce interactive responsiveness in a noticeable
way.
|
| |
|
|
|
|
|
| |
foo_bar_event(). Therefore, fix the references to zoom_height() in
the example.
|
| |
|
| |
|
|
|
|
|
|
|
| |
unsuccessful search wraps around and re-searches that part of the file
between the start of the search and the end of the file - only really
an issue for very large files, but... (also removes a redundant
m.span() call).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Makes the tab key intelligently insert spaces when appropriate (see Help
list banter twixt David Ascher and me; idea stolen from every other editor
on earth <wink>).
o newline_and_indent_event trims trailing whitespace on the old line (pymode
and Codewright).
o newline_and_indent_event no longer fooled by trailing whitespace or
comment after ":" (pymode, PTUI).
o newline_and_indent_event now reduces the new line's indentation after
return, break, continue, raise and pass stmts (pymode).
The last two are easy to fool in the presence of strings & continuations,
but pymode requires Emacs's high-powered C parsing functions to avoid that
in finite time.
|
| |
|
|
|
|
|
| |
Don't rewrite the file in place.
(Reported by Andy Dustman.)
|
| |
|