development:ides_and_editors

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
development:ides_and_editors [2019/10/11 20:21]
meesters
development:ides_and_editors [2020/01/28 08:35] (current)
meesters [gedit]
Line 6: Line 6:
 On our clusters we support a number of editors. If you think your favorite one is missing, [[https://​hpc.uni-mainz.de/​high-performance-computing/​service-angebot/​softwareinstallation/​|please let us know]]. On our clusters we support a number of editors. If you think your favorite one is missing, [[https://​hpc.uni-mainz.de/​high-performance-computing/​service-angebot/​softwareinstallation/​|please let us know]].
  
-The following list is not exhaustive nor complete. ​Particularly, ''​vi''​ and ''​emacs'' ​are not describedThere is plenty ​of documentation ​on the web -- including flame wars.+The following list is not exhaustive nor complete. 
 + 
 + 
 + 
 +==== atom ==== 
 + 
 +[[https://​atom.io/​|''​atom''​]] is a widely used IDEfavored by many developers, which supports all the widespread programming languages and provides a plug-in scheme for most purposes. 
 + 
 +''​atom'' ​can be installed on various platforms. Please refer to the [[https://​flight-manual.atom.io/​getting-started/​sections/​installing-atom/​|installation guide]] (see the top tap for platforms other than Linux).  
 + 
 +=== Running Locally ​and Editing Remote Files === 
 + 
 +If you would like to develop on our HPC-Systems,​ you can edit the source code files stored there. We recommend using the ''​ftp-remote-edit'' ​packageSelect: ''​Edit''​ -> ''​Preferences''​ -> ''​Install''​ to select this package. 
 + 
 +After installing ''​ftp-remote-edit''​ you can select it in the ''​Packages''​ drop-down menue and select ''​Toggle''​. You will be asked for a password, which is actually a passphrase you may choose at will.  
 + 
 +<WRAP center round info 90%> 
 +You will need to enter this password //only once per session//, much like for ordinary [[:​access|ssh-connections]]. 
 +</​WRAP>​ 
 + 
 + 
 + 
 +== Working within the University Network == 
 + 
 +After the installation ​of ''​ftp-remote-edit''​ has been successfully completed, the following settings have to be made in order to work within the University Network. 
 +Select: ''​Packages''​ -> ''​Ftp-remote-edit''​ -> ''​Toggle''​ and enter your password. On the left side of the editor the remote pane has now opened. Right click on the pane and select ''​Edit Servers''​. Enter the settings for the desired cluster according the following template: 
 + 
 +^ MOGON I ^ MOGON II ^  
 +| {{ :​development:​atom_ftp_remote_edit_mi.png?​400 | example setting for Mogon I }}  | {{ :​development:​atom_ftp_remote_edit_mii.png?​400 | example setting for Mogon II}}  | 
 + 
 + 
 +== Working Remotely outside the University Network == 
 + 
 +Thereafter, selecting ''​Toggle''​ will give you the remote pane with a ''​Edit Servers''​ button. Select it and enter settings according to this template: 
 + 
 +{{:​development:​atom.png?​400 | example setting for the Mogon I fileserver}} 
 + 
 +Please note: 
 +  * Select the hostname for direct connect to the file server. This can be either ''​mogonfs.zdv.uni-mainz.de''​ for Mogon I or ''​mogon2ftp.zdv.uni-mainz.de''​. If you develop in your home directory, this choice does not matter. See the [[filesystems:​transfer|filesystem page]] for further details. 
 +  * Choose the plain FTP protocol, but require an encrypted handshake with ''​Require explicit FTP over TLS''​. 
 +  * As the logon type should be ''​Username / Password'',​ supply them in the according fields. 
 +  * Finally supply a full qualified path, e.g. ''/​gpfs/​fs1/​home/<​username>/​...''​ or ''/​lustre/​miifs01/​project/<​projectname>''​. See the [[filesystems:​transfer|filesystem page]] for further options. 
 + 
  
 ==== gedit ==== ==== gedit ====
Line 14: Line 57:
 === Turning off Gtk Warnings === === Turning off Gtk Warnings ===
  
-gedit issues a number of (annoying and meaningless) Gtk warnings. They can be turned off by placing this snippet in ones ''​.bashrc''​.+gedit issues a number of (annoying and meaningless) Gtk warnings. They can be turned off by placing this snippet in your ''​.bashrc''​.
  
 <code bash> <code bash>
Line 42: Line 85:
 </​code>​ </​code>​
  
 +==== emacs ====
  
-===== IDEs =====+''​emacs''​ is provided on every login node.
  
-<WRAP center round todo 90%> 
-This part of the page is work in progress - this warning will be removed, when everything is in place. 
-</​WRAP>​ 
  
 +
 +==== nano ====
 +
 +''​nano''​ is provided on every login node.
 +
 +
 +==== vi / vim ====
 +
 +''​vi''​ (as ''​vim''​) is provided on every login node. 
 +
 +===== IDEs =====
 +
 +==== Geany ====
 + 
 +[[https://​www.geany.org/​|''​geany''​]] is provided a system package. You can simply use it on any login node.
  • development/ides_and_editors.1570818092.txt.gz
  • Last modified: 2019/10/11 20:21
  • by meesters