Hi:
Why would you want to remove the "[1]"? It simply tells you how many
commands you've run in the shell.
I imagine you would need to do some hacking in the source to do that.
It wasn't exactly designed for that kind of customization, as it's not
designed to be a normal system shell - only used when Perl modules are
installed.
Jon
On Sun, Nov 2, 2008 at 9:58 PM, Stephen Liu <[EMAIL PROTECTED]> wrote:
> --- Jonathan Yu <[EMAIL PROTECTED]> wrote:
>
>> Hi there:
>>
>> You need to save your CPAN config. As in the first line, you selected
>> that:
>>
>> > <auto_commit>
>> > Always commit changes to config variables to disk? [no] [Enter]
>>
>> Therefore your settings aren't actually saved. You have to commit
>> them
>> yourself - "o conf commit" or change that setting back.
>>
>> Reading the dialogs it gives you before making your choices will help
>> you make informed decisions.
>>
>> Cheers,
>>
>> Jon
>
>
> Hi Jonathan,
>
>
> Thanks for your advice. Because I'm not quite sure the dialogs, I just
> selected default.
>
>
> Re-run
>
> # perl -MCPAN -e shell
> Sorry, we have to rerun the configuration dialog for CPAN.pm due to
> some missing parameters...
>
> Normally CPAN.pm keeps config variables in memory and changes need to
> be saved in a separate 'o conf commit' command to make them permanent
> between sessions. If you set the 'auto_commit' option to true, changes
> to a config variable are always automatically committed to disk.
>
> <auto_commit>
> Always commit changes to config variables to disk? [no] yes
>
>
> A Build.PL is run by perl in a separate process. Likewise we run
> './Build' and './Build install' in separate processes. If you have any
> parameters you want to pass to the calls, please specify them here.
>
> Typical frequently used settings:
>
> --install_base /home/xxx # different installation
> directory
>
> <mbuildpl_arg>
> Parameters for the 'perl Build.PL' command? [] [Enter]
>
> Parameters for the './Build' command? Setting might be:
>
> --extra_linker_flags -L/usr/foo/lib # non-standard library
> location
>
> <mbuild_arg>
> Your choice: [] [Enter]
>
> Do you want to use a different command for './Build install'? Sudo
> users will probably prefer:
>
> su root -c ./Build
> or
> sudo ./Build
> or
> /path1/to/sudo -u admin_account ./Build
>
> <mbuild_install_build_command>
> or some such. Your choice: [./Build] [Enter]
>
> Parameters for the './Build install' command? Typical frequently used
> setting:
>
> --uninst 1 # uninstall conflicting files
>
> <mbuild_install_arg>
> Your choice: [] [Enter]
>
>
> ( whether I need to type "--uninst 1" here ??? )
>
>
> Please remember to call 'o conf commit' to make the config permanent!
>
>
> ( Disregard selecting "Yes" on <auto_commit> above, here it still
> prompts "Please remember to call 'o conf commit' to make the config
> permanent!" ? Where shall I run 'o conf commit' on console or inside
> cpan? and how? )
>
>
> cpan shell -- CPAN exploration and modules installation (v1.9301)
> ReadLine support enabled
>
> cpan[1]>
>
>
> On next starting cpan it didn't complain again
>
>
> # perl -MCPAN -e shell
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = (unset),
> LC_ALL = (unset),
> LANG = "en_US"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
>
> cpan shell -- CPAN exploration and modules installation (v1.9301)
> ReadLine support enabled
>
> cpan[1]>
>
>
> How to remove [1] making it prompted "cpan >" ? TIA
>
>
> B.R.
> Stephen L
>
> Send instant messages to your online friends http://uk.messenger.yahoo.com
>
