ERC layout issue with more than one server

[dschrempf]

Description :octocat:

When using more than one erc server, only channels from the last server get added to the @ERC layout.

Reproduction guide :beetle:

• Start Emacs

(setq erc-server-list
      '(("irc.freenode.net"
         :port "6697"
         :ssl t
         :nick "mynick1")
        ("irc.gitter.im"
         :port "6697"
         :ssl t
         :nick "mynick2")))
(setq erc-autojoin-channels-alist
      '(("freenode.net" "#emacs" "#archlinux" )
       ("gitter.im" "#syl20bnr/spacemacs")))

• Start ERC with default servers with SPC a i D.

Observed behaviour: :eyes: :broken_heart: ERC does it's magic. However, after all chat rooms have been entered, only #syl20bnr/spacemacs is in the @ERC layout.

Expected behaviour: :heart: :smile: #emacs, #archlinux, and #sul20bnr/spacemacs are in @ERC layout.

System Info :computer:

• OS: gnu/linux
• Emacs: 26.1
• Spacemacs: 0.300.0
• Spacemacs branch: develop (rev. 6a724e416)
• Graphic display: t
• Distribution: spacemacs
• Editing style: vim
• Completion: helm
• Layers:

  (auto-completion better-defaults git gtags helm ibuffer neotree ranger shell spell-checking semantic spacemacs-layouts version-control
               (c-c++ :variables c-c++-default-mode-for-headers 'c++-mode c-c++-enable-clang-support t)
               emacs-lisp ess haskell html
               (javascript :variables tern-command
                           '("node" "~/.node_modules_global/bin/tern"))
               latex markdown python rust shell-scripts vimscript yaml erc twitter mu4e my-org syntax-checking)

• System configuration features: XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GSETTINGS NOTIFY ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 MODULES THREADS LIBSYSTEMD LCMS2

Backtrace :paw_prints:

Not relevant.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!