Hello fredvs,
you wrote on Wed, 18 Mar 2020 03:44:08 -0700 (MST):
> > But most probabely they were preexisting, I presume?
>
> Yes, they were produced maybe by a build process but that build process is
> not part of mse (imho).
>
> > (or compare them with tha originals, or just
> > dump the
> But most probabely they were preexisting, I presume?
Yes, they were produced maybe by a build process but that build process is
not part of mse (imho).
> (or compare them with tha originals, or just
> dump them and _use_ the originals),
Yes, I did tests before to choose what to commit.
And,
Hello fredvs,
you wrote on Mon, 16 Mar 2020 14:45:09 -0700 (MST):
> > Wouldn't it be simpler to just rebuild all binaries
>
> Not sure to understand.
> There is no applications-binaries or libraries-binary in mseide-msegui
> source.
> All the binaries are about images files, like bmp, png, jpe
> Wouldn't it be simpler to just rebuild all binaries
Not sure to understand.
There is no applications-binaries or libraries-binary in mseide-msegui
source.
All the binaries are about images files, like bmp, png, jpeg, ...
Rebuild the images?
--
Sent from: http://mseide-msegui-talk.13964.n8.na
Hello fredvs,
you wrote on Sun, 15 Mar 2020 16:28:19 -0700 (MST):
> > If you are COMPLETELY SURE that NOT A SINGLE FILE of them all is a
> > binary
>
> No, I am not completely sure.
>
> It is the reason why, before to apply the patch, I did copy the
> directories containing binaries and git
> If you are COMPLETELY SURE that NOT A SINGLE FILE of them all is a binary
No, I am not completely sure.
It is the reason why, before to apply the patch, I did copy the directories
containing binaries and git files in safe place.
(Imho, only images and git files are concerned).
Then apply the
Hello fredvs,
you wrote on Sun, 15 Mar 2020 13:45:54 -0700 (MST):
> > OK, done in 2 last commits.
> > I hope I did not a disaster.
Hope you always can...
> I did use that command (after done a copy of .git and images files):
>
> $ find . -type f -name '*.*' -exec sed --in-place 's/[[:space:
> OK, done in 2 last commits.
> I hope I did not a disaster.
I did use that command (after done a copy of .git and images files):
$ find . -type f -name '*.*' -exec sed --in-place 's/[[:space:]]\+$//' {} \+
After that command, I did paste the original copied .git and images files.
Fre;D
OK, done in 2 last commits.
I hope I did not a disaster.
Fre;D
--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ms
> You are green to go! :-)
Aargh, it does not work this time.
OK. (but asap).
Fre;D
--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourcef
On 13/03/2020 12:59 pm, fredvs wrote:
> Anyway, I will use the magic words (that works very well with Graeme):
hahahaha I'm on to you now. ;-)
> "Graeme, if you want, I will do it asap."
You are green to go! :-)
Regards,
Graeme
___
mseid
On 12/03/2020 5:59 pm, fredvs wrote:
> Mse has **many** units, doing this via a editor will takes ages...
Thare are plent of command line tools that can do it too. Some
programmer text editors are process all files in directories recursively
too. Google is your friend. ;-)
Regards,
Graeme
--
Hello Sieghard.
> Do you use Windows (a manualizing tool) or Linux (an automating tool)?
I use Linux.
> "sed -i 's/[[:blank:]]*$//' "
Thanks for the tip!
Maybe Graeme is already busy with it.
Anyway, I will use the magic words (that works very well with Graeme):
"Graeme, if you want, I will
Hello fredvs,
you wrote on Thu, 12 Mar 2020 10:59:15 -0700 (MST):
> > I suggest,if you want, apply it to ALL the source code in the repo and
> > make one
> > commit that says trimming the whitespace. Done and dusted! ;-)
Should be done urgently. I also hate trailing invisible stuff.
> Ho, ye
> I suggest,if you want, apply it to ALL the source code in the repo and make
one
> commit that says trimming the whitespace. Done and dusted! ;-)
Ho, yes, it would be wonderful.
But...
Mse has **many** units, doing this via a editor will takes ages...
Fre;D
--
Sent from: http://mseide-mse
On 12/03/2020 5:39 pm, fredvs wrote:
> Yes, my fault, now I see that it was absolutely not a good idea.
Martin once told me too, to revert my contributions because I enabled
"trim trailing whitespace". :-)
The MSEide+MSEgui code is full of such trailing whitespace. I suggest,
if you want, apply
Hello Graeme.
> change a editor setting (eg: trim trailing whitespace)?
Yes, my fault, now I see that it was absolutely not a good idea.
Fre;D
--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/
___
mseide-msegui-talk mailing list
mseide
On 12/03/2020 10:26 am, fredvs wrote:
> Maybe Graeme could refresh my mind?
Use the 'git diff' with the following parameters
-b (ignores changes in amount of whitespace)
-w (ignores all whitespace)
But I would be thinging to myself, why did Git complain about those in
the first plac
Hello.
When I check my last commits, doing a "diff", shows also all the spaces end
empty lines removed.
That makes the read of the change much more complicated, I would prefer that
only the change in code was show.
I know that there is a option in Git to ignore the change done for space and
empt
19 matches
Mail list logo
