search for: first_path

On Wed, 12 Jun, at 05:01:13PM, Ady wrote: > Perhaps the following is just a crazy idea... How about no > path-separator in the cfg file, and instead use multiple PATH > directives for each path in the cfg file? > > Instead of the previous: > PATH first_path:2nd_path > > now just use: > PATH first_path > PATH 2nd_path You can actually do this already - multiple PATH directives are concatenated. But I think there's still value in allowing users to specify multiple entries with one PATH. -- Matt Fleming, Intel Open Source Technology C...

...tantly; > which was complete madness. > > Matt Fleming, Intel Open Source Technology Center Perhaps the following is just a crazy idea... How about no path-separator in the cfg file, and instead use multiple PATH directives for each path in the cfg file? Instead of the previous: PATH first_path:2nd_path now just use: PATH first_path PATH 2nd_path If this syntax would be possible (while multiple paths in one line would be "unsupported"), then each PATH directive would accept only one path in the cfg file. Each PATH directive would add more paths, in the same order they appea...

...; On Wed, 12 Jun, at 05:01:13PM, Ady wrote: > > Perhaps the following is just a crazy idea... How about no > > path-separator in the cfg file, and instead use multiple PATH > > directives for each path in the cfg file? > > > > Instead of the previous: > > PATH first_path:2nd_path > > > > now just use: > > PATH first_path > > PATH 2nd_path > > You can actually do this already - multiple PATH directives are > concatenated. But I think there's still value in allowing users to > specify multiple entries with one PATH. Right, s...

On Tue, 11 Jun, at 03:54:21AM, H. Peter Anvin wrote: > On 06/11/2013 01:03 AM, Matt Fleming wrote: > > On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote: > >> Either that or make the path a list rather than a string, using the > >> normal word separators when entered on the command line, a bit like the > >> (t)csh does. That is a bigger change but is probably

...). One alternative, in an attempt to reduce potential issues, was/is the recommendation to use multiple PATH directives, each in a different line/row in the configuration file, instead of using the path separator within one same PATH directive. In other words, the PATH directive accepts: PATH first_path PATH second_path and the paths are appended to the list of searched-for paths (looking for c32 (library) modules). I would suggest trying this alternative for a test, independently of how the code might parse / mess up this notation anyway. Yet, again, real-world cases were not presented here....

I am trying to create a dynamic menu using the following construct: <%- menu_list = [ ''first'', ''second'', ''third''] -%> <ul> <%- menu_list.each do |m| -%> <%= link_to "List All #{m.titlecase.pluralize} <m>_path %> <%- end -%> </ul> What I cannot determine is what I have to do to replace

I've been trying to get syslinux.efi working in my environment again... Found what look like a bunch of little bugs that are very frustrating... First, the documentation on the Wiki says that as of 5.11, the list separator is space, not colon. But I can find no evidence that 5.11 was ever officially released or that a commit to git was made to make this change. 6.00 and following still use