Something like this, yes. And the visualized codes in the editor should be
the *default* view -- there are little to no cases where embedded
non-printable control codes would be intentional.
I can't even think of a case where you would want to press a key combination
to make them disappear...
>
> It was a CTRL-X
The context was pair-programming (we were using Honoré's Mac). I'm not much
of a Mac user anymore, and so on Windows I do CTRL-X to cut (it's a
reflex). But on a Mac one must use the Command key, right? I think this is
how it happened, but I'm not 100% sure.
On Mon, 13 Apr
Honoré and I had a debugging session during my sabbatical that was 2+ hours
because of a frustrating hidden character that got inserted in a string
that was executed in a Shell command. It was not possible to see it in the
Pharo editor.
It was a CTRL-X at some point, here's the commit where I
Shift + space = insecable space
It would be cool to be able to toggle a mode as in text editor where
hidden characters are represented by a symbol.
https://www.avrfreaks.net/sites/default/files/notepadpp.PNG
On Mon, Apr 13, 2020 at 8:44 PM Stéphane Ducasse
wrote:
>
> Hi
>
> I have the
Yes... We need to show something. At least in the code editor, when it is
clear we don't want them.
On Mon, Apr 13, 2020, 20:44 Stéphane Ducasse
wrote:
> Hi
>
> I have the impression that we can introduce hidden characters
> while typing code and this is a problem to me because we do not see
Hi
I have the impression that we can introduce hidden characters
while typing code and this is a problem to me because we do not see them :)
I got for example selhiddenf and it can lead to strange situations.
I will try to chase the key combinations that produce them and see how we
can control
There is a new Pharo build available!
The status of the build #233 was: FAILURE.
The Pull Request #6131 was integrated: "Introduce UnhandledException hierarchy"
Pull request url: https://github.com/pharo-project/pharo/pull/6131
Issue Url:
There is a new Pharo build available!
The status of the build #232 was: FAILURE.
Could not extract further issue information from commit message: Update
cleanup-report.md
Build Url:
There is a new Pharo build available!
The status of the build #231 was: SUCCESS.
Could not extract further issue information from commit message: Update
enhancement-request.md
adding expected costs
Build Url:
