Calling names, hygiene, and other grooming matters

(on the good use of bookmarks)

Tips & tricks.

Below is a list of tips and reminders that didn't quite fit in the other sections. Will grow as I go.

Avoid library Clutter:

In many situations, the same insta-BM can efficiently serve several Orgins for a given Destination, and this naming scheme was designed whith that in mind, so to avoid library clutter.
Say you have 3 stations orbiting the same planet and want insta-BMs from all of these stations to another station, itself orbiting a different planet ; this is a clear-cut situation where the same BM will do, as all these three stations can use the same BM to reach the 4th one.
This BM is a Planet -> Object BM and is named accordingly:

SystemName {DestinationPlanet#}: {OriginPlanet#} -> M{DestinationMoon#}, {StationName}
Oursulaert 9: 7 -> Fed Customs
Oursulaert 8: 7 -> M2, Astral Mining

Reminder: syntax differs slightly for gates, as Origin instead of destination is specified in the first part of the label, so that instas to gates are grouped in the listing.

SystemName {OriginPlanet#}: {OriginMoon/Station#} -> {GateName} G
Oursulaert 7: -> Alentene G
Oursulaert 4: -> Renyn G
Oursulaert 8: -> Alentene G
Oursulaert 8: M2 -> Renyn G
Oursulaert 8: Modern Finances -> Renyn G

The two last lines are examples of special cases where the Destination gate is close enough to a planet that different objects orbiting said planet may require separate BMs for accurate insta-warping.

Faster travel:

Once a BM library reaches a given size, scrolling through entire regions' folders to find next system's relevant BM can become tedious.
While it is always possible to set folders filled with BM copies of your most frequently used routes, this can eventually lead to more clutter as the list of frequent routes increases, and comes with the additional hassle of managing even more BMs and folders, and the odd chance of mistakenly moving/deleting while doing so.
A good solution to this problem is to simply have two folders per region:

RegionName (G2G)

RegionName (POI)

The first folder (G2G) contains all Gate-to-Gate BMs I own for a given region, which will cover 80% of what I need to travel and remains limited in size and easy to scroll through.
The next one (POI) will include locations, station BMs, gate <-> station BMs, etc, which I will open only when needed to avoid clutter in my Navigation window.
For safety's sake, when in 0.0, it may be worth tabbing both the (G2G) and (POI) for any region you go through - this shouldn't entail much clutter of your Navigation window, as the peripheral location of 0.0 systems makes less likely you'll travel through many different 0.0 regions over a few jumps.