Kompx.com or Compmiscellanea.com

Windows console applications. Text editors

Operating systems : Windows

FTE : JED : MinEd : Nano : MS-DOS Editor

Initially, all text editors did not have a graphical interface. And work with text almost from the outset was one of the main types of user activity on computer. With the invention and spread of low-level and especially high-level programming languages, text editor has become an important working tool of professionals. Then, other users had to use text editors for their daily tasks. So by the time the programs with GUI started to be wide spread, the concept of text editor was already well developed, there were mature, well-designed and implemented specimens of applications for text editing without graphical user interface. Why the text-based versions coexisted with GUI-based ones for very long and still graphical user interface programs have not replaced the console / text-based applications.

While the average user is not aware of their existence, he / she does not know the power of vim or emacs, often even MS-DOS Editor, built in all the 32-bit versions of Windows is unknown, none the less, console text editors continue to exist and be developed. As it is the case with the text web browsers, the main line of text-based text editors development is in Linux and other *nix systems world. But under Windows as well, there are several interesting applications.

FTE - / home page /

Console text editor. Version for Linux, some other *nix systems, DOS, Windows, OS/2.

Syntax highlighting support for: C, C++, Java, Perl, Sh, Pascal, SQL, Assembly, PHP, Python, REXX, Ada, Fortran, IDL, LinuxDoc, TeX, TeXInfo, HTML, etc. ASCII table. Various facilities for coding and errors handling. Copying words, characters or text blocks is in the same mode and by the same keyboard shortcuts (except Ctrl+A) as in major Windows text editors with graphical user interface - plus, there may be other variations.

FTE 0.49.13:

Open file

Image : FTE - 1

FTE 0.49.13:

A submenu

Image : FTE - 2

FTE 0.49.13:

Settings

Image : FTE - 3

FTE 0.49.13:

Opened .php file

Image : FTE - 4

FTE 0.49.13:

Opened .htm file

Image : FTE - 5

FTE 0.49.13:

Opened C code

Image : FTE - 6

JED - / home page /

Console text editor. Version for Linux, some other *nix systems, QNX, OS/2, BeOS, OpenVMS, DOS, Windows.

Syntax highlighting support for: C, C++, FORTRAN, TeX, HTML, SH, python, IDL, DCL, NROFF, etc. JED can emulate Emacs, EDT, Wordstar, Borland, Brief. C-like S-Lang language for extra settings possibilities and extensions. Search and replace across multiple files ( More ).

JED 0.99.18:

Open file

Image : JED - 1

JED 0.99.18:

A submenu

Image : JED - 2

JED 0.99.18:

Help submenu

Image : JED - 3

JED 0.99.18:

Opened .php file

Image : JED - 4

JED 0.99.18:

Opened .htm file

Image : JED - 5

JED 0.99.18:

Opened C code

Image : JED - 6

MinEd - / home page /

Console text editor. Version for Linux, Solaris, some other *nix systems, DOS, Windows.

Unicode support. Capability of editing files with mixed text encoding. Support for diacritical marks of scripts based on Latin, Cyrillic, Vietnamese. Support for left-to-right and right-to-left scripts. Support for CJK with auto detection of encodings. Word wrap with various nuances. In case of an external interrupt, panic handling saving of the text to a panic file if possible ( More ).

MinEd 2011.19.2:

Open file

Image : MinEd - 1

MinEd 2011.19.2:

A submenu

Image : MinEd - 2

MinEd 2011.19.2:

Settings

Image : MinEd - 3

MinEd 2011.19.2:

Opened .php file

Image : MinEd - 4

MinEd 2011.19.2:

Opened .htm file

Image : MinEd - 5

MinEd 2011.19.2:

Opened C code

Image : MinEd - 6

Nano - / home page /

Console text editor. Version for Linux, Solaris, some other *nix systems, Windows.

Version of the Pico text editor from the Pine e-mail client ( More ).

Nano 2.2.6:

Open file

Image : Nano - 1

Nano 2.2.6:

Cursor position info

Image : Nano - 2

Nano 2.2.6:

Help

Image : Nano - 3

Nano 2.2.6:

Opened .php file

Image : Nano - 4

Nano 2.2.6:

Opened .htm file

Image : Nano - 5

Nano 2.2.6:

Opened C code

Image : Nano - 6

MS-DOS Editor - / home page /

Console text editor. Version for DOS, Windows.

Text editor which appeared as far back as in DOS 5.0 and still remaining the built-in editor in all 32-bit Windows. Commonly called just edit and can be launched either by typing it into the Run command dialog on Windows or by typing edit into the command-line interface (cmd, Console). Windows version can edit files of up to 5 MB in size. Copying words, characters or text blocks is in the same mode and by the same keyboard shortcuts (except Ctrl+A) as in major Windows text editors with graphical user interface. Colors of the interface scheme are customizable.

MS-DOS Editor 2.0.026:

Open file

Image : MS-DOS Editor - 1

MS-DOS Editor 2.0.026:

A submenu

Image : MS-DOS Editor - 2

MS-DOS Editor 2.0.026:

Settings

Image : MS-DOS Editor - 3

MS-DOS Editor 2.0.026:

Opened .php file

Image : MS-DOS Editor - 4

MS-DOS Editor 2.0.026:

Opened .htm file

Image : MS-DOS Editor - 5

MS-DOS Editor 2.0.026:

Opened C code

Image : MS-DOS Editor - 6

Also, DOS text editors may be used. Such as SETEDIT, TDE, PEDIT, MultiEdit, EDITV and others.


Aliosque subditos et thema

 

JavaScript form submit

 

Submitting a form using JavaScript. A dropdown list (form + select + multiple options) is processed without any submit button. Example: --- Select a page --- Linux Windows DOS HTML / XHTML. Code: <form action="action.php" method="post"> <select name="page" required="required" onchange="this.form.submit()"> <option value="" selected="selected" disabled="disabled"> --- Select a page --- </option> <option value="http://www.kompx.com/en/os/linux-1.htm">Linux</option> <option value="http://www.kompx.com/en/os/windows-1.htm">Windows</option> <option value="http://www.kompx.com/en/os/dos-1.htm">DOS</option> </select> <noscript><input type="submit" value="Submit" /></noscript> </form> When an option has been chosen from the dropdown list, the form's state is changed. So the onchange event occurs and JavaScript code in onchange is executed: the process of the form submission in started by the script, not by clicking submit button which is absent. Some server-side script [ 3 ] is meant then to handle the form action. The script is supposed to get what the form sends and have it processed. A PHP script in action.php is used in the example: <?php if (isset($_POST["page"])) {     header("Location: $_POST[page]");     exit; } else {     echo "No options selected"; } $_POST is an array of variables passed to the current script via the HTTP POST method. So $_POST[page] contains the content of the value attribute in a select option. That is, a URL. It is passed from form to PHP script and the script redirects browser to the URL / page selected. HTML code of <noscript><input type="submit" value="Submit" /></noscript> is present in the form as a fallback in case JavaScript happens to be turned off. Then there is a submit button to appear and the form is usable anyway. [ 1 ] As well as Netscape 3.04+, Mozilla 0.6+. [ 2 ] As well as Netscape 3.04+, Mozilla 0.6+. [ 3 ] If a CMS is used, form action may be handled by some of its inbuilt means.

HTTP to HTTPS redirect in .htaccess

 

Redirecting from HTTP to HTTPS, when the web server serving the pages is behind a load balancer or reverse proxy. Server configuration: Apache + nginx; SSL is enabled; SSL-certificate is purchased, approved and installed. That is, everything is up and running. So it is just the HTTP to HTTPS redirection that is left to get ready and start up. Directives for .htaccess file: RewriteEngine On RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L] RewriteCond %{HTTP:X_FORWARDED_PROTO} !https [NC] RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L] HTTP to HTTPS redirect -- Enable runtime rewriting engine: RewriteEngine On -- If domain name has no www: RewriteCond %{HTTP_HOST} !^www\. [NC] -- Then replace it with domain with www: RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L] -- If HTTPS is not present: RewriteCond %{HTTP:X_FORWARDED_PROTO} !https [NC] -- Then replace domain without HTTPS with domain with HTTPS: RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L] Notes 1. X_FORWARDED_PROTO may instead be called X-Forwarded-Proto or even else. The point is to obtain the information from a load balancer or reverse proxy on the original request it gets. Load balancers or reverse proxies may provide the web server with this info and a header named X_FORWARDED_PROTO or X-Forwarded-Proto or else may be sent, holding the protocol string. It is most often so, but not always. So it should probably be determined by practice how to get the protocol string in a particular case. 2. The other way is just to set the environment variable (if it is suitable for the given web server): SetEnvIf X_FORWARDED_PROTO https HTTPS=on Then directives for .htaccess file are to be like this: RewriteEngine On SetEnvIf X_FORWARDED_PROTO https HTTPS=on RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L] RewriteCond %{HTTP:HTTPS} !on [NV] RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L] 3. Apache Module mod_rewrite docs: http://httpd.apache.org/docs/current/mod/mod_rewrite.html