On Saturday 09 April 2016 08:09:22 Martin Schreiber wrote:
> On Friday 08 April 2016 19:16:56 Graeme Geldenhuys wrote:
> > Hi Martin,
> >
> > What is the designed behaviour of MSEide's code editor and EOL styles?
> >
> > Does it auto-convert it to whatever the MSEide target executable is? Or
> > do
On Saturday 09 April 2016 15:42:22 Graeme Geldenhuys wrote:
> On 2016-04-09 14:40, Graeme Geldenhuys wrote:
> > If it can detect the EOL style (say query the first line or two) and
> > simply use that, that would be perfect.
>
> Or make that a 3rd option. For example:
> * Unix
> * Windows
> *
On 2016-04-09 14:40, Graeme Geldenhuys wrote:
> If it can detect the EOL style (say query the first line or two) and
> simply use that, that would be perfect.
Or make that a 3rd option. For example:
* Unix
* Windows
* Leave it as is (whatever is detected in the first line or two)
Regards,
On 2016-04-09 07:09, Martin Schreiber wrote:
> it uses the lineending of the platform MSEide
> has been compiled for.
That explains it then.
> Maybe that should been made configurable. What do you
> think?
Yes, such a setting would be great. I presume it will be a Project ->
Editor setting, an
On Friday 08 April 2016 19:16:56 Graeme Geldenhuys wrote:
> Hi Martin,
>
> What is the designed behaviour of MSEide's code editor and EOL styles?
>
> Does it auto-convert it to whatever the MSEide target executable is? Or
> does it leave the line style whatever it is (example in a shared folder
> e
Hi Martin,
What is the designed behaviour of MSEide's code editor and EOL styles?
Does it auto-convert it to whatever the MSEide target executable is? Or
does it leave the line style whatever it is (example in a shared folder
environment between VM's).
What does it do with newly generated code i
6 matches
Mail list logo
