Subscribe: Nick Parker
Added By: Feedage Forager Feedage Grade B rated
Language: English
create  daemon  emacs daemon  emacs  file  new  num  public  script  set  shell script  string  vim  vimperator  visual studio 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Nick Parker

Nick Parker

My Ramblings on Software Development...

Copyright: Nick Parker

Launch shell script silently at login

Thu, 07 Apr 2011 01:34:36 GMT

In OSX I needed a shell script to execute at login. There are a few different ways to perform this so I thought it might be helpful to document what your options are. I've switched over to Emacs which typically has a longer startup time than editors such as Vim. This is the shell script we will execute:
emacs --daemon
Oftentimes Emacs will stay open during an entire user session of the OS, so the sooner I can launch it the better. OSX offers a few different startup options for us. First, we have Login Items available within Account Settings of the System Preference pane. We need to rename the shell script above to end in a .command file extension to allow the Login Items to execute it. This will run at login, however we will be left with a Terminal prompt visible when the script has completed. Preferably we would execute this in the background at user login. OSX manages system and user daemons via a tool called launchd. The interface to launchd is a tool called launchctl which allows for loading and unloading daemons into launchd. XML formatted plist files are used to describe operations loaded into launchctl.


The above file, emacs-daemon.plist needs to be saved in the ~/Library/LaunchAgents directory. As you can see the xml dictates that the file should be executed at load, note we no longer need a .command file extension. We will now use launchctl to load our plist file.
launchctl load ~/Library/LaunchAgents/emacs-daemon.plist
To verify that your script executed correctly lets ask launchctl to show us what is running.
launchctl list | grep emacs
You will likely see two entries, each with three columns. Mine looks like this:
148	-	0x100100e80.anonymous.emacs
-	0	emacs-daemon
The first column is the process id, the first row shows the PID of the emacs daemon our shell script spawned. The second line is the emacs-daemon.plist job entry that executed, returning a status code of zero in the second column - success! With this setup, I can launch the emacsclient process which will attach to the daemon server and launch instantly. (image)

Generic Factory over Object Initializers

Fri, 03 Oct 2008 04:43:00 GMT

Consider the following generic factory method:
    public class Builder
        public static TType Create(Action actionOnTType) where TType : new()
            var item = new TType();
            return item;
Which allows us to do something like this:

            var aRunningCar = Builder.Create(car => 
                car.Engine = new Engine("v8");
What are your thoughts on the above over the standard object initializers found in C# 3.0?  Initially the difference is that this allows us to invoke methods on the instance as the instance is passed into our lambda expression whereas object initializers only allow us to set property values to be assigned to the instance.  It's a subtle difference but something I think could be helpful.  Just a random thought that passed through my head after I finished watching the debate tonight.(image)

Vimperator Tip - awesome bar

Tue, 23 Sep 2008 01:17:00 GMT

I just wanted to share a quick vimperator tip. You can get the awesome bar style hints by adding the following two commands to your _vimperatorrc file:
:set wildoptions=auto
:set cpt=l 

Vim + Firefox = Vimperator

Tue, 01 Jul 2008 01:39:00 GMT

Okay, so I've lamented about how I enjoy using Vim/gVim several times now. If you are still using notepad.exe as your text editor I strongly advise you to check out some of the other editors out on the market. Vim and Emacs tend to be near the top of the list, are full of features and are both extensible. The bottom line is that you need to find an editor, learn it and use it - it's that simple. In fact Dave Thomas and Andy Hunt discuss this in The Pragmatic Programmer. So, while I enjoy using the keystrokes within Vim to navigate text, what about web browsing - we all do that quite a bit these days? The mouse is the obvious choice, however it is not my only option. Enter Vimperator, suggested by Zed, a Firefox addin that allow your browser to act like Vim. A quick introduction, once you have it installed I like to turn a few things back on so that it still feels like a normal web browser for the times when I actually do want to use my mouse. Like Vim, Vimperator is configurable through a file you can create titled "_vimperatorrc" which needs to be stored within your %userprofile% directory. This file allows you to customize the way Vimperator integrates with Firefox, etc. Below I have included the contents of my _vimperatorrc file to get you started. "Turn the menu and toolbar on. :set guioptions+=mT "Turn off the show tabs by default. :set showtabline=1 "Turn session tracking off. :set! "Allow user to click in address bar. :set! browser.urlbar.clickSelectsAll=true :set! browser.urlbar.doubleClickSelectsAll=true "Map Ctrl + n for new windows :map   "Map Ctrl + t for new tabs :map  :tabopen "Map paste operation normally. :imap   After you create this file you will need to restart Firefox and then the settings with be loaded. Standard navigation include: j - down one line. k - up one line. o - open URL. shift + l - navigate forward 1 step in browser history. f [number] - opens a link based on the number displayed on screen. shift + f [number] - opens a link based on the number displayed on the screen (new tab). gg - go to top of page. shift + g - go to bottom of page. ctrl + f - navigate down one screen length. ctrl + b - navigate up one screen length. b [number] - switches to the buffer (tab) based on the number supplied. /[word] - search for [word], n goes to the next occurance, shift + n to the previous occurance. If you want to read about the other options you can hit F1 or type :help.  You can grab a nightly build here.  One thing I didn't like about the default configuration within Vimperator was that it would track your session, so when you would close your browser, the next time you open Firefox, the site you were on was reloaded.  There are keyboard commands that will not save your session (i.e., ZQ), however there are many times I will simply close the Firefox window by mouse (old habits die hard).  Above in my configuration file I have turned off the session tracking.  I have found my web navigation experience has increased dramatically with this, and my reliance on the mouse continues to decrease.  Let me know if you decide to give it a try, it will definitely be worth your time. [...]

Vim Tip of the Day - File Explorer Navigation

Tue, 06 May 2008 02:17:00 GMT

I don't know how I didn't come across this before, but when using the file explorer built into Vim, you can tell Vim to automatically switch the working directory to the current file you are editing.  Normally in Vim if you performed a ":cd c:\projects\blah" and subsequently navigated three folders deeper to edit a file (say “c:\projects\blah\foo\bar\foobar\fun.cs”), then choose to go back into the file explorer from your current location by issuing ":e .", the "c:\projects\blah" will be listed, not exactly where you might expect to be.  If you edit your _vimrc file and put the following command in when navigating the file explorer window, your current directory will automatically be set based on the file you are editing, and thus we would be dropped back into "c:\projects\blah\foo\bar\foobar").
autocmd BufEnter * lcd %:p:h

Microsoft Mocking Framework and TypeMock

Tue, 01 Apr 2008 09:11:00 GMT

While everyone has been wondering over the past couple years when Microsoft would ship its own version of a mocking framework, as of yesterday TypeMock announced it has been acquired by Microsoft and the product will be included in future versions of Visual Studio.  At least they didn't follow their previous pattern and create a less powerful clone of other products already on the market.  Hmm, interesting this should be me thinks.  Next to follow, possibly a DynamicProxy2 clone from Microsoft?  What day is today again? (image)

Creating Objects - Round 3

Thu, 06 Mar 2008 00:08:00 GMT

Ayende has been discussing the different ways of actually creating objects in .NET and the perf cost associated to each of them.  I thought I'd add to the mix one more method, using the DLR.  I've talked to several people who have identified concerns with the speed of the DLR so I found the results rather interesting.  The context is still the same, identify the time it takes to construct one million Created instances.
The delegate:
delegate Created CreateInstance(int num, string name);
The structure:
public class Created
  public int Num;
  public string Name;
  public Created(int num, string name)
    Num = num;
    Name = name;
Grab the constructor:
ConstructorInfo ci = typeof (Created).GetConstructors()[0];
Define the parameters to be passed to the constructor (relative to the code block we are about to define):
Variable num = Variable.Parameter(SymbolTable.StringToId("num"), typeof (int));
Variable name = Variable.Parameter(SymbolTable.StringToId("name"), typeof (string));
Build a code block with the Ast factories for building expressions (this builds our function for creating new Created instances with our parameters):
CodeBlock block = Ast.CodeBlock("CreateInstance", typeof (Created),
  Ast.Return(Ast.New(ci, new Expression[] {Ast.Read(num), Ast.Read(name)})),
  new Variable[] {num, name}, new Variable[0]);
Compile our block:
CreateInstance create_instance = TreeCompiler.CompileBlock(block); 
Invoke the compiled instance:
int iterations = 1000000;
Stopwatch watch = Stopwatch.StartNew();
for (int i = 0; i < iterations; i++)
  create_instance(i, i.ToString());
The results are rather impressive, the run time on my machine was 00:00:00.2737688.  It looks like creating objects within the DLR via a dynamic code block is pretty cheap.  I've included the source here if you want to run the example.  The DLR bits are based off a release from CodePlex two days ago, the RubyForge bits are much older and will not compile with the above code.  Thoughts?(image)

Vibrant Ink for Visual Studio 2008

Sun, 10 Feb 2008 16:35:00 GMT

For those of you that enjoy the Vibrant Ink theme that was originally produced for Textmate, John Lam converted it to work under both Vim and Visual Studio 2005 a while back.  I've enjoyed that for both editors, however with Visual Studio 2008 out, we need to update.  I've updated the settings file to now work with Visual Studio 2008.  Feel free to download it here. (image) (image)

Code to Live Video from Tulsa TechFest

Wed, 06 Feb 2008 02:09:00 GMT

Jeffrey Palermo and I sat down with Chris Koenig while at Tulsa TechFest back in October to chat about the new ASP.NET MVC stack.  Josh Holmes just published an extract of our conversation out on Channel 9 here.  This was recorded back in October, right after the ASP.NET MVC stack was first made public by Scott Guthrie down at the ALT.NET conference in Austin, TX.  We discussed other things such as the open source movement and it's relationship to the Java counterpart but they didn't make the cut in the editing room.  You can watch the video directly here.  Have you played with the new MVC stack yet, if so what do you think? (image)

Happy New Year

Wed, 02 Jan 2008 03:21:00 GMT

Happy New Year everyone! I've been having some issues with my server recently, so if this post makes it out there all the better. I just received notification from Microsoft this morning that I have received my MVP award for 2008. I look forward to seeing everyone up in Seattle this coming April. I am planning on blogging more this year. We have been absurdly busy at work, but there are a lot of little nuggets I am looking forward to sharing. Until next time... (image)