bashburn-info Mailing List for BashBurn (Page 16)
Brought to you by:
bashburn
Menu
▾
▴
bashburn-info — BashBurn mailing list
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
(3) |
Mar
|
Apr
(31) |
May
(5) |
Jun
(10) |
Jul
(21) |
Aug
(9) |
Sep
(9) |
Oct
(5) |
Nov
|
Dec
(17) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(4) |
Feb
(7) |
Mar
|
Apr
(6) |
May
(1) |
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
(7) |
Nov
(3) |
Dec
(17) |
| 2007 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
|
May
(1) |
Jun
(1) |
Jul
(7) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(1) |
Jun
|
Jul
(8) |
Aug
(114) |
Sep
(283) |
Oct
(128) |
Nov
|
Dec
(1) |
|
From: Steven W. O. <st...@sy...> - 2008-09-03 02:26:37
|
I found some serious problems and I'm in the process of fixing. Thanks. -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net |
|
From: Markus K. <mar...@on...> - 2008-09-02 23:05:35
|
Steven W. Orr wrote: > On Monday, Sep 1st 2008 at 16:45 -0000, quoth Markus Kollmar: > > =>As I wrote already to Steven (who made changes to german translation), > =>it would be VERY NICE - Nick - if you ask me too, before making changes > =>to german translation (since I created and currently maintain german > =>translation). > => > =>No I have conflicts with my working copy, because I have checked it not > =>in frequently - since I thought the german translation is currently > =>maintained by me und thus no changes will be done. > => > =>Because of this, I think we should place a info file, where all current > =>"chief-maintainer" of bashburn-parts - or at least the tranlsations - > =>are listed. So one knows where to talk to in the case there are > =>questions and so the whole work is more structured. > => > =>Or are there any other suggestions? > > I am very happy to leave the language components alone. Markus, you are > now officially the owner of the German directory. I'm hoping that if > everyone else takes two steps backwatds, you will end up as the owner of > the whole lang directory. This doesn't mean you have to be penta-lingual, > just that you should take ownership of making all of the files look > consistent. > Hm - I would manage the language dir's if nobody else want to do this and if all agree. This would - like you said - be work to keep things consistent, and to have a person to talk first if there are any questions about the language side of bashburn. Of course this can only be done TOGETHER with the great native translators. By the way, maybe it is also a good idea if we create analogue to this, persons who coordinates a little bit the user-interface things or the burning technical part of bashburn? > Does this work for everyone? > > =>Steven, yes I personally like your system too - but with one exception > =>that I prefer to write "case 1" like: > => > =>foo='Hello' > => > =>or: > => > =>foo="Hello" > => > =>This may not be better in technically terms. But it keeps a routine to > =>quote strings and one can see with one quick look that it is a string. > =>(Ok, maybe I have a little touch of lisp programming language, where > =>normally strings are quoted, otherwise it is seen as a symbol). > > This is not a religious war I'm interested in championing. We all > understand each other and that must be worth something. > > I have run into cases in the past where people have said something like > foo=Hello > but the hello had whitespace after it. The idea is that the convention > causes you to say what you want to say, not what you mean. > > =>Short comment (for people not speaking german) which has nothing > =>directly to do with bashburn: > =>Vaterland? Steven bist Du urspruenglich aus Deutschland? Oder lebtest Du > =>dort eine weile? > > My family escaped in dubblyoo dubblyoo too. My grandfather on my mother's > side is from Gruenewald and my grandmother on my mother's side is from > Hanover. I visited a couple of times and I spent a Summer in Stuttgart > back in '67. > > Cool Steven. Stuttgart is in Baden Württemberg - where I also live. :-) > =>Arrrg... Steven I had started particulary updating the german > =>translation of the new parts and now I have conflicts with your added > =>things. You only have changed the quotes? Oh yes, I don't like conflicts > =>in vc-systems (nor in real live). ;-) > => > > I agree about the possibility of stepping on people. I'm new to svn but so > far, I'm not all that thrilled. I do need to read more, maybe buy the book > etc. But what's really lacking is the ability for people to define their > own branches. :-( > > Sorry if I can not answer/response every time immediately. (I hope this will partially be better if I have my holiday. :-) ) Markus |
|
From: Steven W. O. <st...@sy...> - 2008-09-02 21:55:03
|
On Tuesday, Sep 2nd 2008 at 15:41 -0000, quoth Nick Warne: =>As per subject. => =>I do not have time tonight (getting latish and I am tired), but perhaps =>it is an easy fix. => =>0 (Audio menu) is not able to be selected in the main menu. => =>Nick Nick, I have not problems with it. -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net |
|
From: Nick W. <ni...@uk...> - 2008-09-02 19:41:44
|
As per subject. I do not have time tonight (getting latish and I am tired), but perhaps it is an easy fix. 0 (Audio menu) is not able to be selected in the main menu. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Nick W. <ni...@uk...> - 2008-09-02 16:23:46
|
I noticed that if you change Language (no need to 'apply changes' ) and then go back to configuration menu, the help text colours now work. i.e. start BB 5 18 Read the help text Select English (or any other lang) [ENTER] 18 Read the text - it is now coloured Strange? I can't see why this is and why coloured help text doesn't work at init. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Steven W. O. <st...@sy...> - 2008-09-02 16:11:30
|
On Tuesday, Sep 2nd 2008 at 11:35 -0000, quoth Nick Warne: =>BTW, can you please explain what you done here? => =>In config/apply_options.sh => =>There is: => =>typeset bbtempfile=$(mktemp) => =>and later... => =>bbtempfile=$(mktemp bashburn_apply_opts.XXXXXX) => =>Isn't the first assignment redundant? Not redundant, just wrong. :-) I just fixed it. Thanks. -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net |
|
From: Nick W. <ni...@uk...> - 2008-09-02 15:35:10
|
On Tue, 2 Sep 2008 11:23:50 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > It could be in /tmp but it really doesn't matter: > > 1. We cp then rm instead of mv. If we did an mv then we might have to > worry if the directory that the tmpfile was in was in a different > partition than the current dir. > > 2. The size of the file is measured in O(<1k) so it doesn't matter > from that end either. > > The important thing is that mktemp should actually be given a > template for what the file should be called. If there's a problem > that needs to be debugged, then we know which file to look at. OK, I see. BTW, can you please explain what you done here? In config/apply_options.sh There is: typeset bbtempfile=$(mktemp) and later... bbtempfile=$(mktemp bashburn_apply_opts.XXXXXX) Isn't the first assignment redundant? Nick -- Free Software Foundation Associate Member 5508 |
|
From: Steven W. O. <st...@sy...> - 2008-09-02 15:23:42
|
On Tuesday, Sep 2nd 2008 at 10:35 -0000, quoth Nick Warne:
=>On Tue, 2 Sep 2008 14:17:26 +0100
=>Nick Warne <ni...@uk...> wrote:
=>
=>> On Tue, 2 Sep 2008 14:12:59 +0100
=>> Nick Warne <ni...@uk...> wrote:
=>>
=>> > > SOOOO, it looks like if you change something the .bashburnrc file
=>> > > gets trashed, and BB cannot then write out a new one... {bonk}
=>> > >
=>> > > If .bashburnrc already exists, you do not see this issue.
=>> > >
=>> > > So move your .bashburnrc out the way and start BB.
=>> > >
=>> > > Nick
=>> >
=>> > OK, fixed. Committed.
=>>
=>> Not fixed :-( .bashburnrc doesn't keep changes now. At least I can
=>> start it :-)
=>
=>OK, fixed now. Committed.
=>
=>BTW, should the bbtempfile be created in the directory where the user
=>starts BB? Should it not be in /tmp/ ?
It could be in /tmp but it really doesn't matter:
1. We cp then rm instead of mv. If we did an mv then we might have to
worry if the directory that the tmpfile was in was in a different
partition than the current dir.
2. The size of the file is measured in O(<1k) so it doesn't matter from
that end either.
The important thing is that mktemp should actually be given a template for
what the file should be called. If there's a problem that needs to be
debugged, then we know which file to look at.
--
Time flies like the wind. Fruit flies like a banana. Stranger things have .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net
|
|
From: Nick W. <ni...@uk...> - 2008-09-02 14:35:01
|
On Tue, 2 Sep 2008 14:17:26 +0100
Nick Warne <ni...@uk...> wrote:
> On Tue, 2 Sep 2008 14:12:59 +0100
> Nick Warne <ni...@uk...> wrote:
>
> > > SOOOO, it looks like if you change something the .bashburnrc file
> > > gets trashed, and BB cannot then write out a new one... {bonk}
> > >
> > > If .bashburnrc already exists, you do not see this issue.
> > >
> > > So move your .bashburnrc out the way and start BB.
> > >
> > > Nick
> >
> > OK, fixed. Committed.
>
> Not fixed :-( .bashburnrc doesn't keep changes now. At least I can
> start it :-)
OK, fixed now. Committed.
BTW, should the bbtempfile be created in the directory where the user
starts BB? Should it not be in /tmp/ ?
Nick
--
Free Software Foundation Associate Member 5508
|
|
From: Nick W. <ni...@uk...> - 2008-09-02 13:17:18
|
On Tue, 2 Sep 2008 14:12:59 +0100
Nick Warne <ni...@uk...> wrote:
> > SOOOO, it looks like if you change something the .bashburnrc file
> > gets trashed, and BB cannot then write out a new one... {bonk}
> >
> > If .bashburnrc already exists, you do not see this issue.
> >
> > So move your .bashburnrc out the way and start BB.
> >
> > Nick
>
> OK, fixed. Committed.
Not fixed :-( .bashburnrc doesn't keep changes now. At least I can
start it :-)
Nick
--
Free Software Foundation Associate Member 5508
|
|
From: Nick W. <ni...@uk...> - 2008-09-02 13:12:56
|
On Tue, 2 Sep 2008 14:00:32 +0100
Nick Warne <ni...@uk...> wrote:
> By chance I found a serious error.
>
> I changed language and saved, closed and restarted BB. It squinnies a
> lot and throws out all sorts of errors.
>
> I then found my ~/.bashburnrc file was EMPTY, and BB couldn't create a
> new one so I removed it out the way.
>
> Reverting to r 481 now shows:
>
> There is no '/home/nick/.bashburnrc'.
> This is the file where BashBurn stores and reads its configuration.
> I will now attempt to create one.
> /usr/bin/bashburn: line 5: /usr/bin/BashBurn: Is a directory
> Failed to create config file. This should not happen.
> Please report this bug to the BashBurn developers.
>
> Reverting to r 480 gets me back again and .bashburnrc is created with
> defaults (but no menus bug, of course).
>
> SOOOO, it looks like if you change something the .bashburnrc file gets
> trashed, and BB cannot then write out a new one... {bonk}
>
> If .bashburnrc already exists, you do not see this issue.
>
> So move your .bashburnrc out the way and start BB.
>
> Nick
OK, fixed. Committed.
Nick
--
Free Software Foundation Associate Member 5508
|
|
From: Nick W. <ni...@uk...> - 2008-09-02 13:00:27
|
By chance I found a serious error.
I changed language and saved, closed and restarted BB. It squinnies a
lot and throws out all sorts of errors.
I then found my ~/.bashburnrc file was EMPTY, and BB couldn't create a
new one so I removed it out the way.
Reverting to r 481 now shows:
There is no '/home/nick/.bashburnrc'.
This is the file where BashBurn stores and reads its configuration.
I will now attempt to create one.
/usr/bin/bashburn: line 5: /usr/bin/BashBurn: Is a directory
Failed to create config file. This should not happen.
Please report this bug to the BashBurn developers.
Reverting to r 480 gets me back again and .bashburnrc is created with
defaults (but no menus bug, of course).
SOOOO, it looks like if you change something the .bashburnrc file gets
trashed, and BB cannot then write out a new one... {bonk}
If .bashburnrc already exists, you do not see this issue.
So move your .bashburnrc out the way and start BB.
Nick
--
Free Software Foundation Associate Member 5508
|
|
From: Steven W. O. <st...@sy...> - 2008-09-02 12:28:21
|
On Tuesday, Sep 2nd 2008 at 04:48 -0000, quoth Nick Warne: =>On Mon, 1 Sep 2008 22:11:18 -0400 (EDT) =>"Steven W. Orr" <st...@sy...> wrote: => => =>> One more thing: NO ONE is referencing BBISCONF. Unless anyone cares, =>> I'm discarding it. There are probably more but that one is looking at =>> me. => =>There is something about BBISCONF in the TODO file. Right. That entry is to remove it from the configuration. We have variables that are not in use. :-) -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net |
|
From: Nick W. <ni...@uk...> - 2008-09-02 11:22:56
|
I see the last change reverted something I borked - I guess the other needs reverting too: http://svn.inf.sgsp.edu.pl/diff.php?rep=0&path=bashburn/menus/configure.sh&rev=466&sc=1 Nick -- Free Software Foundation Associate Member 5508 |
|
From: Nick W. <ni...@uk...> - 2008-09-02 08:48:41
|
On Mon, 1 Sep 2008 22:11:18 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > One more thing: NO ONE is referencing BBISCONF. Unless anyone cares, > I'm discarding it. There are probably more but that one is looking at > me. There is something about BBISCONF in the TODO file. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Steven W. O. <st...@sy...> - 2008-09-02 02:11:11
|
I want to do this but I'm too tired to do it now. I just rode my bike for 47 miles and I'm beat. Here's the deal: The configure menu is just stoopid. It gives us 21 options to change something. Then the last three options are apply changes, apply defaults, and Back. If you make a change then it is altered in your namespace but not 'committed' to your .bashburnrc. If you want to say back then you have no way to revert to what it was. It doesn't make sense. Here's what I want to do: When you make a change, the change will be reflected in the menu but your variables will *not* be changed. The apply changes option will actually change the values of the affected variables AND write out the new .bashburnrc . If the changes have not yet been committed then the menu display will show the value you selected with a * at the end of the line to show that it was modified but not saved. (I think emacs does it that way too. ;-) So you would see either | 4) Speed (-1) or | 4) Speed (-2)* And your actions will look (something) like this: Back will simply discard the changes if they have not been applied. |-(Actions) |- # 22) Apply changes |- # 23) Apply defaults |- # 23) Revert changes | 0) Back One more thing: NO ONE is referencing BBISCONF. Unless anyone cares, I'm discarding it. There are probably more but that one is looking at me. (Did I mention I'm dog tired?) -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net |
|
From: Steven W. O. <st...@sy...> - 2008-09-02 01:43:37
|
On Monday, Sep 1st 2008 at 16:45 -0000, quoth Markus Kollmar: =>As I wrote already to Steven (who made changes to german translation), =>it would be VERY NICE - Nick - if you ask me too, before making changes =>to german translation (since I created and currently maintain german =>translation). => =>No I have conflicts with my working copy, because I have checked it not =>in frequently - since I thought the german translation is currently =>maintained by me und thus no changes will be done. => =>Because of this, I think we should place a info file, where all current =>"chief-maintainer" of bashburn-parts - or at least the tranlsations - =>are listed. So one knows where to talk to in the case there are =>questions and so the whole work is more structured. => =>Or are there any other suggestions? I am very happy to leave the language components alone. Markus, you are now officially the owner of the German directory. I'm hoping that if everyone else takes two steps backwatds, you will end up as the owner of the whole lang directory. This doesn't mean you have to be penta-lingual, just that you should take ownership of making all of the files look consistent. Does this work for everyone? =>Steven, yes I personally like your system too - but with one exception =>that I prefer to write "case 1" like: => =>foo='Hello' => =>or: => =>foo="Hello" => =>This may not be better in technically terms. But it keeps a routine to =>quote strings and one can see with one quick look that it is a string. =>(Ok, maybe I have a little touch of lisp programming language, where =>normally strings are quoted, otherwise it is seen as a symbol). This is not a religious war I'm interested in championing. We all understand each other and that must be worth something. I have run into cases in the past where people have said something like foo=Hello but the hello had whitespace after it. The idea is that the convention causes you to say what you want to say, not what you mean. =>Short comment (for people not speaking german) which has nothing =>directly to do with bashburn: =>Vaterland? Steven bist Du urspruenglich aus Deutschland? Oder lebtest Du =>dort eine weile? My family escaped in dubblyoo dubblyoo too. My grandfather on my mother's side is from Gruenewald and my grandmother on my mother's side is from Hanover. I visited a couple of times and I spent a Summer in Stuttgart back in '67. =>Arrrg... Steven I had started particulary updating the german =>translation of the new parts and now I have conflicts with your added =>things. You only have changed the quotes? Oh yes, I don't like conflicts =>in vc-systems (nor in real live). ;-) => I agree about the possibility of stepping on people. I'm new to svn but so far, I'm not all that thrilled. I do need to read more, maybe buy the book etc. But what's really lacking is the ability for people to define their own branches. :-( -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net |
|
From: Nick W. <ni...@uk...> - 2008-09-01 23:02:42
|
On Mon, 01 Sep 2008 22:45:40 +0200 Markus Kollmar <mar...@on...> wrote: > No I have conflicts with my working copy, because I have checked it > not in frequently - since I thought the german translation is > currently maintained by me und thus no changes will be done. > > Because of this, I think we should place a info file, where all > current "chief-maintainer" of bashburn-parts - or at least the > tranlsations - are listed. So one knows where to talk to in the case > there are questions and so the whole work is more structured. > > Or are there any other suggestions? > Bloody hell. I guessed something like would happen. Do you have svn commit access? As otherwise the file change[s] move so fast sometimes it is hard to keep up. If you do, then commit often and very often. If you do not, then just use the /land/English/<files> as templates (i.e. your work is not wasted). Please mail me if you need any help here. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Markus K. <mar...@on...> - 2008-09-01 20:40:53
|
Nick Warne wrote: > On Mon, 1 Sep 2008 10:58:15 +0100 > Nick Warne <ni...@uk...> wrote: > > > >> OK, I see this was introduced for the English lang files only. >> >> RIGHT, I will fix up at least the menus for the other languages. >> Czech is nearly done. This will take me a while, but hopefully I >> will get it done and committed today. >> >> Steve: Leave off doing your stuff on the lang files for a bit until I >> commit later today. >> > > OK, the files are done and committed - please test the configure menu > in differnet languages, and if you can read the other languages, please > look for any mistakes I made. > > The lang/German/configure.lang has yet to be done, but I need a working > bashburn menu to do it, so will fix the German file later when things > are functional again in HEAD. > > There is still a lot of work to be done with the help text though - I > don't even know where to start with that! > > Nick > As I wrote already to Steven (who made changes to german translation), it would be VERY NICE - Nick - if you ask me too, before making changes to german translation (since I created and currently maintain german translation). No I have conflicts with my working copy, because I have checked it not in frequently - since I thought the german translation is currently maintained by me und thus no changes will be done. Because of this, I think we should place a info file, where all current "chief-maintainer" of bashburn-parts - or at least the tranlsations - are listed. So one knows where to talk to in the case there are questions and so the whole work is more structured. Or are there any other suggestions? |
|
From: Markus K. <mar...@on...> - 2008-09-01 20:17:35
|
Steven W. Orr wrote: > On Monday, Sep 1st 2008 at 00:34 -0000, quoth Steven W. Orr: > > =>On Sunday, Aug 31st 2008 at 17:53 -0000, quoth Nick Warne: > => > =>=>On Sun, 31 Aug 2008 22:50:09 +0200 > =>=>Anders Lind?n <and...@gm...> wrote: > =>=> > =>=>> On Sun, 2008-08-31 at 16:08 -0400, Steven W. Orr wrote: > =>=>> > On Sunday, Aug 31st 2008 at 14:39 -0000, quoth Nick Warne: > =>=>> > > =>=> > =>=> > =>=>./lang/German/BashBurn.lang:22:bb_text_7="Suche CD Brenner...." > =>=>./lang/Czech/BashBurn.lang:22:bb_text_7="Detekuji CD mechaniku ...." > =>=>./lang/Norwegian/BashBurn.lang:22:bb_text_7="Finn cd-brennar...." > =>=>./lang/Spanish/BashBurn.lang:22:bb_text_7="Detectando grabadora de > =>=>CD ...." > =>=>./lang/English/BashBurn.lang:22:bb_text_7='Detecting CD > =>=>Writer ....' > =>=>./lang/Italian/BashBurn.lang:22:bb_text_7="Sto cercando il > =>=>masterizzatore > =>=>cd ...." > =>=>./lang/Swedish/BashBurn.lang:22:bb_text_7="S??ker efter > =>=>CD-br??nnare ...." > =>=>./lang/Polish/BashBurn.lang:22:bb_text_7="Wykrywanie > =>=>nagrywarki..." > =>=> > =>=> > =>=>It is only the English language files that have single quotes... > =>=> > => > =>You said it exactly right. I just haven't yet gotten to all of the > =>language files. > > Ok. I conned myself into doin ze German files. Alles is hoffentlich in > Ordnung bei der Vaterland. > > Short comment (for people not speaking german) which has nothing directly to do with bashburn: Vaterland? Steven bist Du urspruenglich aus Deutschland? Oder lebtest Du dort eine weile? Arrrg... Steven I had started particulary updating the german translation of the new parts and now I have conflicts with your added things. You only have changed the quotes? Oh yes, I don't like conflicts in vc-systems (nor in real live). ;-) It would be VERY NICE to ask me the next time - if you make changes in the german language area - the "chief" of the german translation, which is my humble person...! ;-) |
|
From: Markus K. <mar...@on...> - 2008-09-01 19:29:17
|
Steven W. Orr wrote: > On Sunday, Aug 31st 2008 at 14:39 -0000, quoth Nick Warne: > > =>I just noticed a lot of the English Lang files text is wrapped in > =>singles quotes ' whereas most other languages use double quotes " > => > =>Why is this? Does it matter? Should there be a convention anyway if > =>either work (as they seem to do)? > => > =>I can clean up if desired tomorrow (pub time now ;-) ) > => > =>Nick > > There's nothing wrong with how things are written. using any of the > working quoting systems. I personally use a style that I developed called > The Steven Orr System of Minimal Shell Quoting. (patent pending) :-( > > Anyhoo, it looks like this: > > foo=Hello # Case 1 > bar='Woops. I slipped.' # Cabe B > baz="I like to say $foo when I meet peopls." # Case iii > > so what you have here is three distinct situations: > > In case 1, the value in question is a s single word. There is no need to > quote anything. You are allowed to use both single or double quotes, but > but not using anything, the reader of the code immediately sees that there > is a value that is composed of just one word. > > Case 2 is obviously a multi-word value with no variable expansion. No > double quotes needed. Yes, "s are legal, but I can look at a long string > and see right away that there is no variable expansion going on. > > Case 3 tells me right away that there are variables afoot. > > So you asked about a convention? There it is. > > Do you hate it? Do you love it? > > Steven, yes I personally like your system too - but with one exception that I prefer to write "case 1" like: foo='Hello' or: foo="Hello" This may not be better in technically terms. But it keeps a routine to quote strings and one can see with one quick look that it is a string. (Ok, maybe I have a little touch of lisp programming language, where normally strings are quoted, otherwise it is seen as a symbol). ;-) |
|
From: Nick W. <ni...@uk...> - 2008-09-01 14:58:03
|
Date: Mon, 1 Sep 2008 15:53:16 +0100 From: Nick Warne <ni...@uk...> To: "Steven W. Orr" <st...@sy...> Subject: Re: [Bashburn-info] Latest commit breaks BB On Mon, 1 Sep 2008 10:48:40 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > On Monday, Sep 1st 2008 at 10:44 -0000, quoth Nick Warne: > > =>On Mon, 1 Sep 2008 10:42:31 -0400 (EDT) > =>"Steven W. Orr" <st...@sy...> wrote: > => > =>> On Monday, Sep 1st 2008 at 10:39 -0000, quoth Nick Warne: > =>> > =>> =>On Mon, 1 Sep 2008 10:35:12 -0400 (EDT) > =>> =>"Steven W. Orr" <st...@sy...> wrote: > =>> => > =>> => > =>> =>> =>I have even reomved current installation and re-installed. > =>> =>> => > =>> =>> =>Nick > =>> =>> > =>> =>> This is getting weirderer and weirderer. It's working for > me. :-( =>> =>> > =>> => > =>> =>Ummm. The two files I revert to get it back again: > =>> => > =>> > =>http://svn.inf.sgsp.edu.pl/diff.php?rep=0&path=bashburn/misc/commands.idx&rev=473&sc=1 > =>> => =>> > =>http://svn.inf.sgsp.edu.pl/diff.php?rep=0&path=bashburn/config/apply_options.sh&rev=473&sc=1 > =>> => =>> =>Nick > =>> > =>> I run > =>> > =>> svn diff -r 473 misc/commands.idx > =>> svn diff -r 473 config/apply_options.sh > =>> > =>> and they both show no difference. > =>> > =>> > > I think that somehow the correct version > of BashBurn.sh didn't get checked in. Can you try again? :-( > \0/ success! I was just putting a sleep () in to see what flashed on the screen at init... and svn update pulled it in! Good job! I am not young either ;-) Nick -- Free Software Foundation Associate Member 5508 -- Free Software Foundation Associate Member 5508 |
|
From: Nick W. <ni...@uk...> - 2008-09-01 14:39:23
|
On Mon, 1 Sep 2008 10:35:12 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > =>I have even reomved current installation and re-installed. > => > =>Nick > > This is getting weirderer and weirderer. It's working for me. :-( > Ummm. The two files I revert to get it back again: http://svn.inf.sgsp.edu.pl/diff.php?rep=0&path=bashburn/misc/commands.idx&rev=473&sc=1 http://svn.inf.sgsp.edu.pl/diff.php?rep=0&path=bashburn/config/apply_options.sh&rev=473&sc=1 Nick -- Free Software Foundation Associate Member 5508 |
|
From: Nick W. <ni...@uk...> - 2008-09-01 14:01:44
|
On Mon, 1 Sep 2008 09:38:40 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > On Monday, Sep 1st 2008 at 03:53 -0000, quoth Nick Warne: > > =>I had to revert to an early revision today, as latest commit breaks > the =>menu (i.e. no menu at all) - and as I am still heavily testing > it for =>functionality... > => > =>Now, I am all for this revamp, but I can't see how leaving the code > in =>a broken state so BB doesn't work at all helps anybody... > > Nick, I did test. Between last night and now, I don't see what you > changed. > I haven't changed anything. To get the menus to work (i.e. be filled) I have to: svn update -r 422 misc/commands.idx svn update -r 413 config/apply_options.sh Nick -- Free Software Foundation Associate Member 5508 |
|
From: Steven W. O. <st...@sy...> - 2008-09-01 13:38:33
|
On Monday, Sep 1st 2008 at 03:53 -0000, quoth Nick Warne: =>I had to revert to an early revision today, as latest commit breaks the =>menu (i.e. no menu at all) - and as I am still heavily testing it for =>functionality... => =>Now, I am all for this revamp, but I can't see how leaving the code in =>a broken state so BB doesn't work at all helps anybody... Nick, I did test. Between last night and now, I don't see what you changed. -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net |
8 messages has been excluded from this view by a project administrator.
