Editing
The Perl Lazarus Workshop
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== MSYS2, vim, and Git: recovering a familiar working rhythm == A Windows application should be built and tested against Strawberry Perl, but the craftsman does not need to abandon a familiar Unix-like editing workflow. [https://www.msys2.org/ MSYS2] supplies a Unix-like command-line environment and a package manager for Windows.<ref>[https://www.msys2.org/docs/what-is-msys2/ MSYS2, “What is MSYS2?”]</ref> Within its terminal, the programmer can install vim and Git: <pre> pacman -S vim git </pre> This creates a productive division of labor. The MSYS2 terminal can be used for: * editing with vim; * reviewing diffs; * committing changes; * managing branches; * using SSH keys; * navigating the project with familiar shell tools; * and performing the normal source-control work of a Unix-oriented Perl programmer. The Strawberry Perl terminal should be used for: * installing Perl modules; * running the wxPerl application; * executing Perl-oriented build commands; * creating the executable; * and verifying behavior against the actual Perl environment intended by the project. This separation is not merely a personal preference. Installing Git and related packages in MSYS2 may also install an MSYS2 Perl. Running the application from that shell without checking the active <code>PATH</code> can therefore invoke a different Perl than the Strawberry Perl for which wxPerl was built. The programmer should know which Perl is active. A workshop may contain two hammers. The craftsman must still know which one he has picked up. Git is particularly important when generated code is involved. wxGlade can preserve user code when configured properly, but configuration mistakes and generation changes can still damage handwritten work. A clean commit before generation gives the programmer a truthful record of what changed and a practical way to recover. The detailed edit–emit–wire–run workflow belongs to the next essay. Here it is enough to recognize that MSYS2 is not replacing Strawberry Perl. It restores a familiar editing and revision rhythm around it.
Summary:
Please note that all contributions to Perl Guilds - Getting Medieval with Perl may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Perl Guilds - Getting Medieval with Perl:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
Edit source
View history
More
Search
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
Tools
What links here
Related changes
Page information