i did add a blueprint for this.
AhAh, that is more a redprint 
I don’t use KiCad for long time, but if I remember correctly that “Library” means exactly that, you have to open a Library… then… you will load / edit individual symbols of that Library. I think it is not intuitive and you need some kind of “background abstraction knowledge” of what you are doing… 
1 Like
you navigate trough the open menu and open the library as would you have opened a directory
done deal, no need to fiddle with the save library thing,
if you save the symbol update the library in the background. no need to bother end user with that.
show both you library name and symbol name in the head of the frame, today is only library shown in the top edge.
save library should also go away
if you save the symbol you also save the library where it resides.
simple as that
I can suggest that you open a new wish bug in KiCad bug tracker in order to make it visible and traceable for developers.
Create a bug and mark it as a wish.
The library is the file… that must be how that came to be.
They will touch eeschema down the road and rework it to be like the footprint editor and the footprint concept (1 footprint = 1 file, 1 library = 1 folder) afaik.
Yep, and as I understand new symbol libraries will be called *.sweet
So in the future KiCad will be pretty sweet 
2 Likes
.pretty .sweet ?
Dude, where’s my car?
Why not make some complete reboot:
.kicad_pro - Project
.kicad_sch - Schematic
.kicad_sym - Schematic component/symbol (also as legacy .sym with graphics only)
.kicad_lib - Libraries (no matter if it’s for footprint or schematic symbols)
.kicad_equ - For automatic footprint assignment
.kicad_ant - For backward annotation (legacy .cmp)
.kicad_pcb - Board
.kicad_mod - Footprint
.kicad_wks - Worksheet layout
.kicad_pys - Python script for KiCad
.kicad_der - Design rules
All kind of files,except .kicad_pys have DSN format.
1 Like
I’d like that, do you want to make a suggestion on the bugtracker or developers’ mailing list?