thanks , looks pretty good now :)
many thanks
2013/9/29, Martin Schreiber :
> On Saturday 28 September 2013 19:09:20 airpas wrote:
>> the line number color could be gray instead of black , and the margin
>> could be light gray , it gives nice looking editor space .
>>
> Please try git master
On Saturday 28 September 2013 19:09:20 airpas wrote:
> the line number color could be gray instead of black , and the margin
> could be light gray , it gives nice looking editor space .
>
Please try git master 429a98c83a1c0cf87cb5761a2c4f985687da5e7f.
Better?
Martin
--
thank you so much , looks nice .
just a note
the line number color could be gray instead of black , and the margin
could be light gray , it gives nice looking editor space .
thanks
2013/9/26, Martin Schreiber :
> On Monday 23 September 2013 12:23:48 airpas wrote:
>> and how to show line number
On Monday 23 September 2013 12:23:48 airpas wrote:
> and how to show line numbers left of the source editor?
>
git master da1a610314c8be1a968d6bdf5857c28317e7340d
has 'Project'-'Options'-'Editor'-'Line Numbers'.
Martin
-
On Tuesday 24 September 2013 23:45:40 Sieghard wrote:
> A separate line number display can only make it a bit easier to refer to
> lines nearby, but then, you can calculate the number easily, or use
> "relative addressing" by giving a line distance, like "two lines above".
>
> But then, it won't re
Hallo Graeme,
Du schriebst am Tue, 24 Sep 2013 09:40:47 +0100:
[line numbers]
> 1) Debugging with backtrace information, GDB gives you a file name and
> line position. Yes, jumping directly to that position is possible, but
> sometimes scrolling is also an option, eg: if I can see in the editor
>
On 23/09/13 20:32, Sieghard wrote:
> Not just that - how often do you really need them?
> (I.e. navigate _by_ line number?)
1) Debugging with backtrace information, GDB gives you a file name and
line position. Yes, jumping directly to that position is possible, but
sometimes scrolling is also an o
On Monday 23 September 2013 21:32:33 Sieghard wrote:
> Hallo Graeme,
>
> Du schriebst am Mon, 23 Sep 2013 11:31:48 +0100:
> > On 23/09/13 11:23, airpas wrote:
> > > how to show line numbers left of the source editor?
>
> ...
>
> > I know it's more "space efficient" to not display them - probably w
I can't readily imagine even one use for them.
Me too. It's better not to give units to grow so much to need code
folding within them.
--
October Webinars: Code for Performance
Free Intel webin
Hallo Graeme,
Du schriebst am Mon, 23 Sep 2013 11:31:48 +0100:
> On 23/09/13 11:23, airpas wrote:
> > how to show line numbers left of the source editor?
...
> I know it's more "space efficient" to not display them - probably what
Not just that - how often do you really need them?
(I.e. navigat
On Monday 23 September 2013 12:23:48 airpas wrote:
> hi Martin
>
> is MSEide suport code folding ?
No. I don't need it and I don't like it.
If you need grid row hiding or folding in your projects use
tcustomgrid.rowhidden[n] or rowfoldlevel[n]. There is also tfoldedit which
can be placed in a tw
it is so handy and common place these days.
=
And code navigation - per-unit list of vars [& their methods] clicking
on which brings us to its code definition. In large projects, it's
even more necessary than handy :)
On 23/09/13 11:23, airpas wrote:
> how to show line numbers left of the source editor?
You can't, and that bugs me too. :) I've been considering creating a
local modification on my system to add that.
I know it's more "space efficient" to not display them - probably what
Martin went for, but it
hi Martin
is MSEide suport code folding ?
and how to show line numbers left of the source editor?
thanks
--
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including Visual
14 matches
Mail list logo
