4:48 p.m.
Some suggestions,
it would be nice if the script editor would provide in its header the name of the gretl
instance it belongs to. I sometimes have multiple instances open... The same accounts for
other gretl windows, I guess.
Also, because I often work on scripts within gretls editor (auto completion, highlighting,
help, etc.) but also and at the same time with another editor (PSPad) in order to use
macros and better search&exchange abilities, it would be nice if the script editor
would check for external changes and report this (something like "external change
detected, do you want to update the script to the external version?"). An optional
"auto update" option would also be nice to have.
Best
Frederik
10:26 p.m.
On Wed, 10 Jan 2018, Schaff, Frederik wrote:
it would be nice if the script editor would provide in its header
the name of the gretl instance it belongs to. I sometimes have
multiple instances open... The same accounts for other gretl
windows, I guess.
Feasible, I guess, but it would involve changing hundreds of
translatable strings -- probably not very popular with the
translators of gretl. I tend to think of running multiple gretl
instances as a rather rare activity, with at most two instances
active and one of them probably just displaying a dataset. Running
multiple instances each with multiple windows open is not
recommended procedure.
Also, because I often work on scripts within gretls editor (auto
completion, highlighting, help, etc.) but also and at the same
time with another editor (PSPad) in order to use macros and better
search&exchange abilities, it would be nice if the script editor
would check for external changes and report this (something like
"external change detected, do you want to update the script to the
external version?"). An optional "auto update" option would also
be nice to have.
Hmm, I think it's best to make a choice of script editor and stick
with it. A high-functioning "third party" editor of choice shouldn't
have a problem with running a gretl script (e.g. via gretlcli) and
displaying the output. IMO editing a given text in two editors
simultaneously is asking for trouble!
But if you can tell us what in particular you reckon is missing from
gretl's built-in script editor we could consider enhancing it.
Allin
8:26 a.m.
But if you can tell us what in particular you reckon is missing from gretl's built-
in script editor we could consider enhancing it.
Allin
Ok, here are the things I most frequently miss in gretls editor:
a) Search and "List" option with links (A list where all lines with line-numbers
are given, where the item occurred, and an option to "click" on each single one
to get there). This helps also to get, e.g., a fast index of functions in the file.
b) Searching across files (as before, but searching within (sub)folders and all files)
c) Search & replace in "marked" text only
d) And then, a thing I mentioned in the past, the script editor sometimes has problems
with copy & paste. The most easy thing to reproduce it is to use clipboarder
(http://nes.bplaced.net/de.html), which allows to copy a lot of things into the clipboard
in a row and then past it in a row back (using short keys).
e) Another thing for debugging that would be nice: If the debug error would indicate the
line within the script, not within the code OR if one could add a second vertical bar to
the editor, with line-numbers starting at the position.
f) And (not related to the editor) if the error messages in "outfile" mode would
still be directed at the log, or if there was such an option, debugging would become a bit
easier.
Best
Frederik
10:56 a.m.
Am 11.01.2018 um 09:26 schrieb Schaff, Frederik:
Ok, here are the things I most frequently miss in gretls editor:
a) Search and "List" option with links (A list where all lines with
line-numbers are given, where the item occurred, and an option to
"click" on each single one to get there). This helps also to get,
e.g., a fast index of functions in the file.
I agree that the search facility in the built-in editor is somewhat
rudimentary for today's standards. I've seen this list feature you're
describing in other contexts, and yes it's useful. Don't know if the GTK
apparatus has something like that off the shelf.
b) Searching across
files (as before, but searching within (sub)folders and all files)
Here I think it would be enough to search in all files that are opened
in the editor. For searching in the machine's filesystem I'd rather
recommend to use other specialized tools. IMHO gretl shouldn't aim to do
everything itself.
d) And then, a thing I mentioned in the past, the script editor
sometimes has problems with copy & paste. The most easy thing to
reproduce it is to use clipboarder (http://nes.bplaced.net/de.html),
which allows to copy a lot of things into the clipboard in a row and
then past it in a row back (using short keys).
Can you give a step-by-step to guide to reproduce this? Then I could try
if it happens to me, too.
e) Another thing for debugging that would be nice: If the debug
error
would indicate the line within the script,
It also seems to me that the line numbers given in the errors are
net-of-comment-lines or something like that? It hasn't bothered me too
much but I agree there might be room for improvement.
cheers,
sven
11:56 a.m.
Am 10.01.2018 um 23:26 schrieb Allin Cottrell:
On Wed, 10 Jan 2018, Schaff, Frederik wrote:
Hmm, I think it's best to make a choice of script editor and
stick with
it. A high-functioning "third party" editor of choice shouldn't have a
problem with running a gretl script (e.g. via gretlcli) and displaying
the output. IMO editing a given text in two editors simultaneously is
asking for trouble!
Well, the nice thing about gretl is that you can run a script and then
work with the results (series etc.) in the GUI. If you use a 3rd-party
editor + gretlcli, that's not possible. So if something serious is
missing from the built-in editor, there is no easy substitute.
But if you can tell us what in particular you reckon is missing from
gretl's built-in script editor we could consider enhancing it.
See the other branch of this thread...
thanks,
sven
2300
days inactive
2301
days old
4 comments
3 participants
participants (3)
-
Allin Cottrell -
Schaff, Frederik -
Sven Schreiber