What can we not compile into fluxbox?
"Maciej M." <[email protected]> Wed, 20 Apr 2022 12:24:51 +0100
| Newsgroups | gmane.comp.window-managers.fluxbox.user |
|---|---|
| Message-ID | <CANm-CJHwRO02Sjbg5vNyFFjjGfEUvwDug55vKyTC+=G3y=dSBQ@mail.gmail.com> |
--===============3276089331162774862== Content-Type: multipart/alternative; boundary="0000000000006e8c2d05dd143eb9" --0000000000006e8c2d05dd143eb9 Content-Type: text/plain; charset="UTF-8" Just curious, are the any other things we can not compile into fluxbox besides what is shown after "./configure --help"? For me personally this flexibility is strong attribute of Fluxbox as I do not compile in parts I do not need. Would love not to compile in window tabbing but as far as I know it is not possible. Or maybe I am wrong and there is a way? Anyone? --0000000000006e8c2d05dd143eb9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">Just curious, are the any other things we can not compile= into fluxbox besides what is shown after "./configure --help"?<d= iv dir=3D"auto"><br></div><div dir=3D"auto">For me personally this flexibil= ity is strong attribute of Fluxbox as I do not compile in parts I do not ne= ed.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Would love not to co= mpile in window tabbing but as far as I know it is not possible. Or maybe I= am wrong and there is a way? Anyone?</div></div> --0000000000006e8c2d05dd143eb9-- --===============3276089331162774862== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============3276089331162774862== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Fluxbox-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fluxbox-users --===============3276089331162774862==--