{"id":53545,"date":"2021-10-05T03:01:41","date_gmt":"2021-10-04T17:01:41","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=53545"},"modified":"2021-10-04T15:07:43","modified_gmt":"2021-10-04T05:07:43","slug":"macos-bbedit-text-editor-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/macos-bbedit-text-editor-tutorial\/","title":{"rendered":"MacOS BBEdit Text Editor Tutorial"},"content":{"rendered":"
\"MacOS<\/a>

MacOS BBEdit Text Editor Tutorial<\/p><\/div>\n

We’re guilty of neglectful thoughts regarding our coding friend, our laptop text editor of choice. Yes, you can use one of the IDE text editors for this, but generally speaking, we’ve preferred (the Mac OS X) TextWrangler text editor we last talked about at Mac OS X TextWrangler Web Server File Editing Tutorial<\/a>. We’ve ignored for a couple of years now the TextWrangler offer of an upgrade and branding change to the name “BBEdit”<\/a>. We liked, and found useful, more to the point (good ol’) TextWrangler.<\/p>\n

Moving onto macOS did not change our preference here (for TextWrangler), but, finally, the move to macOS Big Sur saw TextWrangler lassoo its last ornery<\/strike>ternary expression. We were tense about the change.<\/p>\n

Happily, though, BBEDit is good, and has the same scripting and web server talents as we’ve talked about with TextWrangler in the past … so … yayyyyyyyyy!<\/p>\n

Coding HTML and Javascript and CSS, so far, BBEdit has offered us those syntactical niceties like color coding, and adding the (closing) “}” after us typing in an (opening) “{” (though that “coffee ahead of you knowing you wanted it service” is sadly lacking in the current BBEdit version 14.0.1 (416084, 64-bit Intel, sandboxed))<\/font>.<\/p>\n

\n

\n

Previous relevant Mac OS X TextWrangler Web Server File Editing Tutorial<\/a> is shown below.<\/p>\n

\"Mac<\/a>

Mac OS X TextWrangler Web Server File Editing Tutorial<\/p><\/div>\n

Working with the rjmprogramming.com.au web server we like any\/all access ideas we come across. A new idea here came to the top of our mind the other day. How about editing web server files, like software code ones, in place, working on this MacBook Pro, editing those files residing on the rjmprogramming.com.au domain web server? In other words, using this idea you don’t have to have an (s)ftp file tranfser (from MacBook Pro hard disk to rjmprogramming.com.au domain web server (hard disk)) mechanism, such as FileZilla<\/a> (as we talk about here with Windows FTPManager Ftp Client Primer Tutorial<\/a>), all the time, necessarily, to do work that is implemented. Minor progress perhaps, but useful access idea we think.<\/p>\n

There’s another thing about these “multitudinous” access ideas. To have this “TextWrangler” text editor method available, is one less “real” processing step to have to worry about in the deployment process, and the more you can streamline this the more time you will save for programming, thinking, unit testing and other things programmers are supposed to spend their time doing.<\/p>\n

In the Mac OS X (MacBook Pro) “TextWrangler” text editor (our favourite) how do you achieve this?<\/p>\n

    \n
  1. on MacBook Pro open (in whatever way you usually do) the TextWrangler desktop application<\/li>\n
  2. File -> Open from FTP\/SFTP Server…<\/li>\n
  3. click Connect… button<\/li>\n
  4. fill in …\n
      \n
    1. Server (of domain of website you want access to)<\/li>\n
    2. click or not the sftp checkbox (and if checked, the port is likely to be 22)<\/li>\n
    3. User (username login to “Server”)<\/li>\n
    4. Password (password of username login to “Server”)<\/li>\n
    5. Path (of “Server” hard disk, possibly the web server domain’s Document Root)<\/li>\n<\/ol>\n<\/li>\n
    6. click Connect button<\/li>\n
    7. highlight web server file of interest<\/li>\n
    8. click Open button<\/li>\n
    9. all the rest is normal TextWrangler editing of a File except that file happens to be reside on a remote web server and changes you make and File -> Save to FTP\/SFTP Server… happens “in place” (ie. no transferring required) … and feel free to view our associated PDF slideshow<\/a> for today<\/li>\n<\/ol>\n

      Cute, huh?! Access some areas! Edit in place. Follow your dream. Climb every mountain. Ford every stream. Follow every rainbow. T<\/font>i<\/font>l<\/font>l<\/font> y<\/font>o<\/font>u<\/font> f<\/font>i<\/font>n<\/font>d<\/font> y<\/font>o<\/font>u<\/font>r<\/font> d<\/font>r<\/font>e<\/font>a<\/font>m<\/font>.<\/p>\n

      What’s another “take home” from this, for us. Text editors are great, and the better ones full of interesting features like this. Think vi<\/i> and its “make” functionality as talked about at Linux vi C make Primer Tutorial<\/a>. Think Ultra Edit’s brilliant compare file functionality as talked about with Windows Text Editor Primer Tutorial<\/a>.<\/p>\n

      \n

      Previous relevant Linux vi C make Primer Tutorial<\/a> is shown below.<\/p>\n

      \"Linux<\/a>

      Linux vi C make Primer Tutorial<\/p><\/div>\n

      The Linux (or unix) command vi<\/i><\/a> is a powerful command line editor tool which has a long history with unix and the maintenance of C code (as just one example of its uses).<\/p>\n

      So much so, as far as C coding goes, that the creators of vi<\/i> clearly thought you may “set up shop” in the vi<\/i> world, because, if you have a makefile, like our simple one<\/a> for today’s tutorial, you can use vi<\/i>‘s :make<\/i> command to compile your C or C++ code while in vi<\/i> … for those thinking that they never “make” syntax errors in C … hope you know where all the Kryptonite<\/a> supplies are?<\/p>\n

      You’ll notice that you can run that compiled code (if successful) and still not leave vi<\/i> via :!.\/Hello<\/i> (where the ! is taking you to the parent shell).<\/p>\n

      There are other text editors for command line Linux (or unix), some being pico<\/a> and emacs<\/a>, and there is a bigger version of vi called vim<\/a>.<\/p>\n

      The thing about a lot of command line text editors is that they look unfriendly (it’s less unfriendly if you know {ESC}: gets you to the : prompt from the screen view … second green arrow in tutorial picture included this), and that can be true, and this has lead me to do more work with the GUI TextWrangler<\/a> (when on a Mac) if there is going to be much cutting, copying and pasting, but you should know that vi<\/i> has functionality to do with buffers, and some years back, there were maybe 6 or 7 days I’d have preferred to do copying and pasting between buffers using vi<\/i> … you’re right … I’ll “take a Bex”<\/a> and lie down now.<\/p>\n

      Here is a link to some downloadable C code you could call Hello.c<\/a> and its associated makefile<\/a> designed for Linux command line compilation via gcc<\/i><\/a> (and here is a good tutorial regarding makefiles<\/a> for gcc<\/i> compiler … thanks).<\/p>\n

      If this was interesting you may be interested in this<\/a> too.<\/p>\n