Sponsored Content
Full Discussion: Editor Wars!
Top Forums UNIX for Dummies Questions & Answers Editor Wars! Post 14438 by auswipe on Thursday 31st of January 2002 04:06:56 PM
Old 01-31-2002
Code:
copy con > somefile.txt

Grunt! Grunt! Grunt!

Actually. Under Unices I prefer to use elvis or vim.

Under Win32 I prefer to use notepad but really miss the power of vi. If I wasn't such a slacker I'd just purchase UltraEdit for Win32 and be done with it.

Anybody here ever use Brief? I used to code in xBase with Brief many, many years ago and like the ability to perform block based cut and paste.

Wow. Flashback... Wordstar2000 key commands under Borland IDEs... Smilie
 

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Pasting text in VI editor from a different editor

Hi, I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question. How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'? As i see, p & P options does work only within 'vi'. (10 Replies)
Discussion started by: harishmitty
10 Replies

2. Shell Programming and Scripting

set EDITOR=vi -> default editor not setting for cron tab

Hi All, I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by set EDITOR=vi it does not open a vi editor , rather it do as below..... ///////////////////////////////////////////////////// $ set... (6 Replies)
Discussion started by: aarora_98
6 Replies

3. Solaris

Epic Editor was not able to obtain a license for your use. Feature Epic Editor :Licen

Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
ExtUtils::MM_Win32(3pm) 				 Perl Programmers Reference Guide				   ExtUtils::MM_Win32(3pm)

NAME
ExtUtils::MM_Win32 - methods to override UN*X behaviour in ExtUtils::MakeMaker SYNOPSIS
use ExtUtils::MM_Win32; # Done internally by ExtUtils::MakeMaker if needed DESCRIPTION
See ExtUtils::MM_Unix for a documentation of the methods provided there. This package overrides the implementation of these methods, not the semantics. Overridden methods dlsyms replace_manpage_separator Changes the path separator with . maybe_command Since Windows has nothing as simple as an executable bit, we check the file extension. The PATHEXT env variable will be used to get a list of extensions that might indicate a command, otherwise .com, .exe, .bat and .cmd will be used by default. init_DIRFILESEP Using for Windows. init_tools Override some of the slower, portable commands with Windows specific ones. init_others Override the default link and compile tools. LDLOADLIBS's default is changed to $Config{libs}. Adjustments are made for Borland's quirks needing -L to come first. init_platform Add MM_Win32_VERSION. platform_constants constants Add MAXLINELENGTH for dmake before all the constants are output. special_targets Add .USESHELL target for dmake. static_lib Changes how to run the linker. The rest is duplicate code from MM_Unix. Should move the linker code to its own method. dynamic_lib Complicated stuff for Win32 that I don't understand. :( extra_clean_files Clean out some extra dll.{base,exp} files which might be generated by gcc. Otherwise, take out all *.pdb files. init_linker perl_script Checks for the perl program under several common perl extensions. xs_o This target is stubbed out. Not sure why. pasthru All we send is -nologo to nmake to prevent it from printing its damned banner. arch_check (override) Normalize all arguments for consistency of comparison. oneliner These are based on what command.com does on Win98. They may be wrong for other Windows shells, I don't know. cd dmake can handle Unix style cd'ing but nmake (at least 1.5) cannot. It wants: cd dir1dir2 command another_command cd .... max_exec_len nmake 1.50 limits command length to 2048 characters. os_flavor Windows is Win32. cflags Defines the PERLDLL symbol if we are configured for static building since all code destined for the perl5xx.dll must be compiled with the PERLDLL symbol defined. perl v5.18.2 2014-01-06 ExtUtils::MM_Win32(3pm)
All times are GMT -4. The time now is 12:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy