Menu

#15 p4-mode calls p4 for ALL find-file invocations.

v11.0
closed-accepted
None
7
2007-10-06
2005-02-02
No

This normally isn't a problem.

It *is* a problem if the network isn't available. Then
p4 calls the p4 server and emacs hangs.

I'm not sure what the correct solution is, but asking
p4 to check the network for each find-file call makes
it unsuitable for use on laptops and is debilitating
when experiencing network outages.

Discussion

  • Peter Osterlund

    Peter Osterlund - 2005-03-26

    Logged In: YES
    user_id=583120

    I think the correct solution is to use "Disable P4 VC Check"
    from the P4 menu. This will disable the find-file hook and
    is intended to solve exactly this problem.

     
  • Christian Höltje

    Logged In: YES
    user_id=267

    It's good to know about the disable p4 vc check. Thank you.

    I would like it if P4 didn't push traffic out on the net for
    every file I open. As an end user, I want the p4 mode to be
    invisible except when I need it. Is there no other solution?

     
  • Robert Stewart

    Robert Stewart - 2007-08-25

    Logged In: YES
    user_id=402463
    Originator: NO

    The reason for the find-file hook is to know whether to update the local key map with the p4.el bindings. Without that check, the key map would be updated for all files. Perhaps that would be an acceptable mode of operation which could be controlled via a flag. IOW, if not in the map-key-bindings-for-all-files mode, use the current approach to choose. It might also be possible to make the current test time out or test the waters before actually issuing the commands.

    Some of the same logic is used to determine whether a file is managed by Perforce to know whether to activate certain menu options. The latter could be managed via buffer local variables, but I think there is some caching of the information already. At any rate, the menu might trigger a similar problem.

     
  • Robert Stewart

    Robert Stewart - 2007-09-21
    • milestone: --> v11.0
    • priority: 5 --> 7
    • assigned_to: nobody --> rstewart
    • status: open --> pending-accepted
     
  • SourceForge Robot

    • status: pending-accepted --> closed-accepted
     
  • SourceForge Robot

    Logged In: YES
    user_id=1312539
    Originator: NO

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     

Log in to post a comment.

MongoDB Logo MongoDB