1

(27 replies, posted in Feedback)

Speaking of old users coming back (/me) ... been trying to connect to #bsd and the irc server seems to be down.  Is there a new location?

I was looking to pop in and say hi, but looks like the server is down or something.  Has it been down for a while?

Thanks

3

(1 replies, posted in RTFM)

duh, welcome to 1996 

big_smile

4

(7 replies, posted in Programming)

I added vee to google code - mainly to try it out as an alternative to SF.

http://code.google.com/p/vee/

I have a group, too, if you wish to join.

Cheers.

5

(7 replies, posted in Programming)

thanks, guys.  I like that psearch thing, too.

Cheers

6

(7 replies, posted in Programming)

Funny you mention that.  The porter (http://people.freebsd.org/~sat/) said that he had to write a little sed command to take out a "linuxism" he found in the function declarations.  I asked him to let me know what needs to change so he doesn't have to do this - I'd rather have BSD-isms in there than linuxisms!

Cheers

7

(7 replies, posted in Programming)

Check out http://www.0x743.com/.vee/1177353923.20 … 45:23.html to see why!

NOTE - there has been no new functionality, so there is no pressing reason to change things around if you have a set up you like.

Please report any issues with "upgrading", I will be happy to assist.

Cheers.

asemisldkfj wrote:

I haven't used this yet, perlfan, but it sounds really neat.  just thought you'd like to know smile.

Thanks, guys smile.

Thanks, CS.  Your comments about CSS are well taken, I definitely need to tweak those things.  However, they are my doing not a part of vii necessarily.  The numbers and date are, but can be easily tweaked.  Now that I have things structured more nicely in the code, I may go through and rethink the default formatting.  I personally like the fixed font look, but I don't know if I should include that by default.  If anyone is interested in providing me a "default" layout I'd be happy to use it in someway - my html and css skills are very weak these days.

The number on the left is simply the unix time in seconds.  The date format on the right can be tweaked - I might make it day-month-year by default because I actually like that format better.

Good comments!

10

(54 replies, posted in Programming)

I  fixed things so that the top and bottom templates work for all
types of formatting available in the default code.  In fact, as a
result,  it  is a lot easier to add new formatting.  I might be a
lot more willing to add things now.

I am pretty much freezing things in order to test for the 1.0 re-
lease,  but if anyone would like to submit some formatting functions I'd be willing to try them out for possible inclusion.

Also, if anyone is really using this thing, let me know.

Cheers,

11

(287 replies, posted in Off-Topic)

asemisldkfj wrote:

auswipe!

Yeah you right!

12

(54 replies, posted in Programming)

Thanks man - let me know if you use it.  I can start a "vii-log" roll smile.  I'd appreciate any feedback that you guys have from using it.

BTW, I did apply the changes I mentioned above:

http://www.0x743.com/.vii/1175568935.20 … 55:35.html

I also determined that the template thing already respected the right directory since it looked for the top and bottom templates only *after* it had cd'd into the right directory.

The big caveat NOW is that the templates are only used in the default formatting.  I need to make it so that it is used for all formatting, so that means I need to extract things out to a more abstract level.  Once I do this, I will deem it "1.0".

Cheers.

13

(287 replies, posted in Off-Topic)

WIntellect wrote:

Erm... I wasn't there and don't feature in any of the pics. I just know what BSDDomi looks like smile

For the record, I look like this:

For some reason I always thought you were older with a big ass beard wink

14

(54 replies, posted in Programming)

I have added a feature that allows vii to look for top and bottom html (or whatever) when entries are created.

Right now, you can't use them with the "-d" option - you have to be in the main vii-log directory you are writing to, but it looks for:

./vii-top.tpl
./vii-bottom.tpl

I plan on making it so that it respects "-d" and lets you define top and bottom templates via script variables AND commandline args - I just need to take an hour sometime to put it in and test.  Maybe this will mark my "1.0" release.

The latest download has this template stuff and you can see it in action at my site http://www.0x743.com .

Cheers

15

(54 replies, posted in Programming)

Maxx wrote:
phoenix wrote:
Oliver wrote:

Btw. bash in FreeBSD is /usr/local/bin/bash and correct UTF-8 encoding yikes)

Which is one more reason to make is sh-compatible.  /bin/sh is (usually) installed / available on every Unix system, while bash could be in any number of places (/bin, /usr/local/bin, /opt/bin, etc).

This could be accomplished easily with "/usr/bin/env bash", but making it Bourne-compatible is even better.

Yeah it would be cool if it just worked out of the box on any minimal/fresh install of *BSD, so I am going to go back to /bin/sh and fix the incompatibilities as they are made known.

Cheers.

16

(54 replies, posted in Programming)

What does this css look like?  I don't want additional files to download.

17

(54 replies, posted in Programming)

Maxx wrote:

$EDITOR seems to work with vim, thanks.

As vii should now be Bourne-compatible (runs with OpenBSD's sh) you could apply this one:

--- vii.orig    Mon Mar 12 22:58:43 2007
+++ vii Mon Mar 12 22:58:47 2007
@@ -1,4 +1,4 @@
-#!/bin/bash
+#!/bin/sh
 
 VERSION=0.9.7-beta

(I like diffs big_smile)

I'll probably create a format_func for RSS tomorrow,

Thanks, I'll apply the patch sometime today wink.

Also, send me a copy of your RSS format thingy when you are done.  I still don't know where it would fit in, but I'd be will to figure out something to facilitate you. 

I've been thinking about following:

- allowing the specifying of a post-entry script; i.e., if someone wants to do something funky after the post has been written he can write his own script for it.  This could be formatting, indexing, or even a remote transfer.
- letting vii look for a .viirc file where someone could set stuff that he wishes to override in the defaults;

At this point it meets my needs, but I want to make it attractive and easy to use.  I think the above 2 things would do that, but I have to sit on it.  At the end of the day I absolutely want to have something that someone can run out of the box with NO set up required.  That said, I think many people would like a way to tweak and customize things once they get something going and get familiar with the system.

Cheers.

18

(54 replies, posted in Programming)

"EDITOR" support is here!  I also got rid of the "()"'s in the function names.

http://www.0x743.com/vii/.vii/117373056 … 16:07.html

Cheers.

19

(54 replies, posted in Programming)

KernelPanicked wrote:
perlfan wrote:

As far as not-bourne compatible, what about it makes it not?  I don't know offhand, that is why I ask.  I would prefer to have it work under "/bin/sh" for 99.99% of *nix systems - or at least the ones I work on.  Any pointers about doing that would be appreciated.  If it is too much duct tape to do so, I'll concede to using bash.

Regarding the braces - I like them and it helps me see the code better.  You could remove them in your version if you wish smile.  Lastly, the idea of checking for $EDITOR in the home env is not _bad_, but I also don't want to have to account for all the various ways different editors open new files, etc.  In a nutshell, I don't want to go down that road.

Okay so after I got a few seconds to run through this thing, it would seem to the only shell issue is the braces. Now, to be fair, this could be some wierdness on my system since I'm using OpenBSD and sh is actually ksh in sh mode.

The man page says functions should be written like this (and this is how I've always done it myself.

function { some command; some other command; }

/bin/sh, or at least my version is choking on the () and lack of ;  but I've fixed this in the version I'm playing around with.

perlfan wrote:

I appreciate everyone playing around with it and welcome more suggestions ... and better yet, code!  If there is a format you think might be useful, please write it up, test the code within vii, and send me a link of what the output looks like.  Here is a hint though - it must look okay and be easily navigated inside of something like lynx.

I'm glad someone still cares about the text browser users of the world. I died a little inside when Wintellect suggested CSS. tongue

smile...that is funny.

Anyway, so all I need to do is to get rid of the "()"'s and add semi-colons at the end of eachline?  Do I need to add line continuation characters at all?

Maxx, would you settle for "$VI" instead of "$EDITOR"?  I know you want to use the environment EDITOR, but I don't want to encourage the use of other editors that I don't purport to support.  If you test it with your editor (assuming not vii) and tell me that it works fine with it, I'll mention that "users report that vii also works with the following editors"...how does that sound?

Cheers.

20

(54 replies, posted in Programming)

I never heard of nanoblogger, but I agree - seems nice but bloated.  I don't intend on having categories as such - if I wanted to key the reader in on a topic I would put [TOPIC] in the title or I would create a different index with "-i".  I just don't want to have to manage categories, relate them explicitly to messages, etc.

Also, I suppose it would be easy enough to dump some RSS for an index using the same <!--;<integer>;--> per line to ensure proper ordering.  I am willing to consider anything for inclusion as long as it fits in with my goals.  I just don't want to get into managing entries, etc.  I feel like I am already going down a road of managing entries that might start increasing the complexity greatly for less and less return on functionality.

As far as not-bourne compatible, what about it makes it not?  I don't know offhand, that is why I ask.  I would prefer to have it work under "/bin/sh" for 99.99% of *nix systems - or at least the ones I work on.  Any pointers about doing that would be appreciated.  If it is too much duct tape to do so, I'll concede to using bash.

Regarding the braces - I like them and it helps me see the code better.  You could remove them in your version if you wish smile.  Lastly, the idea of checking for $EDITOR in the home env is not _bad_, but I also don't want to have to account for all the various ways different editors open new files, etc.  In a nutshell, I don't want to go down that road.

I appreciate everyone playing around with it and welcome more suggestions ... and better yet, code!  If there is a format you think might be useful, please write it up, test the code within vii, and send me a link of what the output looks like.  Here is a hint though - it must look okay and be easily navigated inside of something like lynx.

Cheers!

21

(54 replies, posted in Programming)

In this latest release (http://www.0x743.com/vii/.vii/117363965 … 00:53.html), I organized the code better to facilitate different formatting options. 

The current options are: groff, fold, and none.  None simply cat's the contents as is while groff and fold try to format things a bit.  KernelPanicked, if you wrote one for breaking the body and subject/title out of an email that was piped into it, I would happily add it to the list of "out of the box" options.

I also made added the following options recently:

-I 
   forces index to be "index.html"

-i 'myindex.html'
   makes vii use "myindex.html" as index

-d dir
   uses this directory as the "base" from which it looks for the index file and the .vii directory

Cheers

22

(54 replies, posted in Programming)

Oliver wrote:

Did some small advert for German people, http://www.from-hades.de/2007/03/11/vii … geek-blog/ big_smile

Awesome, Oliver.  Thanks!

23

(54 replies, posted in Programming)

KernelPanicked wrote:

I do actually find this quite useful and since I long ago blew up my WP blog I might as well start another with this. What I'd like to do, as soon as I have a little time, is modify this or write a wrapper that I can set up a mail alias to pipe to. Basically I want to mail in my blog entries, because I'm extremely lazy and don't want to log into my server.

Let me know if some small tweaks to vii would help facilitate this.

I know that it is easy to pipe the message itself into vii, but as of right now it would use everything you printed into it as the message body.  It might be easier if there was a flag that told it to strip out the headers, use the email body for the main message, and use the subject for the title.  That way, it would be trivial to set up a mail filter for updating your blog.

I totally agree that emailing blog entries is idea, and when I wrote this I was thinking, "what is as good or almost as good as being able to email a blog entry".

So keep me posted, and I'll be thinking about where to put all of this.  I am probably going to write a formatting-dispatch shell block that allows one to add any number of formatting styles by putting an entry in a case statement that then calls the function they specify.  This would facilitate a "-f format_label" commandline flag that makes it easy for people to add their own.

Cheers,

24

(54 replies, posted in Programming)

KernelPanicked wrote:

This is good stuff. Once I figured out that it's not really bourne compatible and just ran it under a bash shell, that is. I've got 18MB of text file technical notes at work I was going to put in HTML format at some point and I'm thinkin this thing plus batch mode might just do the trick.

If this is the case, I need to be sure to state this.  Thanks for pointing this out!

Also, I think it is cool that you might find it useful. If you get something publicly accessible up, let me know smile

25

(54 replies, posted in Programming)

That is probably where I'd draw the line - that said, you can easily put it in your own copy of vii since it is just bourne shell. I certainly don't want another file to have to send out, but if you can suggest a way that wouldn't require distributing a second file and only adds a few extra "echos", then I am all for it. 

I think this is where it goes from just right in my mind to a bit much.  Figure out the above for me, and I'll happily add a few more lines of html goodness.