Slightly OT - editors
Chris Warwick
used for serious periods of time include
vi
Xedit
TextPad
Notepad2
Notepad++
GVim
But I've just found another that for some reason I've never come
across before - EditPad Pro* here: http://www.editpadpro.com/ I'm
highly impressed and shelled out for a full version a day after
downloading the trial. Syntax support for PowerShell** of course plus
sensible folding and excellent regex support. Recommended - try it!
I'd like to use PrimalScript I guess but the prices are extortionate
for private use. Really just not sensible at all. Keeping an eye on
PSAnalyser, but not yet.
What do you use and why?
Chris
* I have no connection with the company:-)
** Bringing the post ever-so-slightly back on topic
dreeschkind
- Vim
- notepad
- Notepad2
in that particular order
(for some unknown reason)
--
greetings
dreeschkind
Rob Kenny
I am using Vim with a syntax file from vim.org
Hal Rottenberg
> What do you use and why?
Thought I replied to this but apparently it went missing. I'm using
Notepad++, the Perl highlighter for it works well with Powershell.
JussiJ
wrote:
> Syntax support for PowerShell** of course plus sensible folding
> and excellent regex support. Recommended - try it!
FWIW the Zeus for Windows IDE has support for PowerShell:
http://www.zeusedit.com/features.html
It does PowerShell syntax highlighting and code folding.
Jussi Jumppanen
Author: Zeus for Windows IDE
ThuyLee
PowerShell:
http://www.zeusedit.com/language.html
ThuyLee
stable, extensible and just great.
I hope the next version includes a syntax coloration file for PowerShell,
similar to
http://weblogs.asp.net/jgalloway/archive/2006/11/25/powershell-language-definitions-for-notepad.aspx
Chris Warwick
If you try Notepad++ beware that (at least in the most recent version
I used) the installation routine completely screws-up filetype
information in your machine's registry. Rather than just creating an
association between (for example) .cmd files and the editor it
actually changes the displayed file type from "Windows Command Script"
to "Notepad++ Document". It does this for all the file types you
associate with it - a real mess and not fixed by uninstalling:-(
Chris
XDKDQO...@spammotel.com
It is free, regularly updated, available in my language (Finnish) and
has features I need. One that is missing in many editors is syntax
highlighter that can correctly color all different syntaxes that can
be included in HMTL and HTA files. PSPad has no problem with vbscript,
javascript, css sections in HTML.
PowerShell support is available as a separate download (made by me..).
Look section "PSPad extensions" -> "syntax definition" -> "Windows
PowerShell (naputtelija)". You can expand all standard aliases. For
example write iex, press ctrl+space, and PSPad replaces iex with
Invoke-Expression. You may need beta version for that because there
was a slight change in definition files in beta build 2261.
Hal Rottenberg
Awesome tip! I'm checking it out now. I think I tried this editor
many versions ago but it has been a while. The interface is a little
busy but I think I'll get used to it.
Matt
wrote:
> On Mon, 25 Jun 2007 09:09:06 -0500, "ThuyLee" <t...@unlv.edu> wrote:
> >I use Notepad++ too (http://notepad-plus.sourceforge.net) since it's free,
> >stable, extensible and just great.
>
> >I hope the next version includes a syntax coloration file for PowerShell,
> >similar to
>
> If you try Notepad++ beware that (at least in the most recent version
> I used) the installation routine completely screws-up filetype
> information in your machine's registry. Rather than just creating an
> association between (for example) .cmd files and the editor it
> actually changes the displayed file type from "Windows Command Script"
> to "Notepad++ Document". It does this for all the file types you
> associate with it - a real mess and not fixed by uninstalling:-(
>
> Chris
I prefer to download the zip and then running the program directly:
set-alias npp c:\tools\notepad++\notepad++.exe
Then within the preferences you can manually set the file types if you
wish.
However, the features of notepad++ are phenominal. I definitely
recommend giving it a try. Notepad++ and PowerShell have completely
changed the way I work for the better. I use both programs every hour
of every day.
![William Stacey [C# MVP]'s profile photo](http://lh3.googleusercontent.com/a-/ALV-UjUtEanr0b0I_eVupbLDNja5jk09ktJpLjlmTx6Lj38Gm7mCVsZp=s40-c)
William Stacey [C# MVP]
and has all the feature I need and then some. Notepad++ has so much stuff I
would almost never use and feels kinda spastic with the tons of menu items
and buttons. Both good apps however.
--
William Stacey [C# MVP]
PowerLocker, PowerPad
www.powerlocker.com
"Matt" <mgr...@gia.edu> wrote in message
news:1182975825.5...@x35g2000prf.googlegroups.com...
klu...@xtra.co.nz
> PSAnalyser, but not yet.
>
curiousity into a must have for you?
Chris Warwick
Hi Karl,
Hmmm.... interesting question that has provoked some thought because
my earlier off-hand rejection was based on feeling rather than
anything substantial. I guess because there are some issues/bugs in
the most recent version (yeah, I know it's an early release but I
suppose I trust my feelings about beta software having been around it
for so long), indications of possible coexistence problems with other
products (PSCX for example - although these may have been fixed now
(and I'm not even saying I'm a great fan of PSCX (on philosophical
grounds, not implementation or conceptual ones - I'm gonna get so
flamed here!)))
Also, I see some small things I dislike which I've admittedly not fed
back (although on some I have). For example, the syntax highlighting
follows the recommended, or de facto, 'standard' of only recognising
reserved words in all lower-case. Standards are great and I really
think we should have more of them, but I've personally been
programming scripting languages for more years than I care to divulge
and many years ago I got into a habit of capitalising the initial
character of statement blocks "...If ($Switch) {....." etc. Pedantic
I know.
I have to say I also struggle somewhat with the separate input line
and output areas in PSA - again, probably just me not giving it enough
time.
Having got that off my chest I must add that I think the concept is
great and I'm sure I'm going to need PSA at some point - which is why
I was agonising about the recently announced "buy early for a discount
offer". I'm pretty certain my decision to wait will come back to bite
me.
What happened to my startup bug btw? Haven't check the bug site for a
couple of weeks.
Anyway, all very minor points and I'm sure they're mostly down to my
foibles rather than yours - but the end result is that I'm keeping an
eye for now.
HTH
Chris
Jason
> I used) the installation routine completely screws-up filetype
> information in your machine's registry.
This will reset *some* of the changes made, but it seems like Matt's
solution (extracting from zip manually, etc.) is the better way to go:
set-itemproperty HKLM:\software\classes\.log -name "(default)" -value "LOG
File"
set-itemproperty HKLM:\software\classes\.inf -name "(default)" -value "INF
File"
set-itemproperty HKLM:\software\classes\.ini -name "(default)" -value "INI
File"
set-itemproperty HKLM:\software\classes\.nfo -name "(default)" -value "NFO
File"
set-itemproperty HKLM:\software\classes\.txt -name "(default)" -value "TXT
File"
set-itemproperty HKLM:\software\classes\.vbs -name "(default)" -value "VBS
File"
set-itemproperty HKLM:\software\classes\.log -name "(default)" -value "LOG
File"
Close and reopen Windows Explorer afterwards.
Cheers,
Jason
------------------------------------------------------
PowerShell Training at SANS Conferences
http://www.WindowsPowerShellTraining.com
------------------------------------------------------
Jason
set-itemproperty HKLM:\software\classes\.inf -name "(default)" -value
"INFFile"
set-itemproperty HKLM:\software\classes\.ini -name "(default)" -value
"INIFile"
set-itemproperty HKLM:\software\classes\.nfo -name "(default)" -value
"TXTFile"
set-itemproperty HKLM:\software\classes\.txt -name "(default)" -value
"TXTFile"
set-itemproperty HKLM:\software\classes\.vbs -name "(default)" -value
"VBSFile"
set-itemproperty HKLM:\software\classes\.log -name "(default)" -value
"TXTFile"
Chris Warwick
Thanks Jason - I had it on my list of things to do to write a script
to find all these things and them to check the original values against
a reference machine - but now I don't need too :-)
Chris
Chris Warwick
OK - read your roadmap, loved the 4/7/07 price idea and bought it:-)
(Also enjoyed the Stock Level value!)
Thanks,
Chris
Chris Warwick
Eurkkk!
I really wish you wouldn't use PayPal or Google Checkout. I don't
want to have to register with Google (and have them know what I'm
buying - they know enough about me already); and I've heard BAD things
about Paypal - OK, it's hearsay but they seem to offer the kind of
customer service that I don't think I want.
Please, for the benefit of others who will pass this way, look into
providing a standard debit/credit card payment service.
Thanks,
Chris
Oisin Grehan
wrote:
> ...
> (and I'm not even saying I'm a great fan of PSCX (on philosophical
> grounds, not implementation or conceptual ones - I'm gonna get so
> flamed here!)))
>
> HTH
> Chris
Hi Chris,
I'm surprised noone has taken you up on this yet; lets hold a
magnifying glass to the tinder and just ask you to elaborate: on what
"philosophical grounds" do you object (too strong a word?) to PSCX* ?
- Oisin
* disclaimer: I'm a dev on the pscx team ;-)
Chris Warwick
wrote:
Yeah - thought it was quiet myself!
My grounds are simply those of portability. That's it.
There's some really excellent stuff in PSCX. OK, so the whole profile
thing is a bit elaborate and takes rather a lot of unpicking (I've
arranged mine, after much work, so I can have two PS icons - one
launching PS with PSCX and one without) but other than that, as I say,
there's some great stuff in there that I can see myself relying on and
getting into the habit of using.
All great, of course, until I come to write a script or port an
existing one somewhere else where PSCX isn't available (probably for
support reasons).
So, I try to make sure that if I use a PSCX facility it's flagged up
and the resulting script (or whatever) is marked as "non-portable",
just in case.
Incidentally, the same approach applies to the Quest AD cmdlets too of
course. I'm kinda waiting for the MS versions - one of these days -
maybe in V2???
Perhaps you guys could arrange for all the PSCX stuff to be in the
native V2 - then I'd be very happy:-)
HTH!
Chris
Brandon Shell
having a powershell install script instead of a windows installer? I agree
with you on one aspect. I never write any script using any third-party
CMDLets.
I have envisioned an idea where I could have a set of DLL's on a network
share that can be accessed anywhere as well as deploying a dynamic profile
that updates it's self from a central location.
"Chris Warwick" <ne...@remove.this.bit.nuney.com> wrote in message
news:83dk9313o9tkt7k30...@4ax.com...
Chris Warwick
<tshel...@mk.gmail.com> wrote:
>What if they provided a scripted way to include/install the snap-in. Maybe
>having a powershell install script instead of a windows installer?
I don't think that would make any difference. A company may very well
permit PowerShell scripts but not third-party add-ons. Just the way
it is I guess.
Keith Hill
news:83dk9313o9tkt7k30...@4ax.com...
> native V2 - then I'd be very happy:-)
So would I. :-) Over time I'd like to see the need for PSCX diminish as
PowerShell absorbs more and more of the functionality that's in PSCX. I'm
not confident that will be anytime soon though. For what it is worth, we
realize that the PSCX profile situation isn't ideal. In 1.1 we tried to
move a number of profile functions out into scripts. We still have more
work to do. We are also planning on consolidating most Pscx global
variables into a Pscx or PscxConfig object.
--
Keith