The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,949 other followers

Archive for the ‘atom editor’ Category

To Favor Microsoft VS Code, Microsoft’s GitHub is Killing GitHub’s Atom Editor – time to prepare switching to another open source editor with a rich ecosystem in less than half a year

Posted by jpluimers on 2022/06/21

If you are still on Atom, try to see if other cross platform open source editors suit your needs.

Myself, I have moved to Visual Studio Code quite some time ago as, though based on Electron – the core of Atom, it is way faster and much better supported than Atom.

The official announcement is at [Wayback/Archive] Sunsetting Atom | The GitHub Blog.

Various sites reported it in different phrasings:

Read the rest of this entry »

Posted in .NET, atom editor, Development, Missed Schedule, Power User, SocialMedia, Software Development, Text Editors, vscode Visual Studio Code, WordPress | Leave a Comment »

A choco install list

Posted by jpluimers on 2021/02/03

Sometimes I forget the choco install mnemonics for various tools, so here is a small list below.

Of course you have to start with an administrative command prompt, and have a basic Chocolatey Installation in place.

If you want to clean cruft:

choco install --yes choco-cleaner

Basic install:

choco install --yes 7zip
choco install --yes everything
choco install --yes notepadplusplus
choco install --yes beyondcompare
choco install --yes git.install --params "/GitAndUnixToolsOnPath /NoGitLfs /SChannel /NoAutoCrlf /WindowsTerminal"
choco install --yes hg
choco install --yes sourcetree
choco install --yes sysinternals

For VMs (pic one):

choco install --yes vmware-tools
choco install --yes virtio-drivers

For browsing (not sure yet about Chrome as that one has a non-admin installer as well):

choco install --yes firefox

For file transfer (though be aware that some versions of Filezilla contained adware):

choco install --yes filezilla
choco install --yes winscp

For coding:

choco install --yes vscode
choco install --yes atom

For SQL server:

choco install --yes sql-server-management-studio

For web development / power user:

choco install --yes fiddler

For SOAP and REST:

choco install --yes soapui

If you don’t like manually downloading SequoiaView at gist.github.com/jpluimers/b0df9c2dba49010454ca6df406bc5f3d (e8efd031d667de8a1808d6ea73548d77949e7864.zip):

choco install --yes windirstat

For drawing, image manipulation (paint.net last, as it needs a UI action):

choco install --yes gimp
choco install --yes imagemagick
choco install --yes paint.net

For ISO image mounting in pre Windows 10:

choco install --yes wincdemu

For hard disk management:

choco install --yes hdtune
choco install --yes seatools
choco install --yes speedfan

For Fujitsu ScanSnap scanners (not sure yet this includes PDF support):

choco install --yes scansnapmanager

–jeroen

Posted in 7zip, atom editor, Beyond Compare, Chocolatey, Compression, Database Development, Development, DVCS - Distributed Version Control, Everything by VoidTools, Fiddler, Firefox, Fujitsu ScanSnap, git, Hardware, Mercurial/Hg, Power User, Scanners, SOAP/WebServices, Software Development, Source Code Management, SQL Server, SSMS SQL Server Management Studio, SysInternals, Text Editors, Versioning, Virtualization, VMware, VMware ESXi, vscode Visual Studio Code, Web Browsers, Web Development, Windows | Leave a Comment »

PlantUML – Visual Studio Marketplace

Posted by jpluimers on 2020/08/12

This and built-in markdown support made the switch to Visual Studio code from Atom.io so much easier: [WayBack] PlantUML – Visual Studio Marketplace.

Atom.io was already on my list of tools to say good bye to: though a good project to show the versatility of the Electron Framework, over time – like Google Chrome – it had become a memory and CPU hog and a drag to use and update.

Integrating debuggers and other parts of the development life cycle involved too much fuzz, for which Visual Studio code (also known as vscode) was much easier from the start.

Probably Visual Studio code did not suffer from what the Dutch call Law of the handicap of a head start: it is much more responsive and versatile than Atom.io. Also the plugins – despite having come to the market later – feel way more mature in Visual Studio code than Atom.io.

Finally, the PlantUML support extension for vscode is so much nicer than in Atom.io, it for instance supports live updating and in addition to local rendering, rendering through a PlantUML server (see [WayBack] GitHub – plantuml/plantuml-server: PlantUML Online Server).

Source code is at [WayBack] GitHub – qjebbs/vscode-plantuml: Rich PlantUML support for Visual Studio Code.

Read the rest of this entry »

Posted in .NET, atom editor, Development, Power User, Software Development, Text Editors, Visual Studio and tools, vscode Visual Studio Code | Leave a Comment »

Omg this is awesome. Synchronize settings etc between Atom installs! …

Posted by jpluimers on 2018/02/27

[WayBack] Omg this is awesome. Synchronize settings etc between Atom installs!https://atom.io/packages/sync-settings#atomio – Roderick Gadellaa – Google+

I revisited this and it’s awesome.

Note that – as usual – when you sync settings for packages that have external dependencies, these dependencies depend on your platform of choice.

Which means that if for instance depend on Pandoc and you use both a Mac and Windows, you need Pandoc installations plus all dependencies on those platforms before syncing your settings.

–jeroen

Posted in atom editor, Power User, Text Editors | Leave a Comment »

Atom.io package pandoc convert requires pdflatex for converting to pdf

Posted by jpluimers on 2018/02/20

It’s a bit hard to copy the error messages that only last a second or so, but I finally managed to:

File 0Project 0No Issues20170204.rst1:1
LF19 L | 168 W | 2329 CUTF-8reStructuredTextmaster1
[pandoc-convert]
Command failed: /usr/local/bin/pandoc --standalone --to=latex --output=/Users/jeroenp/20170204.rst.pdf /Users/jeroenp/20170204.rst pandoc: pdflatex not found. pdflatex is needed for pdf output.

In order to have pdflatex on my Mac OS X installation, I had to do this:

brew install Caskroom/cask/mactex

This will install pdflatex as

/Library/TeX/texbin/pdflatex

–jeroen

Posted in atom editor, Power User, Text Editors | Leave a Comment »

 
%d bloggers like this: