Re: [PATCH] (Incomplete) Nonexistent debug flag now throws an error

2013-05-29 Thread Scott Kostyshak
On Fri, Apr 26, 2013 at 2:11 PM, Scott Kostyshak wrote: > On Fri, Apr 26, 2013 at 10:54 AM, Vincent van Ravesteijn wrote: >> Op 26-4-2013 4:05, Scott Kostyshak schreef: >> >>> On Thu, Apr 25, 2013 at 4:49 PM, Vincent van Ravesteijn >>> wrote: Op 1-4-2013 6:07, Scott Kostyshak schreef:

Re: [PATCH] (Incomplete) Nonexistent debug flag now throws an error

2013-04-26 Thread Scott Kostyshak
On Fri, Apr 26, 2013 at 10:54 AM, Vincent van Ravesteijn wrote: > Op 26-4-2013 4:05, Scott Kostyshak schreef: > >> On Thu, Apr 25, 2013 at 4:49 PM, Vincent van Ravesteijn >> wrote: >>> >>> Op 1-4-2013 6:07, Scott Kostyshak schreef: I think this is something I need to get used to: I woul

Re: [PATCH] (Incomplete) Nonexistent debug flag now throws an error

2013-04-26 Thread Vincent van Ravesteijn
Op 26-4-2013 4:05, Scott Kostyshak schreef: On Thu, Apr 25, 2013 at 4:49 PM, Vincent van Ravesteijn wrote: Op 1-4-2013 6:07, Scott Kostyshak schreef: I think this is something I need to get used to: I would not have thought that this duplication of code (e.g. reparsing the string in the same w

Re: [PATCH] (Incomplete) Nonexistent debug flag now throws an error

2013-04-25 Thread Scott Kostyshak
On Thu, Apr 25, 2013 at 4:49 PM, Vincent van Ravesteijn wrote: > Op 1-4-2013 6:07, Scott Kostyshak schreef: >> I think this is something I need to get used to: I would not have >> thought that this duplication of code (e.g. reparsing the string in >> the same way) was a good solution but I do see

Re: [PATCH] (Incomplete) Nonexistent debug flag now throws an error

2013-04-25 Thread Vincent van Ravesteijn
Op 1-4-2013 6:07, Scott Kostyshak schreef: On Sat, Mar 30, 2013 at 10:02 AM, Vincent van Ravesteijn wrote: Op 30-3-2013 6:08, Scott Kostyshak schreef: The following command now throws an error: lyx -dbg doesNotExist NOTE: THIS PATCH IS INCOMPLETE. I think I have the right condition for

Re: [PATCH] (Incomplete) Nonexistent debug flag now throws an error

2013-03-31 Thread Scott Kostyshak
On Sat, Mar 30, 2013 at 10:05 AM, Vincent van Ravesteijn wrote: > Op 30-3-2013 6:08, Scott Kostyshak schreef: >> >> + // Search for an explicit name >> >> + bool foundMatch = false; >> + for (int i = 0 ; i < numErrorTags ; ++i) >> +

Re: [PATCH] (Incomplete) Nonexistent debug flag now throws an error

2013-03-31 Thread Scott Kostyshak
On Sat, Mar 30, 2013 at 10:02 AM, Vincent van Ravesteijn wrote: > Op 30-3-2013 6:08, Scott Kostyshak schreef: > >> The following command now throws an error: >> >>lyx -dbg doesNotExist >> >> NOTE: THIS PATCH IS INCOMPLETE. I think I have the right condition >> for detecting the error, but I do

Re: [PATCH] (Incomplete) Nonexistent debug flag now throws an error

2013-03-30 Thread Vincent van Ravesteijn
Op 30-3-2013 6:08, Scott Kostyshak schreef: + // Search for an explicit name + bool foundMatch = false; + for (int i = 0 ; i < numErrorTags ; ++i) + if (tmp == errorTags[i].name) { +

Re: [PATCH] (Incomplete) Nonexistent debug flag now throws an error

2013-03-30 Thread Vincent van Ravesteijn
Op 30-3-2013 6:08, Scott Kostyshak schreef: The following command now throws an error: lyx -dbg doesNotExist NOTE: THIS PATCH IS INCOMPLETE. I think I have the right condition for detecting the error, but I don't know what to do with it. I see two ways of throwing an error: (1) create a new

Re: [PATCH] (Incomplete) Nonexistent debug flag now throws an error

2013-03-29 Thread Scott Kostyshak
On Sat, Mar 30, 2013 at 1:08 AM, Scott Kostyshak wrote: > The following command now throws an error: > > lyx -dbg doesNotExist > > NOTE: THIS PATCH IS INCOMPLETE. I think I have the right condition > for detecting the error, but I don't know what to do with it. > > I see two ways of throwing an

[PATCH] (Incomplete) Nonexistent debug flag now throws an error

2013-03-29 Thread Scott Kostyshak
The following command now throws an error: lyx -dbg doesNotExist NOTE: THIS PATCH IS INCOMPLETE. I think I have the right condition for detecting the error, but I don't know what to do with it. I see two ways of throwing an error: (1) create a new enum value for Type, THROWERROR, which LyX.cpp