1. Trace suggestion
Hi Rob and group,
I know the "nice to have's" list is closed for v2.5,
but how about this for v2.6:
When you are in the trace(1) interactive screen, the source line numbers
are displayed. How about displaying the full path/filename of the file
being traced too? In the yellow line that prompts for a variable.
Ideally, Id like to have tracing on in my source, and exclude tracing
all (trusted) includes but be able to easily override this as required.
eg:
a) a new trace variable "with trace_include on/off" and
"with trace_include_nesting_level n"
b) or, 'with trace_exclude="c:\euphoria\include' and I put my
include source in another directory
My reason for wanting this, is that its a pain to add the trace(1)
and trace(0) in included files, Id like to keep them untouched ,
so that the contributor knows they are vanilla and I don't pick
up traces while working on a different program.
Its easier to edit ONE file only.
Further, this will disable leftover trace on in included files.
Regards
Alan
2. Re: Trace suggestion
Alan Oxley wrote:
> I know the "nice to have's" list is closed for v2.5,
> but how about this for v2.6:
It's not exactly "closed", but I don't want to delay
the release too much longer.
> When you are in the trace(1) interactive screen, the source line numbers
> are displayed. How about displaying the full path/filename of the file
> being traced too? In the yellow line that prompts for a variable.
The filename is displayed in the top left corner of the screen.
It doesn't have the full path. I thought that would take up too
much space.
> Ideally, Id like to have tracing on in my source, and exclude tracing
> all (trusted) includes but be able to easily override this as required.
>
> eg:
> a) a new trace variable "with trace_include on/off" and
> "with trace_include_nesting_level n"
> b) or, 'with trace_exclude="c:\euphoria\include' and I put my
> include source in another directory
>
> My reason for wanting this, is that its a pain to add the trace(1)
> and trace(0) in included files, Id like to keep them untouched ,
> so that the contributor knows they are vanilla and I don't pick
> up traces while working on a different program.
>
> Its easier to edit ONE file only.
> Further, this will disable leftover trace on in included files.
OK, thanks. I'll add this to my list of ideas for improving
the trace facility.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: Trace suggestion
Hmm, full path.
How about display the full path if it fits within 80 column screen.
such as C:\euphoria\include\graphics.e
and in the cases where it doesn't... be fancy like many windows
programs do. C:\...\users\unkmar\desktop\test.e
OR
We allow method for requesting it.
Press F12 for full path to the include file and its name.
Um. I don't really suggest F12.. just giving an example.
unkmar
----- Original Message -----
From: "Robert Craig" <guest at RapidEuphoria.com>
To: <EUforum at topica.com>
Sent: Monday, May 31, 2004 12:32 PM
Subject: Re: Trace suggestion
>
>
> posted by: Robert Craig <rds at RapidEuphoria.com>
>
> Alan Oxley wrote:
> > I know the "nice to have's" list is closed for v2.5,
> > but how about this for v2.6:
>
> It's not exactly "closed", but I don't want to delay
> the release too much longer.
>
> > When you are in the trace(1) interactive screen, the source line numbers
> > are displayed. How about displaying the full path/filename of the file
> > being traced too? In the yellow line that prompts for a variable.
>
> The filename is displayed in the top left corner of the screen.
> It doesn't have the full path. I thought that would take up too
> much space.
>
> > Ideally, Id like to have tracing on in my source, and exclude tracing
> > all (trusted) includes but be able to easily override this as required.
> >
> > eg:
> > a) a new trace variable "with trace_include on/off" and
> > "with trace_include_nesting_level n"
> > b) or, 'with trace_exclude="c:\euphoria\include' and I put my
> > include source in another directory
> >
> > My reason for wanting this, is that its a pain to add the trace(1)
> > and trace(0) in included files, Id like to keep them untouched ,
> > so that the contributor knows they are vanilla and I don't pick
> > up traces while working on a different program.
> >
> > Its easier to edit ONE file only.
> > Further, this will disable leftover trace on in included files.
>
> OK, thanks. I'll add this to my list of ideas for improving
> the trace facility.
>
> Regards,
> Rob Craig
> Rapid Deployment Software
> http://www.RapidEuphoria.com
>
>
>
>
4. Re: Trace suggestion
On Mon, 31 May 2004 09:32:48 -0700, Robert Craig
<guest at RapidEuphoria.com> wrote:
>Alan Oxley wrote:
>> How about displaying the full path/filename
>
>The filename is displayed in the top left corner of the screen.
>It doesn't have the full path. I thought that would take up too
>much space.
If you are pushed for screen estate, when you key ?, the remainder of
the top line (F1=main F2=trace Enter down-arrow ? q Q !) no
longer applies, so while a variable name is being entered,
you could use the whole of the top line.
Actually, you could move that part of the top line over to the far
right, which with an 8.3 filename allows the last 15 or so characters
of the path to be displayed, eg "...ria/include/database.exw"
Just some ideas,
Pete
