I used to Atom editor for coding Golang, PHP,...
When I am coding, sometimes it is automatic close. I install it on Window 10.
Maybe when I switch tab or move mouse but I don't know why so.
UPDATE:
Version: 1.18.0 (before, it is older version but It also so)
Atom : 1.18.0
Electron: 1.3.15
Chrome : 52.0.2743.82
Node : 6.5.0
Do you have any more information? Anything special you did when installing? Have you followed the suggestions in the Debugging document? Also, could you give the following information?
Which version of Atom are you using?
Can you reproduce the issue after completely exiting Atom and restarting using atom --safe?
Related
A recent update (of either MinTTY/MSYS2/bash or sbt) started breaking the output of sbt such that control characters are appearing instead of displaying rich text output in the terminal:
From the image you can see that rich text does still work as can be seen from my prompt line, but sbt started showing control characters like ←[0m[.
I'm on windows 11 and it was working perfectly fine last week, and my TERM terminal setting is set to xterm.
After some searching, I found these two posts:
https://github.com/gradle/gradle/issues/13279
https://youtrack.jetbrains.com/issue/IDEA-247532
both suggesting that I should try setting my TERM to cygwin but this did not solve the issue.
Question
How can I isolate where the issue is happening? I highly suspect it's an internal sbt update because the version it's indicating is 1.6.0 but the version I installed was 1.4.4 last year. I just tried uninstalling it and installing 1.6.2 via the installer but the issue still persists.
Does anyone have a solution to this issue? Is it a general thing that affects certain CLIs? From the links above it looks like it used to impact gradle as well.
Looks like it was MinTTY or MSYS2 because an update of those fixed the issue.
Working version of MSYS2:
$ cat /proc/version
MINGW64_NT-10.0-19044 version 3.3.5-341.x86_64 (#WIN-MG5BEJ9M9JD) (gcc version 11.3.0 (GCC) ) 2022-07-08 09:41 UTC
and MinTTY:
I am trying to run juno in atom because I hope it will be easier to debug code than it has been for me in vs studio but upon starting julia from juno I received the following error message in an orange box in the top right:
Julia could not be started.
Couldn’t resolve version.
We tried to launch Julia from: julia This path can be changed in the settings.
Where in settings can this be changed? It is not clear to me.
You need to open the Settings tab (Ctrl+,), then go to Packages > julia-client.
The path is the first setting:
In addition to Nils's suggestion, here's a lazy approach that has worked for me on MacOS BigSur and probably works on other systems.
Go to Juno Settings
Go to the Uber-Juno Settings (scroll down)
De-select: Disable (Don't run installation on Atom startup)
Exit Atom and re-start.
What this does is force Atom to run the installation script on startup. Atom then looks for Julia on your system and, in my case, found it easily. Problem solved.
Fresh install of ubuntu 18.04 then standard apt-install of awesome with awesome-extra.
Awesome --version returns
awesome v4.2 (Human after all)
• Compiled against Lua 5.3.3 (running with Lua 5.3)
• D-Bus support: ✔
• execinfo support: ✔
• xcb-randr version: 1.5
• LGI version: 0.9.2
gnome-control-center sound -v
** (gnome-control-center:14812): DEBUG: 14:27:19.737: Enabling debugging
** (gnome-control-center:14812): DEBUG: 14:27:19.850: No extra argument
** (gnome-control-center:14812): WARNING **: 14:27:19.850: Could not find settings panel "sound"
Basically there is no settings whatsoever.
Anyone can suggest what went wrong?
Everything else works just fine, I have sound, keyboard, multiple displays. I just lost control over settings, cannot mute sound, cannot dim a screen, cannot lock my laptop.
PS
Previous ubuntu (16.04) had unity-control-center and it was working just fine (but with older version of awesome I think)
gnome-control center can be run by tricking it into thinking it is in a gnome desktop
env XDG_CURRENT_DESKTOP=GNOME gnome-control-center
or by editing the .desktop files for each control app.
for example
/usr/share/applications/gnome-display-panel.desktop
find the line OnlyShowIn=GNOME;Unity; add awesomewm
I reached to Awesome irc channel to figure out what might be wrong. Explanation I was given (I am not quoting, I am answering as I understand the problem) is that nowadays gnome is more and more strict over it's architecture. So in the past you could replace window manager on gnome with another tool and retain whatever underlying solution was (mentioned control panel, sound widgets and etc). But nowadays gnome has approach all or nothing.
So real solution to my problem is, because sound and screen is working and I am only missing settings-control over them, is to install widgets and/or tools. For example pavucontrol was mentioned as good tool for a sound and bind key shortcuts to control brightness.
Previous iteration of Ubuntu worked, because exactly it was running unity, not gnome.
I don't like the 3.6 version at all. It has too many bugs and it's too slow compared with the previous versions, so I'd like to install to a previous version and wait till they fix the problems. I can't downgrade the installation, so no, not an option.
I know that in this web: https://wiki.appcelerator.org/display/guides2/Reverting+to+a+Previous+Version there is a list of old versions, but this are VERY old, I'd like to download at least the 3.4.2 version or newer (like 3.5), but I can't see any link from wich I can download it. Can anyone give me a link or way to get previous versions of aptana?
Oh yes, oh yes, finally I found them:
MAC OS
http://d1iwq2e2xrohf.cloudfront.net/tools/studio/standalone/3.4.2.201308081805/mac/Aptana_Studio_3_Setup_3.4.2.dmg
WINDOWS
http://d1iwq2e2xrohf.cloudfront.net/tools/studio/standalone/3.4.2.201308081805/win/Aptana_Studio_3_Setup_3.4.2.exe
Linux 32 bits
http://d1iwq2e2xrohf.cloudfront.net/tools/studio/standalone/3.4.2.201308081805/linux/Aptana_Studio_3_Setup_Linux_x86_3.4.2.zip
Linux 64 bits
http://d1iwq2e2xrohf.cloudfront.net/tools/studio/standalone/3.4.2.201308081805/linux/Aptana_Studio_3_Setup_Linux_x86_64_3.4.2.zip
Can't get the plugin, sorry.
You could find Aptana 3.4.2 as Eclipse plugin at the following URL: http://d1iwq2e2xrohf.cloudfront.net/tools/studio/plugin/update/studio3/3.4.2.201308081736/com.aptana.feature.studio-3.4.2.201308081736-7W7I57boG98RAi489ctbvKi7VXbq.zip
When you are installing it from the zip, make sure you un-tick "Group Items by Category"
I have just installed the latest versions of R (3.1.0) and Rstudio (v0.98.507) on a Windows 7 machine, 64 bit.
The R GUI works OK, but when I open the RStudio.exe only a blank window opens. I've tried re-installing R and RStudio.
Any suggestions?
By choosing the R version I wanted to use I was able to use Rstudio again.
To choose the R version you want to use with Rstudio do the following;
Click the CTRL key (don't let go)
Click on the Rstudio icon
Choose the version you want in the pop-up window.
For Ubuntu users where #neal's solution doesn't work.
$ rstudio --no-sandbox
related to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1944468
Download the 64bit version and reinstall it.
The same for Linux
FOR LINUX: this happens to me on cloud instances. A solution is forcing software rendering of RStudio. You need to start RStudio, get to the black screen, close Rstudio black screen, do my solution below in the terminal with Rstudio closed, then start Rstudio again.
In terminal:
sudo nano ~/.config/RStudio/desktop.ini
APPEND THE FOLLWING TO [General] section (leave whatever is there and add the line below):
[General]
desktop.renderingEngine=software
Again this is for Linux, but there may be a similar issue in Windows and you may be able to force software rendering.
Press down Ctrl key and then click on RStudio icon to launch. A dialog box asks you about the R version. Choose the one that actually exists (you might see an R version which does not exist; confusing RStudio)
For Windows10 64bit.
After following the hold Ctrl and clicking RStudio icon.
Change the Rendering Engine: to Software.
This fixed the problem on my machine.